Emma and James email it to 240 people, and every guest gets a link
of their own to the same page. There is no venue yet and no
schedule — just the announcement, a cover they made themselves,
and a song written for the two of them. Because each link belongs
to one person, every reply comes back with a name on it: Emma and
James can see who has answered, and how.
The same link becomes the invitation. Venue, time, running order,
and an RSVP that also asks what people can and cannot eat. Nothing
is re-sent. Everyone who saved the link in March opens it in June
and gets a banner naming exactly what changed.
- Event details
- Schedule
- RSVP
- Survey
Guests start replying in the chat thread. Where should we stay? Is
there parking? Emma answers once, in front of everybody, instead of
forty times in forty separate text messages.
Enough people asked about hotels that Emma simply adds a Where to
Stay section — three hotels, the block code, and how to get there
from the airport. Everyone already holding the link now has it.
- Where to stay
- Travel
- Location
Guests post photos to the page from the reception floor and everyone
sees them straight away. No hashtag, no shared-album invitation, no
app for anybody to install.
The photographer’s gallery and the first-dance video go up on the
same link. It is now the place the whole wedding lives — and it
never needed a second URL to get there.