For hosts who want the counting done
A pretty page is the easy half. The real work is replies that land against names, meal choices the caterer can trust, and a guest list that stays accurate without a spreadsheet.
Plenty of tools will let you assemble a nice-looking invitation page and hand you a link. Then they stop. You are left with replies arriving by text, a headcount you estimate from memory, and meal choices buried inside someone's cousin's message about parking.
A genuine builder wires the page to a live guest list. When a guest taps yes, that answer attaches to their name. Their plus-one is counted inside the limit you set. Their dietary note is collected on the spot and rolls into a number you can hand the kitchen. The invitation and the tracking are the same system, which is the whole point.
Each reply matches a name on your list, so you can see who has confirmed and who has not, without re-reading a thread of messages.
Decide how many companions each guest may bring. The form enforces it, so you are not negotiating headcount by text the week before.
Options and allergies are captured during the reply. Weeks ahead you have a real count per dish instead of a hopeful guess.
Almost no one opens your invitation on a laptop. The builder assumes a small screen from the first pixel.
If you would rather describe your wedding than configure it, message Jitabi on WhatsApp. In a single line, say who, when, and where. It drafts the sections and the reply system together, leaving you to correct the wording and publish. What used to be an afternoon of dragging boxes is now a short exchange and a look-over.
Whatever route you take, the result is the same: one shareable link that both invites and accounts, so the day you send it is the day the counting quietly begins.
How it works
Choose a design and tell the builder who you are inviting. Unlike a static page, the list is part of the build, not something you bolt on later.
Send one line describing the wedding on WhatsApp and let it draft both the page and the reply flow for you to edit.
Choose the plus-one limit per guest and the meal options you can actually serve. These constraints shape what guests can submit.
Share the link once. Confirmations arrive against names in real time, so the headcount is settled well before any vendor needs it.
Questions
The page and the guest list are one system. Every reply, plus-one, and meal choice attaches to a name automatically, so tracking attendance is built in rather than done separately by message.
Yes. You set the allowed plus-ones per guest and the reply form enforces it. No one can confirm beyond the number you decided, and you are not left renegotiating over text.
Dietary choices and allergies are captured while guests reply, then counted. You hand the kitchen an exact number per option instead of an estimate assembled from memory.
No. They open your link, read the page, and reply in a couple of taps. Nothing to install and no sign-up standing between a yes and your guest list.
The designs are mobile-first and tested on small screens, so text, buttons, and the reply form stay usable even on a phone without the latest browser.
Get Started
Build once, share one link, and keep the guest list accurate from the first reply to the final headcount. The counting stops being your job.
