RSVP without QR codes: why a personal link wins

At some point the QR code became a default on wedding invitations too: a black-and-white square in the corner, with "scan to RSVP" beside it. It looks modern and efficient — until you count the steps the guest actually takes, from the moment the invitation is in front of them to the moment their confirmation lands with you. On that count, the QR loses badly.

How does a QR-code RSVP actually work?

A code is printed on the invitation, and scanning it opens an RSVP form. The code is identical for every guest, so the form it opens has no idea who scanned it — it has to ask: full name, phone, sometimes whose side you belong to. The guest scans, types, submits — and you receive a row that still has to be matched against your guest list.

How many steps does each flow ask of the guest?

The QR route takes six or seven steps. A personal link takes two. It is worth counting honestly, because this is the whole difference:

• With a QR: find the invitation, open the camera, aim at the square, wait for the code to register, tap the link that pops up, type name and phone — and only then confirm.
• With a personal link: open the WhatsApp message and tap "We're coming". The name is already there, the details are already there.

Why does every extra step cost confirmations?

Because an RSVP happens in a short moment of goodwill — and every bit of friction wears it down. A guest who receives an invitation is willing to give it a few seconds, not a few minutes. If those seconds require finding the printed invitation, leaving the chat and opening a camera, some guests will tell themselves "later". And "later" is exactly where RSVPs vanish: not a refusal, just forgetfulness. These are the people you end up phoning the week before the wedding.

What about older guests?

Scanning a QR assumes phone fluency that not every guest has. Not everyone knows the camera reads codes; older phones need a separate scanner app; and the printed square is small, demanding a steady hand and precise aim. An eighty-year-old aunt taps a WhatsApp button perfectly well — she does it every day. Aiming a camera at a small square on an invitation? Far less so. The generation most conscientious about answering invitations is exactly the one the QR leaves out.

Why does one code for everyone burden you too?

Because a form that doesn't know who it is talking to hands the manual work back to you. It takes three shapes:

• Manual matching — the "David Cohen" in the form could be three different guests on your list.
• Typing errors — a nickname, a missing surname or an old number, and you have a row that connects to no guest at all.
• Blind reminders — you cannot send a reminder "only to those who haven't replied" when you are not sure who replied.

A personal link is born attached to the guest's row: the confirmation, the headcount and the meal preference update by themselves, with no matching and no guesswork.

Do you need to print anything at all for RSVPs?

No. A QR needs a surface to live on — a personal link needs nothing. A code requires a printed invitation, or at least an image passed around the chats, waiting to be scanned from someone else's screen. A personal link arrives inside the message itself, on WhatsApp or SMS, and opens on the very screen the guest is already looking at. No intermediate step, no "scan it off your parents' phone" — and no dependence on where the invitation ended up.

So when does a QR actually belong?

When it is large, right in front of the eyes, and the phone is already in hand — that is, at the event itself. A sign at the reception leading to the shared photo album, a code beside the seating board at the entrance — there the scan is natural: nobody has to find anything, the code is poster-sized, and one scan serves a whole hall. The rule is simple: a QR works up close, at the moment it is relevant. An RSVP happens from afar, weeks ahead — so it belongs to a link, not to a code.

What does an RSVP without QR look like?

Every guest receives their own personal link, straight on WhatsApp or SMS. In Weddigo it works like this: the invitation goes out through the official WhatsApp Business API with a unique link per guest; a tap opens an invitation page carrying their name; confirmation, headcount and meal preference close on a single screen; reminders go out automatically only to those who haven't answered; and everything is counted live in the dashboard. And the QR? It gets its place on the day itself — a sign at the entrance leading to the shared Snapigo album, where guests upload photos without installing a thing.

Save the QR for the sign at the entrance. RSVPs belong to a link that already knows who the guest is.