Wedding Guests Not RSVPing? The 2026 Follow-Up Timeline, 18 Scripts, and How to Chase Per-Function Headcounts

Here is what to do when wedding guests don't RSVP: work backwards from the earliest final-count date in your vendor contracts, set one guest-facing deadline at least ten days before it, then chase the silence in four escalating rounds where each round goes to a smaller list than the one before.

That last part is where most wedding advice stops being useful. It treats your wedding as one yes-or-no question. A 2026 US wedding weekend is usually four questions: the welcome party, the ceremony, the reception and the Sunday brunch, each with its own venue, vendor, final-count date and often its own guest list. Chase all four with one list and you nudge people who already answered, miss the guest who owes you the brunch only, and hand your caterer a number you do not believe.

This guide fixes that. Week-by-week timeline, 18 copy-paste scripts sorted by who you are chasing, the per-function chase, and the vendor math at the end.

Key takeaways

• One deadline rule, no exceptions: your guest-facing RSVP deadline sits at least 10 days before the earliest final-count date written into any of your vendor contracts, never on it. Some published wedding advice states both versions of this rule in consecutive lines. Only the earlier date works, because that gap is the only room you get to chase.
• Chase in four rounds, each to a smaller segment: warm nudge, deadline-day nudge, vendor-named nudge, then one direct personal ask. Four rounds to a shrinking list is attentive. Two rounds to the whole list is nagging.
• A weekend wedding has one non-responder list per function, not one for the wedding. The guest who confirmed the reception on day two should never get another reception reminder.
• Your parents' guest list is your parents' chase. Assign it to them in writing with a date, because you often do not have those phone numbers and they always do.
• A partial answer is a usable number. "Reception yes, ceremony no" fills a plate count and empties a ceremony chair. A single-event "maybe" fills nothing.
• Buffer by line item, not by wedding: roughly 3 to 5% on plated dinner, 5 to 8% on buffet, about 10% on bar, and 0% on escort cards, favors and venue capacity.

Why wedding guests go quiet, including the multi-function confusion nobody names

Guests go quiet for five reasons, and only one of them is about you. Naming the right reason tells you which script to send.

1. They meant to reply and the invitation left their hands

The most common cause. They opened it on a phone, between two other things, thought "we should check the flights," and closed it. A single warm nudge recovers most of this group, which is why round one is warm and never mentions vendors.

2. They do not know an answer yet, and there is no honest button for "not yet"

Travel costs, childcare, a shift they cannot swap. Faced with yes, no and maybe, a guest with a real constraint often picks nothing, because "maybe" feels like a lie and "no" feels final. Give them somewhere to put the truth and they answer.

3. They do not know your deadline is real

To you the caterer's final-count date is a live threat. To your college roommate it is an abstraction, because guests do not know a headcount closes weeks before the wedding. Round three exists to say the sentence that fixes this: the vendor's name and the date.

4. Nobody in your household has their phone number

This is the parents'-friends problem, invisible in most guides. Your mother invited nine couples you have met twice, and they were never in your phone. They will not RSVP to a link they never received. This is a delegation problem, not a wording problem, and it gets its own section below.

5. The multi-function confusion nobody names

Here is the cause of most silence in a modern wedding weekend. It looks like rudeness and it is a form-design problem.

Your guest gets one invitation covering a Friday welcome party, a Saturday ceremony and reception, and a Sunday brunch. They can come to the reception. They cannot make the ceremony, they are unsure about the brunch, and they cannot tell whether the welcome party is a real invitation or a courtesy mention. One button, four answers, no way to send the true one. They put it down to think about it, and you read that as being ignored.

If your invitation cannot take four separate answers, your guests cannot give you four separate answers, and the "non-response" you are chasing is partly a form you designed.

The one deadline rule, stated once

Set your guest-facing RSVP deadline at least 10 days before the earliest final-count date in any of your vendor contracts. Fourteen days is more comfortable. Never set it on the cutoff date.

That is the whole rule, and it will not be contradicted anywhere else in this guide. If two lines of wedding advice tell you both to build a buffer and to set your deadline the same week the caterer needs numbers, one of those lines is a stripped "don't" and it will cost you the chase.

