Writing · Guides

Giving each wedding guest their own invitation link

Send every guest a link tied to them rather than one address shared with everyone. The website then knows who is reading it, shows only the functions that person is invited to, and records their answer without asking them to remember a password or type their name into a box.

A guest holding a phone at an evening wedding function.

One link for everybody is the obvious way to share a wedding website, and it is the reason most of them end up saying less than they should. The moment the address works for anyone who has it, the site has to be written for a stranger. Out go the home address, the hotel your uncle is staying in, and the hour the house will be empty on Saturday morning.

A link tied to a person removes that compromise. The site knows who opened it before it renders anything.

Nobody wants an account on your wedding website. A password is a small task you have handed to two hundred people, and about thirty of them will do it wrong on the day it matters.

The link itself is the credential. Each guest gets an address that belongs to them, sent the way you already talk to them: a message to your cousin, an email to a colleague, a printed card with a short code for an aunt who does not use WhatsApp. They tap it and they are in, on whichever device is in their hand, in three months' time as easily as today.

That also means you can see the invitation as they will see it. Open your father's link and you get your father's wedding: his functions, his timings, his page. It is the closest thing to reading your own invitation over someone else's shoulder.

A printed wedding invitation card on a table beside a cup of tea.

Let the site decide what each person sees

Once the site knows the reader, every function can carry its own invited list, and the same address shows a different wedding to different people.

Your colleague invited to the reception opens the link and finds one event, one venue, one time to arrive. Your cousin who is there for the whole week finds five. Neither of them has to scroll past events they were never asked to, and neither has to work out which parts apply to them. You are not publishing a schedule and hoping people read the right rows.

This is also what makes the private things possible. Directions to a family home, the number to call when someone is lost, the photographs afterwards — all of it sits behind the same door. The gallery stays with the people who were actually there.

Get answers back without chasing anyone

A guest who has already been identified by their link does not need to tell you who they are. They answer for each function they were invited to and that is the whole interaction. No name field, no email field, no spelling of a surname that arrives three different ways.

The reply lands attached to the right person and the right event, which is what makes a headcount trustworthy. Two hundred yeses from a single form field require somebody to sit down with a spreadsheet and work out which two hundred. Per-guest answers do not.

Change something at eight in the evening

Venues move. A time gets pushed. The Sangeet ends up in a different hall than the one on the card.

With a shared address, an update is a broadcast: everyone hears about a change to an event most of them are not attending, and the twelve people who genuinely needed to know are somewhere in the middle of a group chat with ninety others. When the site knows who is invited to what, the change reaches the people it concerns and leaves everyone else alone.

What to prepare before you send anything

A guest list with a name and one reliable way to reach each person. A note beside each name of which functions they are invited to — that column does most of the work here. A short code or printed alternative for the handful of people who will not open a link at all, and one person in the family whose number goes on the site for the day itself.