RSVP wording — the ask, the reminder and the decline

What a reply has to collect before it is any use

RSVP wording fails for one reason more often than any other: it asks a question whose answer you cannot use. Let us know if you can make it comes back as a yes, and a yes is not a number, a menu or a note about a nut allergy. Four weeks later you are messaging the same forty households again, one at a time, to ask the things you could have asked once.

A reply earns its place when it collects five things in a single pass:

• whether they are coming — the only part most invitations bother to ask for
• how many people, named where you can get names, because plus one eventually becomes a chair and a plate
• which menu, including the meat-free option, the gluten-free one and the children's
• what they cannot eat — an allergy is not a preference, and the kitchen needs it in writing
• anything else you should know — arriving after the ceremony, leaving before the cake, a toddler who needs a high chair

Those five answers turn into the four numbers everything downstream runs on: the headcount your venue charges for, the total per menu option the restaurant asks for about a week ahead, the chairs the seating plan has to find, and the list somebody ticks off at the door on the day. All four are decided by a sentence you write once, months earlier.

RSVP wording that gets an answer, not a yes

Ask for all five things in one long sentence and most guests answer none of them. Ask in the order above, one short line at a time, and they answer in order. That is most of the craft.

The rest is the verb. We hope you can make it is a sentiment; nobody has to do anything about it. Please reply by 1 August is an instruction with a date attached. Name the date, name where the reply happens, and say roughly how long it takes — people postpone a task with no edges and complete a one-minute one.

The formal version keeps the register of a formal invitation and still asks for all five things:

Kindly reply by Saturday, 1 August 2026.
Please tell us how many of you will attend,
which menu you would like, and anything you are unable to eat.

The warm version, for a page written in your own voice, is allowed to say the quiet part — that replying is a favour and that it spares you a hundred separate conversations:

Let us know by 1 August 2026 whether you can be with us:
how many of you there will be, whether any children are coming,
and what you would rather not find on your plate.
It takes a minute, and it saves us a hundred messages.

Then there is the message you send alongside the link, which is not the same text as the one on the page. On WhatsApp your invitation lands in a thread with forty unread messages above it, so the line that carries it has to say who, when and what to press:

Sarah and Tom are getting married on 12 September 2026, and you are invited.
Everything is on this page — both ceremonies, the addresses, the map.
The Confirm button is at the bottom; pick your menu while you are there.
Replies close on 1 August.

Send that to each household separately rather than to a group. In a group thread a reply becomes public, so anyone who needs a moment to think decides to answer later, and later is a synonym for never.

The deadline, and why it is not an arbitrary date

Set the reply date four to six weeks before the event, and set it for a reason you can name out loud. Your venue asks for final numbers at a fixed point — often a week to ten days out, sometimes a fortnight for a plated menu — and you need the gap between the two deadlines to chase the people who said nothing, move them into the count, and build the tables around whoever is real.

Work backwards from the venue's date, not forwards from today. Then adjust for the calendar: a deadline that lands on a bank-holiday weekend is read the following Tuesday, one that falls in half-term is read when the family gets home, and a Sunday deadline is answered on Monday by everyone who meant well. A Wednesday or Thursday gives you the weekend before it as the last honest window.

Resist the temptation to publish a date earlier than the one you need, as insurance. It only works once. Guests who reply on the day you asked and then watch nothing happen for a month learn that your dates are soft, and the second deadline — the one that is genuinely final — arrives with no force behind it. Put the true date in three places instead: the closing of the invitation, the message that carries the link, and every reminder you send. One date, spelled out the same way, three times.

Chasing without nagging

Two chases is the right number. The first goes out about ten days before the deadline, while there is still time to be relaxed about it. The second goes out in the deadline week, and it is allowed to be direct, because by then you are asking for something you actually need on a specific day.

Both go to individuals, not to the room.

Never send the chase as a group message. The people who replied the day they received the invitation read a blanket reminder as proof that answering promptly counted for nothing — and they are exactly the people whose help you will want in the last fortnight.

The first reminder assumes forgetfulness, because it usually is forgetfulness. Give the reason, give the route back to the page, and remove the sense that an answer is a commitment carved in stone:

Hello Anna — no rush, just a reminder that we close the numbers on 1 August.
If you open the invitation again, the Confirm button is at the bottom of the page.
It takes a minute, and you can change the answer later if your plans move.

The second one names the consequence and makes a no as easy to give as a yes. That last sentence is what unblocks the people who have been avoiding you because they think a refusal will be a disappointment:

Anna, we hand the restaurant the final count on Monday.
Could you tell me by Sunday evening whether you are coming, and with how many?
A no is completely fine — I just need a number I can pass on.

After the second reminder, stop writing and either telephone or let it go. A guest list that marks each person as invited, confirmed, declined or still silent means you are chasing the eleven people who owe you an answer rather than broadcasting to all forty, and it is worth grouping them by household first — one message to a family is one message, not four.

Wording a decline, and receiving one well

Half of RSVP etiquette is about the answer nobody enjoys giving, which is why so many people give no answer at all. A good refusal has three properties: it arrives quickly, it does not over-explain, and it does not leave the door ajar. We'll try to make it is the worst possible reply — it holds a seat, a meal and a place at a table hostage, and it postpones the same conversation to a week when the host has no room for it.

The warm version, for people you are close to, says no once and then offers something real instead:

Sarah, thank you for the invitation — it means a lot that you thought of us.
We can't be there on 12 September; we're away that whole week and it can't be moved.
We'll be thinking of you both, and we'd love to take you to dinner when you're back.

The short version, for a colleague or a distant cousin, does the job in two lines and needs no reason at all. A reason invites a negotiation; the absence of one closes the subject kindly:

Thank you for the invitation. Unfortunately we won't be able to come on 12 September.
We wish you both a wonderful day.

If you are the one receiving it, answer the same day, and answer with gratitude rather than with disappointment. A no eleven weeks out is a seat you can offer to somebody else. A no on the Thursday is a plate the venue has already billed you for:

Thank you for telling me, Anna — knowing early genuinely helps.
We'll miss you on the day. Let's find a date in October.

Plus-ones and children: the two questions nobody asks out loud

On paper, the envelope did this work: whoever was named on it was invited, and everyone understood the convention. A link forwarded on WhatsApp has no envelope, so the page and the message have to be explicit or the guest will guess — usually generously.

Say the number in the covering message, not in the small print. We've kept a place for you and Michael answers it without a rule being quoted at anybody. So does this one is just for you — it's a small room, and we wanted the people we see most. If the whole day is adults-only, that belongs in the same sentence as the invitation itself rather than three screens down: we're keeping the evening child-free, and we hope that gives you a night off.

Children are worth asking about separately, because "2 people" hides whether the second person is four years old. A children's menu, a high chair and a seat at the right table all follow from that one detail, and the only reliable way to learn it is to make the children's option a visible choice in the reply rather than something a parent has to think to mention. The same is true of allergies: nobody volunteers coeliac disease in a WhatsApp message, but almost everybody ticks it when a field asks. If you want the wording for the list itself — who goes on it, who quietly does not, and how to keep both sides of a family from counting — building the guest list is a job of its own.

What the answers turn into

The reason to collect replies in one place rather than in your messages is that every answer has three lives after the yes. The menu choices add up to a total per option, which is the number the restaurant asks for a week before the day and the number you cannot reconstruct from memory. The confirmations become the pool the seating plan is built from, so you are moving real people between real tables instead of pencilling in maybes. And the same names become the list at the door, ticked off from a phone as people arrive, walk-ins included, so at any point in the evening you know who is in the room.

That is the argument for the reply living inside the invitation rather than behind an email address: an address gets you sentences, and sentences have to be transcribed. A button gets you a row — the answer, the headcount, the menu, the allergy, the time it arrived — for every guest, in the same shape. It is worth opening a design with your own names and dates before you finalise any of this wording, because the closing section of the page is where the ask actually lives, and it is easier to write a sentence when you can see how much room it has on a phone.

When an answer changes after the deadline

Some of them will. A guest who declined in June gets the weekend free in August; a couple who confirmed for two arrive as one. This is the part where a printed reply card has nothing to offer and a link does: the invitation stays live and editable after you have sent it, so an answer can be revised, and the number that matters is simply the last one recorded before your venue's cut-off.

Handle late changes with one rule, stated in advance and applied to everybody: after the final count goes to the restaurant, a change is a request rather than an update. Most venues will add a person in the last week and very few will remove one, so a late no lands on you and a late yes usually does not. Saying that once, in the second reminder, is fairer than deciding it case by case at midnight.

If it is your details that change rather than a guest's — a ceremony hour that moves, a restaurant that falls through — correct the page once and everyone opening the same link sees the new version, then send a short message asking anyone affected to confirm again. That is also the moment to check your reply date still makes sense against the new plan; when to send the invitations works backwards from the same calendar, and the closing lines that carry the ask are written out in full in the guide to wedding invitation wording.