Work backwards from the contract, not from a blog

Do not use a generic lead time. Open the documents you have already signed and write down the final-count date each one names. Mixily's guide on non-responding guests cites The Knot for a 10 to 14 day caterer window, with some venues asking three to four weeks; treat any published figure as a starting point to re-verify against your own contract.

Then take the earliest date on your list. That date, minus 10 to 14 days, is your guest-facing deadline. If the welcome-party restaurant needs numbers 21 days out and the caterer needs them 14 days out, you work to 21.

One deadline or one per function?

Both work. Pick by how different your guest lists are.

If you stagger, say so in one line on the invitation, because a guest who answers one function and assumes they are done is a non-responder you created.

Your week-by-week follow-up timeline

This is the sequence for a wedding whose earliest vendor final-count date is 14 days out, with invitations mailed eight weeks ahead. Shift every row by the same amount if your earliest cutoff is different.

Two rules make this feel considerate rather than relentless. The segment shrinks every single round. The channel escalates from in-app to email to text to voice. Break either rule and four messages become four annoyances.

For the general version of this sequence across any event type, with 24 non-wedding scripts, see our guide on how to get people to actually RSVP. The scripts below are the wedding-specific set.

18 copy-paste chase scripts by relationship and channel

Every script below is complete. Replace the bracketed parts and send. They are grouped by who you are chasing, because a bridesmaid and your mother's book-club friend are silent for different reasons and the same wording does not work on both. Pick the channel by how you already talk to that person; escalating to a phone call with a cousin you text daily reads as an emergency.

Close family (scripts 1 to 3)

Script 1. Text, round 1, warm. Nothing about vendors yet.

Script 2. Phone call, for a grandparent, aunt or uncle who does not use links. End on a binary question so the call cannot end in "we'll see."

Script 3. Text, round 4, for a sibling or close cousin who owes you two answers. Direct, affectionate, and it makes the cost visible without making them the villain.

Wedding party (scripts 4 and 5)

Script 4. Text to a bridesmaid or groomsman with an outstanding rehearsal-dinner answer. They assume being in the wedding party is the answer. It is not, because the restaurant needs a number.

Script 5. Wedding party group thread, per-function roll call. Public, light, and effective because nobody wants to be the one name left blank.

Friend group (scripts 6 to 8)

Script 6. Text, round 1, one friend who has gone quiet. Assume logistics, not rudeness.

Script 7. WhatsApp, friend-group thread. Name the function and the people, because a thread nudge aimed at everyone is aimed at nobody.

Script 8. Text, round 3. This is the script that names the vendor and the date. It is the highest-converting message in the whole sequence and it only works once, so do not spend it early.

Parents' friends and guests you cannot reach (scripts 9 to 11)

Script 9. Message to your parent, delegating their own list. Send it in writing with a date, not as a comment during a phone call, because a verbal delegation produces no list.

Script 10. Email, formal register, to a family friend or older guest you are contacting for the first time. Identify yourself in the first line. They may not have your email in their contacts.

Script 11. Phone call to an older guest who has not replied to anything. Slow, unhurried, one question at a time.

Plus-ones (scripts 12 and 13)

Script 12. Text to a confirmed guest whose plus-one is still nameless. The name matters for the escort card, the dietary list and the seating chart.

Script 13. Text directly to a plus-one whose number you do have. Do this only when the primary guest has already confirmed and has told you to reach out.

Partial attendance and unresolved maybes (scripts 14 and 15)

Script 14. Text to the guest who can only make part of the weekend. This turns a useless maybe into three usable numbers.

Script 15. Text, round 4, to a destination-wedding guest waiting on flights. Give them a hard fork instead of an open question.

In-app nudges (scripts 16 and 17)

Short, function-scoped, and only ever sent to the people who have not answered that specific function.

Script 16. First in-app nudge, one function outstanding.

Script 17. Final in-app nudge for that function.

Closing the door (script 18)

Script 18. Post-deadline note to everyone who never answered. Send it once. It converts a surprising number of people, and for the rest it is the cleanest possible ending.

