For hosts who want the tally wired in
Most makers hand you a pretty page and stop. This one pairs the invitation with a live reply system, so the page that announces your event is the same page that counts who comes.
Plenty of tools let you assemble a nice invitation and hand you a link. Then they leave. You are still holding replies that arrive by text, a headcount you estimate from memory, and meal notes buried inside someone's cousin's message about parking.
A genuine maker wires the page to a guest list from the first step. When a guest taps yes, that answer attaches to their name. Their companion is counted inside the limit you set. Their dietary note is collected on the spot and folds into a number you can hand the caterer. The invitation and the tracking are one system, which is the entire idea.
Describe the event once. The maker lays out both sides and keeps them in step.
A headline that reads like you, the details, the rough order of the day, the place and how to find it, and any note about what to wear.
Confirmations tied to names, plus-ones capped at your rule, and meal or allergy choices captured as people answer, so the count is data rather than a hunch.
You give the maker the who, when and where once. It builds the page and the reply flow from the same facts, so they cannot drift apart.
However you like to work, the result is the same: an editable page with replies already attached.
Drafting is fast, which is its virtue and its risk. A maker will write a confident time or address that happens to be wrong, so read every date, venue name and guest entry against what you actually know before you publish. That single habit is the whole safety rule.
Nothing reaches guests until you choose to publish, so you can make the page, fill the reply rules, and revise the wording without an early guest reading a half-finished invitation. When you are satisfied, one action takes it live under its own link.
How it works
Say who it is for, when, and where, in the web app or a line to Jitabi. The maker returns an invitation and a reply system together, as a private draft.
Choose the plus-one allowance and list the meals you can actually serve. These constraints shape what guests are able to submit.
Rewrite the headline and the details until they sound like you. Verify every fact. Accept, adjust or delete anything the draft got wrong.
Send the single link once. Confirmations arrive against names in real time, so the headcount settles long before any vendor needs it.
Questions
Both, wired together. The invitation and the guest list are built from the same description, so every reply, plus-one and meal choice attaches to a name automatically rather than living in a separate form.
Yes. Message Jitabi on WhatsApp or use Clara in the browser, and the maker turns a few sentences into an editable page with the reply flow already attached.
No. The page stays a private draft until you publish it, so you can shape the wording and set the reply rules before any guest can open the link.
Weddings, birthdays, baby showers and graduations are fully supported types with their own sections. Any other gathering uses the same general page and reply list, so the maker is not tied to one occasion.
You can edit names at any time, but the maker works best when the list is part of the build. Starting with the people you invited means every reply attaches to a name from the first confirmation, instead of you copying answers over later.
Get Started
Describe the event once, edit the invitation into your own words, and share one link that both invites and keeps the tally honest.
