Most advice on how to get people to RSVP stops at "send a friendly reminder" and then links you somewhere else for the actual wording. This guide keeps the wording here: 24 complete, copy-paste messages for text, email, in-app notification and phone, sorted by the stage of the chase they belong to.
It also fixes the part almost every guide skips. Chasing RSVPs is not one message repeated louder. It is a five-stage sequence across three channels, aimed at a shrinking segment of people, and the reason most hosts fail is that they send the same email to the same full list twice and call it follow-up.
| # | Tactic | What it fixes |
|---|---|---|
| 1 | Put an end time on the invitation | The guest who can't tell if a "yes" costs them two hours or eight |
| 2 | Put a dated deadline in the invitation itself | "I'll do it later" with no later |
| 3 | Give the deadline a reason | A date with no consequence reads as optional |
| 4 | Cut the reply to one tap, no account, no password | The 40 percent who bounce at a signup screen |
| 5 | Invite each person directly, not to one shared address | "It got buried in my inbox" |
| 6 | Split the event into functions | The guest who can come to the reception but not the ceremony |
| 7 | Send Tuesday to Thursday, in the right week | Weekend and Monday sends that get skimmed |
| 8 | Nudge non-responders only | Reminder fatigue among the people who already answered |
| 9 | Escalate channel, not volume | Ten emails to someone who does not read email |
| 10 | Publish who's coming | Fence-sitters waiting to see if their friends are going |
| 11 | Run a 72-hour headcount call | Maybes that were never going to resolve on their own |
| 12 | Confirm the day before, yeses only | The no-show you could have caught |
People don't RSVP because your invitation left a question unanswered, not because they are rude. Five specific gaps account for nearly all of it, and each has a concrete fix.
A guest cannot say yes to an unknown quantity of their Saturday. "Dinner at 7" could be two hours or six. If they have a morning flight, a babysitter on the clock or a second event that evening, the only safe answer to an open-ended invitation is no answer.
The fix: state a finish time. "6:30 to 9:30 p.m." converts better than "6:30 p.m. onward" because it prices the commitment. If the event genuinely runs late, write "dinner 7 to 9, drinks after for anyone who can stay."
"Let me know if you can make it" creates no task. There is nothing to put in a calendar, nothing to be late for, and no moment at which not replying becomes rude. Guests are not procrastinating on your deadline. You didn't give them one.
The fix: a named date with a day of the week. "Please reply by Thursday, October 8." See the deadline wording section below for phrasing that holds up.
This is the most under-diagnosed reason. Plenty of guests are deciding whether they want to spend an evening in that particular room, and they cannot answer until they know who is in it. Silence here is not indecision about your event. It is indecision about your guest list.
The fix: make the yes list visible. A live count ("18 going") does some of the work. Naming two or three people does more: "the Okonkwos and Priya are already in." Ask permission before naming anyone.
Your invitation offers three buttons: yes, no, maybe. Your guest's honest answer is none of those. They can make the reception but not the 2 p.m. ceremony on a workday. They can do Sunday brunch but not Friday's welcome dinner. Faced with a form that cannot express that, most people pick "maybe" and stop thinking about it, or say nothing and turn up to whichever part they can.
Either way you lose. A maybe is not a headcount, and a surprise arrival at brunch is not something your caterer can absorb.
The fix: stop treating a multi-part event as one event. Give each function its own date, time, venue, guest list and RSVP. This is what per-function RSVP means in practice, and it is covered in detail below.
Every screen between the invitation and the answer costs you responses. A signup form, an email verification, a password, an app download. Each one is a place where a guest who meant to say yes puts their phone down instead.
The fix: the reply should be one tap from wherever the invitation was opened, with no account and no download. If your platform asks a 71-year-old aunt to create a password, that is your response rate problem, not hers.
Send the invitation far enough out that calendars are still open, and close enough that people don't file it away and forget. These windows are practical defaults, not rules.
| Event type | Send invitation | RSVP deadline | Notes |
|---|---|---|---|
| Weeknight dinner, 6 to 12 people | 2 to 3 weeks out | 5 days before | Text is the right channel end to end |
| Birthday, BBQ, game night | 3 to 4 weeks out | 10 days before | Send Tuesday to Thursday |
| Baby shower, engagement party | 4 to 6 weeks out | 14 days before | Travel guests need the longer window |
| Milestone birthday, anniversary | 6 to 8 weeks out | 21 days before | Save-the-date 3 months ahead if guests fly |
| Wedding, single day | 6 to 8 weeks out | 21 to 28 days before | Caterer cutoff usually 10 to 14 days out |
| Wedding weekend, multiple functions | 8 to 10 weeks out | Per function, staggered | Each function gets its own deadline |
| Holiday season party (Nov to Dec) | 5 to 6 weeks out | 14 days before | December calendars fill first |
| Last-minute among close friends | 5 to 10 days out | 48 hours before | Text only, no formal deadline |
On a multi-function event, one shared deadline is a mistake. Your Friday welcome dinner needs numbers before your Sunday brunch does, and the ceremony seating chart is a different problem from the after-party bar count.
Set each function's deadline against the vendor it feeds. Welcome dinner at a restaurant with a 14-day cutoff gets a 21-day deadline. Backyard brunch you're cooking yourself gets a 5-day deadline. Guests see one invitation and answer each part on its own timeline.
Tuesday through Thursday, mid-morning or just after work, is the reliable window. Monday sends land in inbox triage. Friday and Saturday sends get skimmed and lost. Sunday evening is surprisingly good for text, because that is when people look at the week ahead.
Count the taps between your invitation and a recorded yes. If the number is above two, that is where your responses are going.
Here is the full list of things that cost you a reply:
Ask two questions at the RSVP stage: are you coming, and are you bringing anyone. Everything else is a follow-up to people who already said yes.
The most common failure mode in this category is the one Mixily's own guide opens with: the invitation got buried in an inbox. That happens because it was addressed to a mailbox rather than to a person.
Lumhe changes the delivery path. You find and connect with your guests by name, phone number or email inside Lumhe and send the invitation directly, so it arrives as an invitation in the app rather than as one more unread email competing with receipts and newsletters. They open it and answer with one tap. No account creation, no password, no PDF attachment that won't open on a phone.
You upload the invitation you already made, in whatever form it exists: an image exported from Canva, a video, a PDF from your stationer, or typed text. Lumhe does not design it for you. It carries what you made.
Every invitation also generates a shareable link, so you can drop it into WhatsApp, iMessage, Instagram or email for the handful of people you are not connected with yet.
A deadline works when it names a date, a day of the week, and a reason. Drop any one of the three and it reads as a suggestion.
Weak: Please RSVP soon. Weak: Kindly respond at your earliest convenience. Weak: RSVP by 10/8.
Strong, casual:
Strong, semi-formal:
Strong, formal:
Strong, per function:
Your RSVP deadline is not your vendor's deadline. Put 7 to 10 days between them. If the caterer needs final numbers on the 20th, your guest-facing deadline is the 10th. That gap is the only room you get to run stages 3 through 5 of the chase below, and hosts who skip it end up sending the "final headcount" text on the same day they have to submit the number.
Saying what happens after the deadline raises response rates more than any amount of politeness. "After the 8th I have to give the venue a final number, so I may not be able to add anyone" is honest, non-punitive, and it converts.
This is the sequence, anchored to days before the event, for an event with a 14-day RSVP deadline. The response column is a planning assumption you can use to size an order. It is not research data, it is a rule of thumb for filling in a spreadsheet before the answers arrive.
| Days before event | What you send | Channel | Who gets it | Planning assumption (cumulative reply rate) |
|---|---|---|---|---|
| 28 | The invitation, with dated deadline and end time | Direct in-app invite, plus link | Everyone | Assume roughly half reply within 72 hours |
| 21 | Nothing. Quiet week on purpose | none | none | Drift up to roughly 60% |
| 14 | Deadline lands. Live count visible on the page | Passive | none | Assume roughly 70% by the deadline |
| 10 | First nudge, warm and light | In-app notification, plus email | Non-responders only | Recovers roughly a third of who's left |
| 5 | Second nudge, more direct, names the vendor | Text, plus in-app | Still-silent only | Recovers roughly half of the remainder |
| 3 (72 hours) | Final headcount call. Binary question | Text, then phone | Still-silent, plus every maybe | Assume 85 to 90% accounted for |
| 1 | Day-before confirmation | Text or in-app | Confirmed yeses only | Surfaces the late cancels |
| 0 | Nothing. Host your event | none | none | Assume a small walk-up |
Two rules govern the whole table. First, the segment shrinks at every stage. Second, the channel escalates. If both hold, five messages feel attentive. If neither holds, two messages feel like nagging.
Every script below is complete and ready to send. Replace the bracketed parts. They are grouped by stage, and within each stage by channel, so you can work straight down the timeline table above.
The message that carries the invitation matters as much as the invitation. All three of these state the end time and the deadline.
1. Text, casual
2. Email, semi-formal
3. Direct in-app invite note
Warm, short, zero guilt. This one catches the people who genuinely forgot. Send to non-responders only.
4. Text, close friend
5. Text, acquaintance or coworker
6. Email, batch to non-responders
7. In-app notification, non-responders
8. Per-function nudge, one function only
Now name the constraint. This is where you move from email to text for anyone under about 60.
9. Text, direct
10. Email, second and final email
11. In-app notification, still silent
12. Partial-attendance prompt
13. Family group chat, one message for the whole thread
Three days out you stop asking and start closing. Every message here ends in a binary question. Send to still-silent guests and to every maybe.
14. Text, binary close
15. Email, last call
16. Phone call script
17. Voicemail, 20 seconds
18. Relay through a partner or sibling
This goes to confirmed yeses only, never to non-responders. It is a logistics message that happens to surface late cancellations.
19. Text, confirmed guests
20. Email, confirmed guests with logistics
21. In-app, confirmed guests, per function
Plan on a small residue who will not answer email, text or app notification. As a planning number rather than a measurement, assume about 5 percent of your list. These three exist for them.
22. Phone call, older relative who doesn't use email
23. In-person ask
24. The final direct text, no link
That is 24 scripts: 3 initial invites, 5 first nudges, 5 second nudges, 5 final headcount messages, 3 day-before confirmations and 3 for the guests who answer nothing.
Send reminders to non-responders only. Everything else trains your guests to ignore you. The guest who replied on day one and then gets two more "are you coming?" emails concludes your messages are automated noise, and next time they will not open the first one either.
Filtering by response status is standard now. Filtering by response status within one function of one event is not, and it is where multi-part events fall apart.
Here is how nudge tooling compares, based on what each platform documents publicly. Mixily's own feature update posts from Spring and July 2026 are the source for its column; re-verify against current product before quoting.
| Nudge capability | Mixily (per its Spring 2026 and July 2026 update posts) | Lumhe |
|---|---|---|
| Reminder channels | In-app notification to guests you're connected with, plus a shareable link for any channel | |
| Ready-made reminder copy | Two: an "Are you coming?" nudge and a "See you tomorrow!" day-before message | Nudge reminders to non-responders |
| Segment by response status | Yes. July 2026 added checkboxes for Going, Maybe and Haven't responded yet | Yes |
| Segment by function inside one event | Not applicable. One event, one guest list | Yes. Each function has its own guest list and its own RSVP |
| Handling of "maybe" | Can be switched off entirely, leaving Yes or No (July 2026) | Kept, but usually unnecessary because partial attendance has its own answer |
| Invitation formats accepted from you | Event page with your photo and styling | Upload image (JPG/PNG), video, PDF or typed text |
| Template library | Design options on the event page | Not live yet. Coming soon |
Two honest notes on the Lumhe column. There is no template library yet, so if you want a platform to design the invitation for you, this is not the one. And the in-app notification only reaches guests you are connected with inside Lumhe, which is why connecting your list is the first step rather than an afterthought.
The guest who confirmed for the reception on day two never hears about the reception again. They only hear about the ceremony, which they haven't answered.
A maybe is almost never indecision. It is a guest whose real answer does not fit the form.
Break the maybes on your list into three groups and treat them differently:
| Type of maybe | What they actually mean | What to send |
|---|---|---|
| The scheduler | "I can make part of it, not all of it" | Script 12, per function |
| The waiter | "I'm waiting on flights, childcare or a shift swap" | Script 14 at 72 hours, binary |
| The soft no | "I don't want to say no to your face" | Script 15, with an easy exit |
Take a real shape of event. A wedding weekend with three functions: a Friday welcome dinner at 7 p.m., a Saturday ceremony at 2 p.m., and a Saturday reception at 6 p.m.
Your cousin's husband works Saturdays until 4. On a single-event tool, he has three buttons: yes, no, maybe. Yes is wrong, because he cannot be at a 2 p.m. ceremony. No is wrong, because he is absolutely coming to the reception. So he picks maybe, and you now have one useless data point covering three vendor orders.
With functions, he answers three times in about eight seconds:
| Function | His answer | What you can now do |
|---|---|---|
| Friday welcome dinner, 7 p.m. | Yes | Restaurant count plus one |
| Saturday ceremony, 2 p.m. | No | One fewer chair, no printed program |
| Saturday reception, 6 p.m. | Yes | Plate, place card, bar count |
Same guest, same constraints, three usable numbers instead of one maybe. Multiply by the twelve people on your list with a similar conflict and the difference is the entire accuracy of your catering order.
This is also why switching the maybe option off is a partial fix at best. It forces a guest with a genuinely partial answer to pick a wrong one. Giving them somewhere honest to put the real answer works better than removing the button they were reaching for.
After two nudges and one direct 72-hour ask, count non-responders as not attending and move on. You have done the work.
Not every part of your budget needs the same cushion.
| Line item | Buffer on top of confirmed yeses | Why |
|---|---|---|
| Plated catering | 3 to 5% | You pay per plate. Keep it tight |
| Buffet or family style | 5 to 8% | Cheaper per head to over-cater |
| Drinks | 10% | Cheapest thing on the list to have spare |
| Seating | 2 seats or 1 spare table | Flexible and free to hold |
| Place cards, programs, favours | 0% | Nobody who didn't reply expects one |
| Venue capacity | 0% | It's a legal limit, not a suggestion |
Mixily's own wedding guide cites RSVPify data putting non-response at 10 to 15 percent of invited wedding guests. Treat that as a starting assumption to be re-verified at source rather than a fact about your list, and check it against what actually happened at your last event.
Email your vendor the number and keep the email. "Our final confirmed count is 112. Please plan to that figure." A phone call is not a record.
Use a three-stage funnel rather than one rate: invited, responded, attended. The numbers below are planning rules of thumb for a local weekend event, offered so you have something to put in a spreadsheet before the answers arrive. They are not survey findings, and your own last event is a better guide than any of them.
| Funnel stage | Planning rule of thumb | Worked example, 100 invited |
|---|---|---|
| Replied by the deadline | Assume about 70% | 70 replies |
| Replied after two nudges and a direct ask | Assume about 90% | 90 replies |
| Never reply at all | Assume the remainder | 10 silent |
| Said yes, of those who replied | Assume 70 to 80% for a local event | 63 to 72 yeses |
| Actually attend, of the yeses | Assume 90 to 95% | 57 to 68 attending |
| Turn up without replying | Assume 1 to 3% of invited | 1 to 3 |
Adjust down hard for anything requiring travel, a weekday date, or a guest list drawn mostly from work. Adjust up for a small list of close friends, a recurring event people already love, and any event where the yes list is visible.
Track your own three numbers after each event. Two events in, your own history beats every benchmark in this article.
Copy this table into a doc or sheet. One row per household, one column per function. The last two columns are the ones that stop arguments with yourself at 11 p.m.
| Household | # in party | Welcome dinner | Ceremony | Reception | Last contact (date + channel) | Counted as | Notes |
|---|---|---|---|---|---|---|---|
| Okonkwo | 2 | Yes | Yes | Yes | Aug 2, in-app | 2 | No nuts |
| Priya + guest | 2 | No | Yes | Yes | Aug 4, text | 2 | Vegetarian |
| Delgado | 4 | Yes | No | Yes | Aug 9, text nudge 2 | 4 | 2 kids, high chairs |
| Whitfield | 1 | No reply | No reply | No reply | Aug 11, phone, voicemail | 0 | 3 attempts, closing as no |
| Function totals | 8 | 12 | 16 |
Three things make this version work. Per-function columns, so you are not resolving a maybe in your head. A last-contact column with the channel, so you know whether you have earned the right to call. And a "counted as" column that is a decision, not a status, so the number you send the caterer is a number you chose.
The RSVP list you fought for is also your thank-you list and your photo list. Use it before it goes cold.
On Lumhe, Moments is a shared photo timeline for the event. Guests upload their photos and everything collects in one place, per event. It is not a group chat and not a Story. It does not expire, and it is still there after the event ends, which is the whole point. Send the same link to the people who attended each function and the timeline builds itself.
If money gifts are part of your occasion, Digital Lifafa handles them without you posting bank details in a group chat. You add your payment ID, whether that is Venmo, Zelle, Cash App, PayPal or a bank transfer. The guest pays from their own app, uploads the receipt, and it arrives wrapped in a digital envelope you open. Lumhe never touches the money.
Name the date, give the reason, and make either answer easy. "Could you let me know by Thursday? I'm ordering food Friday morning, and a no is genuinely fine." The reason is what makes it polite rather than pushy, because it shows you are asking for a practical purpose and not for reassurance. Scripts 4 through 9 above are all built on that shape.
Three targeted messages plus one direct personal ask is the ceiling. That means a first nudge at 10 days, a second at 5 days, a binary question at 72 hours, and one call or in-person ask for anyone still silent. The rule that keeps it from feeling like harassment is segmentation: each message goes to a smaller group than the last, and nobody who has answered ever gets nudged again.
Text gets answered, email gets ignored, and the last few people need a voice. Use email for the first batch nudge because it carries detail and links well, switch to text at the 5-day mark for anyone under about 60, and pick up the phone at 72 hours for the handful still missing. An in-app notification from the platform sits usefully between email and text, because it arrives where the invitation lives rather than in an inbox.
Only one, the day before, and only about logistics. Confirmed guests should never receive an "are you coming?" message, because it tells them their answer wasn't recorded and teaches them to ignore your next reminder. The day-before message is different: it carries parking, timing and arrival detail, and it quietly surfaces the cancellations you would otherwise discover on the day.
Ask a binary question at 72 hours, and if they still don't answer, count them as not attending. Before that, check whether their maybe is actually a partial yes: if your event has more than one part, they may be able to make one function and not another, and giving them a per-function answer resolves it immediately. A maybe that survives a direct yes-or-no question at 72 hours is a no in practice.
Three to four weeks for casual events, six to eight weeks for weddings and milestone celebrations, and eight to ten weeks for anything with multiple functions or guests who need to fly. Send Tuesday through Thursday. Earlier is not better past those windows, because an invitation that arrives three months out gets filed and forgotten, and you end up running the whole reminder sequence anyway.
Yes, if your platform supports functions inside one event. On Lumhe you add each function separately with its own date, time, venue and guest list, so the sixty people at the ceremony and the hundred and forty at the reception are two lists inside one invitation, each with its own RSVP count. On single-event tools you would have to create separate events and reconcile the guest lists by hand, which is where duplicate and missed invitations come from.
As a planning assumption, expect roughly 70 percent to reply by the deadline and roughly 90 percent after two nudges and a direct ask, with the remainder never replying. Of those who reply yes to a local event, assume 90 to 95 percent actually attend. Those are rules of thumb for sizing an order, not measured figures, and after two events your own numbers will be more accurate than anyone else's.
Planning a celebration with more than one function? Upload the invitation you already made to Lumhe, whether that is an image, a video, a PDF or typed text, then find and connect with your guests by name, phone number or email inside Lumhe and send it to them directly. Add each function separately, so the welcome dinner and the reception have their own guest lists and their own RSVPs, and you always know the headcount for each one. Nudge only the guests who haven't answered, per function, so nobody who already said yes gets chased again. After the event, everyone's photos collect in Moments, a shared timeline that does not expire. Guests who want to send money instead of a gift can do it through Digital Lifafa. You add your payment ID, they pay from whichever app they already use and upload the receipt, and it arrives wrapped in a digital envelope you open. Lumhe never touches the money. You can also share your invitation link on WhatsApp, iMessage, Instagram or any other platform. Explore Lumhe.
| Keyword | Type | Placement |
|---|---|---|
| how to get people to rsvp | Primary | H1, intro, "The 12 tactics at a glance", "Your follow-up timeline" |
| why people don't rsvp | Secondary | H2 "Why people don't RSVP: five real reasons, and the fix for each" |
| rsvp reminder message examples | Secondary | H2 "24 copy-paste reminder, nudge and last-call scripts", stages 2 and 3 |
| how to ask for an rsvp politely | Secondary | FAQ "How do you politely ask someone to RSVP?"; scripts 4 to 6 |
| rsvp deadline wording | Secondary | H2 "RSVP deadline wording that people actually respect" |
| increase rsvp response rate | Secondary | "Make responding one tap"; "Response-rate benchmarks: invited, responded, attended" |
| when to send invitations | Secondary | H2 "When to send: timing windows by event type and by function"; FAQ on advance notice |
| what to do when people don't rsvp | Secondary | H2 "What to do when people still don't respond"; "Your copy-paste final headcount tracker" |
| rsvp reminder text message | Secondary | Scripts 4, 5, 9, 14, 24; FAQ "What's the best channel for an RSVP reminder, text or email?" |
| per-function rsvp | Secondary | "Reminding only the guests who haven't answered, per function"; "Handling maybes and partial attendance" |
Find and connect with guests by name, phone, or email. Manage multi-event schedules with individual RSVP headcounts for each ceremony or gathering, collect shared memories in permanent Moments timelines, and receive blessings through Digital Lifafa wrappers.
Explore Lumhe for FreeDesign a beautiful event invitation in seconds and share it with a link — free, no app needed.
You have a guest count and a card you like. You want one number. The reason you cannot find one is that the Paperless Post cost for a wedding is quoted three di
An online RSVP is a link that asks one question and stores the answer where you can count it. That is the whole idea. Everything else in this guide is about the
There is a standard argument for hosting events off social media, and it goes like this. You do not own your followers. A ranked feed decides who sees your post