Chasing per-function RSVPs without nudging the same guest four times

Send each reminder only to the guests who still owe you an answer for that specific function. This is the single rule that separates a chase your guests tolerate from a chase they mute.

Filtering a guest list by "no response" is standard on every digital invitation tool. Filtering by no response inside one function of one wedding is not, and that is where a weekend wedding breaks.

What the wrong version actually looks like

Most couples end up with one event page for the welcome party, another for the ceremony and reception, and a spreadsheet for the brunch. The chase then looks like this:

• Open dashboard one, filter non-responders, write a reminder, send.
• Open dashboard two, filter non-responders, write a similar reminder, send.
• Open the spreadsheet, cross-reference by hand, text the leftovers.
• Discover you have texted your cousin three times in a week about three different things, and she has already replied to two of them.

The work triples and the guest experience gets worse at the same time. Your cousin does not see three tidy function reminders. She sees a couple who cannot keep track.

What the right version looks like

One event. Each function inside it has its own date, time, venue, guest list and RSVP. One guest, four answers, four independent counts.

This is what Lumhe is built around. Sub-events sit inside a single event and RSVP tracking is per function, so the non-responder list is always scoped to the function you need numbers for. Nudge reminders go only to the guests who have not answered that function, and the real-time count per function is the number you hand that function's vendor.

Reaching people works the same way. Find your guests inside Lumhe by name, phone number or email, send a connection request, then send the invitation and every nudge to them directly. Every invitation also generates a shareable link for WhatsApp, iMessage, Instagram or email, which is how the parents'-friends list usually gets covered.

The practical flow, in order:

1. Upload the invitation you already made: image, video, PDF or typed text. Lumhe does not design it for you and there is no template library live yet, so bring the file you made in Canva or wherever you made it.
2. Add each function separately with its own date, time and venue.
3. Build a guest list per function. Different guests can be invited to different functions, which is what makes the welcome party a real invitation rather than a courtesy mention.
4. Watch the counts per function in real time.
5. At each round in the timeline, nudge the non-responders for one function only.

If you are still deciding how to hold the whole list together, our walkthrough of free ways to track wedding RSVPs covers the tracking side.

What reminder tooling costs, and which tools can chase per function

Cost matters less here than whether the tool can send a reminder scoped to one function, because that is the thing you will do eight or ten times in the next month.

Every third-party figure below is the platform's or a cited source's own published claim, reproduced as published and flagged for re-verification. We do not have a live price check in this draft. Confirm current pricing on each vendor's site before you buy, and note that at least one competing wedding guide has figures that contradict each other in places.

Two honest limits on the Lumhe column. There is no live template library, so if you want the platform to design the invitation, this is the wrong tool. And the in-app nudge only reaches guests you are connected with inside Lumhe; anyone else gets the shareable link instead.

The parents'-friends problem: guests whose contact details you never had

Delegate this list. Do not try to chase it yourself, because you cannot: the phone numbers live in your parents' phones and the social obligation lives in your parents' friendships.

This block is the one most likely to be sitting at zero response two weeks before your deadline, and the one where a wrong-tone message from you causes the most family fallout.

The delegation that actually works

Three details make it work. Give each parent a short list rather than the whole spreadsheet, because a long list produces no calls. Ask per function, because "the Kapoors are coming" does not tell you whether they are at the brunch. And put the return date in the message, because a chase with no date is a favor with no deadline.

When your parent's list comes back as a headcount

If a parent hands you "about fourteen from my side," that is not a number, it is a mood. Ask for names. A caterer cannot plate fourteen unnamed people and a seating chart cannot hold them.

Plus-ones, and the answer that isn't an answer

A confirmed guest with an unnamed plus-one is a half-answer, and it is the most common gap in an otherwise clean list.

You need three things from a plus-one and only the first is a headcount: are they coming, what is their name, and what do they eat. Escort cards, place cards and the kitchen list all need the name. Chase it once, at 16 days out, with script 12.

Rules that stop the plus-one chase from spiraling

