For the change that comes after you hit send
The time moved, the venue swapped, the cake table rethought. Reply to Jitabi with the new line and the page updates, so the next guest to open the link reads the corrected version rather than last week's.
Once an invitation link is circulating, copies of it scatter: pinned in the family group, forwarded to a work chat, screenshotted by a friend who was being helpful. Then something changes. The ceremony moves an hour later, the marquee gets a different field, and the pinned message — frozen, confident, wrong — is now the problem.
An invitation page is not a printed card, and the honest way to run one is to accept that it will change after sending. The link stays the fixed object; the page behind it is allowed to move. When the venue swaps, one reply updates everything the link points at, and the stale screenshot quietly loses.
The messages below are phrased the way hosts actually text — one change, plain words, nothing formal.
Hi Jitabi, the ceremony now starts at 4 pm instead of 3. Update the time everywhere on the page and keep everything else the same.
Change the location to La Vigna on Via Colombo 4. The directions and parking notes need to match the new place, not the old one.
Three people have asked about children. Add a note that kids are welcome until eight, then it becomes grown-ups around the cake.
Before publishing, none of this is stressful: an unpublished event is invisible to guests, so you can draft, sleep on it, reply with three corrections in the morning, and only then let the link out. After publishing, edits go straight to the live version — which is exactly what you want on the Tuesday the cateriser moves your slot. One habit worth keeping: when you change a detail, reread the FAQ section in the same pass, because that is where the old time tends to hide.
How it works
Short beats clever. Name what moved and where; Jitabi edits that page, not a fresh one.
Thirty seconds of checking saves a message later, especially against the schedule and FAQ, which echo the detail you moved.
Post the same address into the chat with a line that the page has the updated time. Guests read the live version and reply on it.
Questions
That is the point of the page. Reply with the change and the live version updates; the address stays the same, so everyone who opens it from that moment sees the corrected invitation.
There is no automatic push to everyone who looked at the page. Hosts typically send one line into the chat pointing at the link and the change, and the page itself carries the current details from then on.
Nothing is typed in stone. Reply with any change you want made — including putting a line back the way it was — and the page follows. Chat and app edit the same site, so the wording always has a route home.
For a line or a time, the reply wins; you are already in WhatsApp. For reshaping sections or loading a gallery, the app is worth opening. Both act on the one event, in whichever order suits.
Yes, and that last window is when it earns its keep. A moved door time or a rained-off garden becomes one message, sent from the same phone the guests are holding.
Get Started
Plans move and replies can move with them. Keep the conversation open, and the invitation keeps telling the truth to whoever opens it last.
