For whoever is holding the wine and the spreadsheet
A dinner invite lives or dies on the headcount. The page carries the menu tease, the time, the address — and guests send dietary needs with their reply, so the kitchen plans against truth.
Dinner parties are the event where a wrong number hurts most. Six people, and a hidden plus-one wrecks the table plan. Sixty, and a missed allergy is an emergency rather than an inconvenience. What a chat-message invitation cannot do is keep track: Marta said yes in March, changed her mind in May, and the message that says so is buried under a holiday photo.
An event page keeps the number honest until the last hour. Every reply that arrives shows on a live list, guests who have not answered are visible as a gap, and WhatsApp or email reminders go out to them so you are not setting place cards against ghosts.
The dinner-party reply form is the whole point of the page:
Write what is on the table without spoiling the evening. Guests reply better when they know why the seating has a theme, and a line of description sits easily in a page section.
For one long table, seating arrangements let you place the two people who should not be neighbours before the complaint arrives on the night.
Black-and-white dinner, cocktail, or sensible shoes for the terrace: stated once on the page, obeyed by everyone.
The address is news to nobody and yet everyone asks. Directions live on the page beside the note about arriving before the soup.
For a dinner party at home, the general event-page tools above carry the whole job. There is also a separate dinner invitation product on the platform when the occasion wants something shaped around a dinner from the start — its own structure, its own wording. If that sounds closer to your evening, look at the dinner invitation feature page and see which fits.
Autumn dinner at ours on the 15th: lamb or a mushroom wellington that Tom has finally perfected. Reply on the page and tell us which plate is yours.
We are turning fifty and feeding you for it. The menu tease, the time, the address and a reply button are all on this page. Allergies go on the form, not on your conscience.
How it works
Describe it the way you would tell a friend: home dinner, Saturday the 15th, two mains, about thirty people. Jitabi drafts the invitation page from that message.
Menu options, the allergy field, the plus-one limit. Deciding these early is what makes the reply data useful rather than decorative.
Send the link into the host chats. Nothing is visible to guests until you publish, so the draft can sit while you argue about dessert.
In the last days, the live list shows exactly who is coming and what they cannot eat. Late non-answers get a reminder before you shop.
Questions
Yes. The meal-choice field on the reply form is built for exactly this — fish or vegetarian, set menu option A or B — and each choice arrives attached to the guest's name on your list, with an allergy note in their own words underneath.
They overlap. The dinner invitation product exists for occasions that want a page built around a dinner from the start; a general event page does the same headcount job with a different shape. The feature page for dinner invites explains which is which.
No formal registration is involved for a private dinner. Parties use a plain RSVP reply — name, attendance, plus-one inside your limit, meal choice. Registration flows belong to the webinar product, not your table.
You mostly cannot, and it is fine. The page still holds the truth by the final week: the guests who answered in chat usually get around to tapping the link once the food questions start, and the genuinely silent ones are caught by the reminders, which is the number that matters.
Get Started
Start free and put the menu, the date and the reply button on one page. Whether the table seats six or sixty, plan details live on the pricing page.