• Write "and guest" on the invitation only if you are willing to print "and guest" on the escort card. If you are not, you have to get the name.
• A plus-one who has not been named by your submission date is still a plate. Count them, name them "Guest of [Name]," and move on.
• If your guest downgrades to solo after you have submitted, tell the venue. That is a released plate, not an admin detail.
• Never invite a plus-one directly unless the primary guest has said you can. Script 13 exists for the case where they have.

What a partial yes does to your seating chart

A partial yes is a gift, because it fills one number and empties another on the same line. A single-event maybe fills neither.

Your partner's cousin works Saturdays until four. On a one-button tool he chooses yes, no or maybe for the whole wedding, all three are wrong, so he picks maybe, and one ambiguous data point now sits across four vendor orders.

Give him four answers and the same eight seconds produces this:

Four usable numbers instead of one maybe. Multiply that by the ten or twelve guests on a typical list with a similar conflict and the difference is the accuracy of your entire catering order.

Seating chart specifics

• Build the chart from the reception list only. Ceremony attendance and reception attendance are different numbers and mixing them is how a table ends up one chair short.
• Lock the chart 10 days out, not on the day you submit catering. You want the chart to survive one round of late changes without a rebuild.
• Keep one flexible table of eight with no escort cards assigned. It absorbs the late yes, the walk-up and the seating emergency you did not predict.
• Kids' meals are a separate count. Ask ages as well as headcount, at the same time you chase the plus-one names.

Handing per-function numbers to the caterer, venue and rehearsal-dinner restaurant

Send every final count in writing, to the person named in the contract, with the function named. A number given on a phone call is not a record and it will not protect you in a billing dispute.

Each function has its own vendor and its own date. Confirm each one against your contract; the lead times below are typical ranges you should verify, not promises.

The email that closes it

Ask those two questions in writing every time. The answer tells you exactly how long your flexible table stays useful.

When to count a non-responder as a no, and how much buffer to add

Count them as a no after two targeted nudges and one direct personal ask, with the dates written down. Three documented attempts across two channels is more than etiquette requires and enough that you will not second-guess it at midnight. Then stop: a fourth message to someone who has ignored three costs you the relationship and buys you nothing.

Buffer by line item, not by wedding

A single flat buffer across your whole wedding is either wasted money or an underfed table. Buffer the things that are cheap to have spare and do not buffer the things nobody misses.

Mixily's guide cites RSVPify data, drawn from more than 500,000 digital wedding RSVPs, putting complete non-response at an estimated 10 to 15% of invited guests, and states that 57.6% of RSVPs arrive in the first five weeks. Re-verify both at source and treat them as a starting assumption for a spreadsheet, not a description of your guest list.

Destination and travel-heavy weddings

Expect a lower yes rate and slower answers, and build the timeline earlier rather than adding more messages. The same Mixily guide cites RSVPify (2024) for a median destination-wedding attendance rate of 43%, against 78 to 82% for a local Saturday wedding; re-verify before you plan a budget around it.

Three practical adjustments for a travel-heavy list:

• Send invitations 12 weeks out rather than eight, so flight prices force an honest answer inside your window.
• Ask for a flight-booked confirmation as a separate checkbox from the RSVP. A yes without a booking is a maybe wearing a costume.
• Use script 15's two-column fork at round four. Open-ended questions get open-ended answers from guests who are waiting on a price.

The emotional weight of chasing family

Chasing family is harder than chasing friends, and the reason is worth naming: with a friend you are asking about a plate, and with family you are pressing on a relationship you have to keep afterwards.

The aunt who will not answer may be waiting to see whether her sister is coming. The brother blank for three weeks may be short of money for the flight and unwilling to say so. Silence in a family carries information, and the script that works is the one that gives them an easy no.

Four things that reduce the cost of this part:

• Give every ask an explicit exit. "A no is genuinely fine" is not a formality. It is the sentence that gets you the answer, because most family non-responses are unspoken nos.
• Split the chase by side. You chase yours, your partner chases theirs. This one rule prevents most of the in-law friction in the whole process.
• Delegate upward, not sideways. Parents chase their own guests. You do not become the enforcement arm of a guest list you did not write.
• Write down each attempt with the date and channel. When someone turns up anyway, or complains later that they were never asked, you will want the record. It is also what lets you stop.

