For hosts who want a reusable format
Here are two templates. Copy the first, and it works perfectly until a detail changes. Copy the second, and the same words open a page that tracks replies and edits itself. Choose on purpose.
A template is a fixed shape you refill: what, when, where, reply-by, and the contact route. The frozen version ends in type your answer and send it back; the living version ends in a link. Everything before the link can be identical, which is the point: the template is the message, the page is what the message opens.
The living template trades one small thing, a few extra seconds of setup before the first send, for three large ones. Answers arrive in a list instead of a scroll. Details get edited without a resend. The deadline sits beside the button and reminds people for you.
Same words, two endings.
You are invited: [what], on [date] at [start time], [venue name and town]. By [reply date], please let us know if you can come, here in chat or by text. [address], [parking note], [anything they should bring].
You are invited: [what], on [date] at [start time], [venue name and town]. Everything else, with directions, menu and one reply button, is on this page: [link]. Tell us by [reply date], either answer works for us.
You are invited: Elsa's graduation lunch, Sunday 4 October at midday, the restaurant by the harbour. The rest, directions, the table plan and one reply button, is on this page: [link]. Tell us by 25 September, either answer suits us.
You are invited: the marriage of Marta and Tom, Saturday 3 October at half past three, Lindqvist House, Stockholm. The order of the day, travel notes and one reply button are on this page: [link]. Answers by 12 August help the caterer more than you know.
The frozen template collects replies across chats and groups, in your scroll. The living one lands them in one guest list, names attached, plus-ones inside limits, meal notes where you asked for them.
The frozen template lies the moment anything moves, and corrections are re-sent everywhere. The living one is edited once, and every tap afterwards sees the current truth.
The frozen template leaves non-responders in your memory. The living one shows them on the list and sends a reminder from there, so the deadline is enforced by the tool, not the guilt.
How it works
Sections for the details, the reply button with the deadline. Start from a template design or describe the event to Jitabi and let it draft the site around your wording.
What, when, where, reply date, the line about the page. Fill the living shape once and keep it as a message you reuse, event after event.
Every recipient opens the same page, so nobody works from an older copy of the details.
Change the details later and the link shows the new version. After the event, the next one gets a fresh page and the same skeleton.
Questions
The message skeleton, yes; that is what makes it a template. The page itself gets new details for each event. Each occasion should have its own link and its own list, so last month's replies never mix with this month's.
Nothing resends, and that is the whole design. Guests who tap the link later see the edited version, even if they received the original message. Your chat scroll keeps the old words; the page holds the current ones.
That is the normal pattern: one link, many places. The group announcement, the personal ping and the printed card all open the same page and count into the same list.
For weddings and birthdays there are full designs. For any other gathering, the same shape works: a shareable page, replies in one list, reminders to the quiet ones. Corporate and anniversary designs are marked as coming soon, so the page keeps the promise honest.
Each event gets its own link on a subdomain plus a short path URL. Guests open the page itself; the list behind it is where your account lives. If the event is password-protected, you share the password with invited guests.
Get Started
Start free, publish one page, and the message you reuse becomes a template that tracks its own replies.
