Collecting RSVPs when half your guests read Spanish
Updated September 18, 2026
If one family is Mexican and the other is not — or if half the guests are relatives who use WhatsApp and half are friends who use email — the RSVP is where that difference stops being charming and starts costing you evenings.
Three decisions make the difference.
The page should arrive in the right language
Not a toggle at the top: the right language, first try. A guest who lands on a page in the wrong language and has to hunt for a switch is a guest who closes it.
You know which language each guest reads — it is on your own list. Send them the link that is already in it.
Give people a way in that is not a form
Some of your guests will not fill in a web form, ever. That is not a failure of the form: they are seventy, or they are your uncle.
Plan for it. Somebody should be able to answer on their behalf without breaking the list — the same record, answered by somebody else, rather than a second row and a note in a group chat.
Ask each guest about each celebration separately
“Will you attend?” is one question, and a wedding with three celebrations needs three answers. A guest who is coming to the religious ceremony but not the party needs a way to say exactly that — otherwise they will say it in a WhatsApp message and you will transcribe it.
And ask how many are coming, not just whether. Two invited and one coming is the commonest answer in the whole list and the one most forms cannot represent.
Make the link impossible to guess and easy to type
The link goes into WhatsApp, and WhatsApp is where it will be forwarded. A code in the URL should be unguessable — nobody should be able to walk your guest list by trying codes — and a guest who lost the message should be able to find themselves by name instead.
Those two things are in tension and both are necessary: short enough to be read out loud, long enough that it cannot be enumerated.