You are allowed to stop. Three documented attempts, a decision, and your attention goes back to the wedding.

After the wedding: photos, thank-yous, and the list you already built

The per-function list you fought for is your thank-you list and your photo list. Use it in the first week, while it is still accurate.

• Within 48 hours: a short message to everyone marked attending. One line is enough.
• Within two weeks: thank-you notes for gifts, plus a separate note to anyone who traveled far or helped with setup. Your per-function list tells you who was at the welcome party, usually the group that did the most work.
• The photos: this is where most weekends lose the evening. Pictures scatter across a group chat that scrolls away, forty camera rolls, and Stories that expire in a day.

Moments on Lumhe is a shared photo timeline for the event. Guests upload their photos and everything collects in one organised place. It is not a group chat and not a Story, it does not expire, and it is still there after the wedding. Because the timeline is tied to the event, the Friday welcome party photos land in the same place as the reception ones.

If money gifts are part of your celebration, Digital Lifafa handles them without anyone posting bank details in a family group chat. You add your payment ID, whether that is Venmo, Zelle, Cash App, PayPal or a bank transfer. Your guest pays from whichever app they already use, uploads the receipt, and it arrives wrapped in an occasion-themed digital envelope that you open. Lumhe never touches the money; it is a direct transfer between your guest and you.

Frequently asked questions

Can you assume no RSVP means no?

Yes, after two targeted reminders and one direct personal ask, with the dates recorded. Three attempts across two channels gives the guest every reasonable chance. Mark them as not attending, add the line-item buffers above, and send script 18 so the ending is clean rather than ambiguous.

How many times should you follow up on an RSVP?

Four rounds maximum, each to a smaller list than the last: a warm nudge at 35 days, a deadline-day nudge at 26, a vendor-named nudge at 21, and one direct personal ask at 18. Never send a fifth. What keeps four rounds from feeling like harassment is segmentation, not politeness: nobody who has answered a function is ever nudged about it again.

When should the wedding RSVP deadline be, relative to the caterer's headcount?

At least 10 days before the earliest final-count date in any of your vendor contracts, and 14 is more comfortable. Work from the contract rather than a generic figure, since the welcome-party restaurant often needs numbers earlier than the caterer. That gap is not slack; it is the only window the four chase rounds fit into.

What do I do about a guest who says they can come to the reception but not the ceremony?

Record it as two separate answers, because it is two separate numbers. One fewer ceremony chair and one more reception plate is a genuinely useful pair of facts, and a platform with per-function RSVP will hold it for you without a spreadsheet. This is the case where a partial answer beats a maybe outright.

Who should chase my parents' guest list?

Your parents. They have the phone numbers, the relationships and the standing to call, and most of that list was never reachable by you anyway. Hand each parent their own names in writing with a return date four days before your submission date, ask per function, and count anything still blank as a no.

How much catering buffer should I add for no-shows?

Roughly 3 to 5% over confirmed yeses for a plated dinner, 5 to 8% for a buffet, and about 10% on the bar. Add nothing for escort cards, place cards, favors or welcome bags, since a guest who never replied is not expecting one, and add nothing to venue capacity because that is a legal limit. Buffer the cheap things generously and the expensive things narrowly.

Should I nudge someone who already RSVP'd for one event but not another?

Yes, but only about the function they have not answered. Reference the answer you already have in the first line, the way scripts 4 and 16 do, so the message reads as organised rather than forgetful. Nudging a guest about a function they have already confirmed is the fastest way to train them to ignore you.

What if a guest who never RSVP'd turns up on the day?

Tell your coordinator or banquet captain immediately and let them solve it, which is usually straightforward if you kept a flexible table and a bar buffer. Greet the guest warmly and say nothing about the RSVP on the day. Deal with any per-cover charge after the wedding.

Planning a wedding weekend? 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 party and the reception have their own guest lists and their own RSVPs, and you always know the headcount for each one. When you need to chase, the nudge goes only to the guests who have not answered that specific function. After the wedding, 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.