How to ask wedding guests to RSVP
Give guests a clear deadline, the exact response method and an easy way to answer yes or no. “Please RSVP by 12 May using the link below, even if you can’t attend” is more useful than “Let us know soon.” If the deadline has passed, contact missing guests directly and state when you need a final answer.
Please let us know by 12 May whether you can attend, using the RSVP link on your invitation.
We’d love to celebrate with you. Please reply by Friday with a yes or no for each person named on the invitation.
A quick reminder that RSVPs are due this weekend. Please respond even if you’re unable to join us.
An RSVP request is a planning question, not a demand that the answer be yes. Make it comfortable for guests to decline so they do not avoid replying because they feel they need a perfect explanation. Keep attendance separate from extra information where possible, while clearly stating any meal or access details you need at the same time.
On this page: Make the original request usable · Reminders before the deadline · Following up after the deadline · Handling uncertain or incomplete replies · Close the list clearly · Questions people ask
Make the original request usable
A good request tells guests what to do, where to do it and by when. If you accept responses through a website, include the working link. If you want a text reply, say who should receive it. Avoid sending guests between several channels that each appear to be the official one.
Please use the wedding website to RSVP by 12 May. If the form gives you trouble, message me and I’ll help record your answer.
Please return the enclosed reply card by the date shown, or send your answer directly to us if posting it is difficult.
Only offer an alternative route you can manage. If replies arrive by several methods, keep one consistent record so you do not chase someone who already answered. A reminder sent in error can be corrected politely; it should not become the guest’s responsibility to prove that they followed your instructions.
Ask for each invited person
Please confirm attendance separately for each name on your invitation, so we don’t assume that everyone has the same answer.
This matters when one partner attends and the other cannot, or when an invitation includes several named family members. Avoid a single “Are you coming?” if the answer needs to cover different people. The form or message should make the intended guest list clear rather than inviting additional names by accident.
Explain any additional information
Along with your attendance answer, please send your meal choice and any dietary information requested on the form.
Ask only for information needed for planning. If someone needs to discuss a private practical requirement, offer a direct contact rather than requiring them to put it in a public group message. Keep access and dietary conversations respectful and specific to what the event organisers need to arrange.
Reminders before the deadline
A reminder before the due date should sound like a reminder, not a reprimand. People are still within the time you gave them. Keep the date and method prominent, and avoid suggesting that a guest has already failed to respond on time when the deadline has not arrived.
A general reminder
Just a reminder that our RSVP deadline is next Friday. The reply link is in your invitation, and we’d appreciate a response either way.
We’re looking forward to celebrating. If you haven’t replied yet, please send your RSVP by the end of Sunday.
If you send a group reminder, make clear that people who already responded need not reply again. Better still, target only the missing responses where your records allow it. Do not publish a list of non-responders in a group chat to create pressure.
A personal nudge
Hi, I’m checking that the invitation reached you. Please let me know by Friday whether you’ll be able to come.
I know there’s still a few days until the deadline; I just wanted to make sure you had the RSVP link.
Use the second only if you are genuinely helping with access rather than disguising impatience. A guest may be waiting for a work schedule, travel decision or family arrangement. They are entitled to use the response window you provided.
A reminder with the method included
Could you complete the RSVP form by Tuesday? If it isn’t working for you, a direct yes or no to me is fine and I’ll record it.
This removes friction when the method itself is the obstacle. Do not assume that silence always means disregard. An inaccessible form, lost invitation or unclear household name can prevent a response that the guest intended to send.
When a guest has said yes informally
Lovely to hear you’re coming. Could you also complete the RSVP form by Friday so we have your meal choice and details in the same place?
Acknowledge the answer you already received. “You still haven’t replied” would be inaccurate if they told you in person. Explain the remaining administrative step rather than making them repeat the whole conversation without context.
Following up after the deadline
Once the deadline passes, contact the missing guests directly. State that you have no recorded answer, ask for a final response by a specific time, and explain the practical planning need. Avoid publicly shaming people or making threats about their friendship with you.
A first overdue message
Our RSVP deadline has passed, and I don’t have a response recorded for you. Could you let me know by Wednesday whether you can attend?
We’re finalising the numbers now. Please send a yes or no by tomorrow evening so we can complete the guest list.
Leave room for a record error. “I don’t have a response recorded” is more accurate than “You ignored the invitation” when you do not know what happened. If they say they replied, thank them and check the practical details rather than beginning a dispute about which channel they used.
A brief phone call
I’m calling about the wedding RSVP. We need to finalise the numbers, and I wanted to check whether you’ll be joining us.
A call may help with someone who does not use the online system or has missed messages. Keep it focused. Do not use the opportunity to demand an explanation for every delay if a simple answer will resolve the planning issue.
A final response date
We need your final answer by six on Thursday. If we don’t hear from you, we’ll record that you’re unable to attend and finalise the arrangements on that basis.
This communicates what you will do rather than issuing a vague ultimatum. Use a deadline that reflects your real planning process, and only state an outcome you intend to follow. Do not say a place will be released if you plan to hold it indefinitely regardless.
When someone else is coordinating
Please send your final answer to Maya, who is managing our guest list, by Thursday. She’ll confirm it has been recorded.
Make the contact clear and avoid asking guests to answer multiple people. Ensure the coordinator has agreed to that role and has the information needed. A named contact should reduce confusion, not create a new person whom guests have to find without directions.
Handling uncertain or incomplete replies
“We’ll try to come”
We’d love to see you, but we need a definite attendance answer for the booking. Can you confirm yes or no by Tuesday?
A hopeful message is not a usable headcount. Ask for the missing decision without treating uncertainty as bad faith. If the guest cannot confirm by the necessary date, explain how you will record the answer rather than continuing an open-ended maybe.
“I won’t know until the last minute”
I understand. Unfortunately, our numbers have to be fixed before then, so we’ll need to record you as unable to attend unless you can confirm by Friday.
This may disappoint both sides, but it is clearer than pretending the event can remain flexible when it cannot. If you truly have an arrangement that allows later additions, explain it accurately. Do not promise a last-minute place merely to avoid an uncomfortable no.
Only one person in a couple replies
Thanks for your yes. Could you confirm whether Robin is also attending, or should I record different answers for the two of you?
Do not assume one response covers everyone unless the guest explicitly says so. This is especially important if the RSVP system requires individual meals or transport places. Keep the follow-up narrow so the guest knows exactly what remains unanswered.
Meal information is missing
Your attendance is confirmed, thank you. We just need your meal selection by Monday to complete the details.
Separate confirmed attendance from incomplete supporting information. A guest should not wonder whether they lost their place because they missed a meal question. Tell them what is recorded and what still needs attention.
Extra names appear on the reply
I noticed an additional name on the RSVP. The invitation is for the named guests only, so could you confirm your response within that guest list?
Handle additions privately and promptly. Do not silently delete a person and assume the guest will notice. For a dedicated explanation of guest allowances, see how to ask whether you have a wedding plus-one, which covers the question from the invitee’s perspective.
A guest says they already replied
Thank you for telling me. I’m sorry our record missed it. I’ll update it now; could you confirm the answer once so I enter it correctly?
Take responsibility for your record where appropriate. You do not need to assign blame to the form, the planner or the guest before updating the answer. The immediate aim is an accurate list.
A guest declines
Thank you for letting us know. We’ll miss you, and we appreciate having a clear answer.
Accept a no without requesting a better reason. If you make declining uncomfortable, other guests may become more hesitant to answer. A respectful response keeps the RSVP process about planning rather than proving loyalty.
Close the list clearly
After a final deadline, update the record and communicate the outcome where needed. Do not leave a guest thinking their unanswered invitation remains open if you have now finalised them as not attending. A short closing message can prevent a later assumption that they are still expected.
As we haven’t heard back by the final date, we’ve recorded you as unable to attend. We’ve now finalised the wedding arrangements.
Thanks for your response. We’ve recorded two attending and the meal choices you sent.
The first message closes a missing response; the second confirms a completed one. Keep confirmations accurate. If your system sends automatic receipts, do not add contradictory personal messages that create uncertainty about which answer is current.
A late yes after the list closes
Thank you for getting back to us. The numbers are now final, so we can’t add another place at this stage.
I’ll check whether an addition is possible, but please don’t make travel plans until I confirm. I can’t promise a place yet.
Use the first when the answer is known and the second only when you are willing and able to check. Do not keep a guest waiting under the impression that a place is likely if the practical answer is almost certainly no. Once you have a result, tell them promptly.
A confirmed guest changes to no
Thank you for telling us. I’ll update the list. Please also let the transport organiser know if you had a place reserved with them.
Avoid shaming a guest for a change without understanding the situation. You may need to discuss specific arrangements, but the immediate task is to update accurate information. Keep any shared booking issue separate from the emotional response to their absence.
Use one master record for attendance, names and necessary details. If several people help, agree who makes final changes. This prevents duplicate reminders and conflicting counts. Protect private guest information and share it only with people who need it for the event arrangements.
Personalise reminders with the correct name, deadline and channel. Do not copy a message that says “tomorrow” if you are sending it on a different day. Small errors can create real confusion near a final count deadline. A precise date is often safer than relative wording.
Questions people ask
How many reminders should we send?
Use a proportionate sequence: a clear original request, a reminder if useful, then a direct overdue follow-up with a final date. The exact number depends on the event and communication problems. Repeated daily messages rarely add useful information once the deadline and consequence are clear.
Is silence a no?
Do not rely on an unspoken assumption. Tell the guest when you need the answer and what you will record if none arrives. After that stated point, act consistently. This makes the outcome clear without treating silence as an answer the guest definitely intended from the beginning.
Can we ask why somebody is not coming?
For planning, you usually need the attendance answer rather than a personal explanation. In a close relationship, you may naturally talk more, but do not make a reason a condition of accepting the RSVP. Guests can decline without disclosing finances, health or family circumstances.
Should the reminder be funny?
Light humour can fit your relationship, but it should not obscure the request or shame people. Include the actual deadline and method. Avoid jokes about cutting friends off or charging guests for failing to reply; they can turn an administrative reminder into unnecessary tension.
What if the website is the problem?
Offer a workable alternative and update the record yourself or through the agreed coordinator. Do not keep sending people to a form they cannot use. Once the issue is resolved, confirm the recorded answer so the guest knows they do not need to keep trying.