For the answer you have typed nine times
Children at the ceremony, arrival time, the awkward gift question: an event FAQ page keeps every answer on the invitation itself, so you write it once instead of a dozen times in a dozen chats.
When an invitation arrives as a message, guests answer in the same shape: a chat thread. Each question gets a private reply, and the guests who asked nothing learn nothing. One cousin hears the parking plan from you directly; the ones further down the list invent their own. An FAQ section moves those answers out of private threads onto the page everyone opens.
That makes it the polite record-and-repeat killer. There is no mishearing an answer over a poor phone line; there is a short list of questions, phrased the way guests actually ask them, with the answers sitting underneath. Anyone who reads it gets the identical thing.
Short, plain, and complete. Adapt the tone to your event; the shape is what works.
Yes, little ones are very welcome at the party. There is a quiet corner off the main hall if anyone needs a break with a tired toddler.
The door opens at half past three and the toasts begin at four, so arriving any time in between gets you seated before the first speech.
Nothing is expected. If you would still like to give something, the gift section on this page lists what would genuinely be used, and a card works perfectly.
Free along the side road past the pub, and the coach stops at the main gate if you would rather leave the car at home.
Not “travel logistics” but “where do we park?” The question should match the words in the message you keep receiving, so guests recognise their own question at a glance.
Enough to be a real answer, short enough to read standing at a door. If an answer needs a list of its own, it probably belongs in a separate section, like directions or the dress note.
Children, gifts, who is invited and who is not, what happens if it rains. Guests find these the hardest to ask and the easiest to guess wrongly, which is exactly why they deserve a written answer.
Every gathering has its own set, but these recur so often they are worth drafting before anyone asks:
The flow stays simple. The WhatsApp message opens the invitation page; a guest reading the details hits a question, finds the FAQ, and the answer arrives without involving you at all. Then the reply button is right there, so their yes does not stall while they work out whether the kids are invited.
The section also keeps working as plans settle. A new question that has arrived three times is worth adding; an answer that changed, a moved time, gets edited once and every later guest reads the corrected version. The page becomes the quiet record of what the event actually is.
How it works
Build a wedding, birthday, baby shower or graduation page through the web app, or describe the event to Jitabi on WhatsApp. The FAQ is one of the sections the finished site carries.
Scroll back through the messages you have already answered and write the FAQ from that list. In-app drafting can turn your rough notes into clean question-and-answer pairs; you adjust the wording until it sounds like you.
Nothing is visible to guests until you publish. Once the page is live, send the invitation link to the group and let the answers stand where everyone can reach them.
Add a line when the same question keeps arriving, and correct an answer when a plan moves. Replies continue to land on your guest list while you edit.
Questions
Six to ten is a comfortable size for most events: enough that the recurring questions are covered, short enough that reading it costs a minute rather than a lunch break. If the list grows past that, some answers probably belong in their own sections, like directions or the dress note.
After the main details, alongside the schedule and the reply button, where guests reach it without hunting. Its position matters far less than its existence; guests arrive at it from the same link as everything else on the invitation.
The page shows one set of answers to everyone who opens it. If a question is genuinely for a smaller circle, like the details of a surprise, send that in a private message or move those answers onto a password-protected page.
Only when you know the answer will matter on the day: the rain plan, step-free access, how long the speeches run. Guessing at questions produces pages that read like instruction manuals, so keep the list to what guests genuinely need to know.
Yes, and that is part of the point. The page is live, so a corrected answer is what the next guest reads. Nobody needs anything resent, and your reply list stays exactly as it was while you edit.
Get Started
Draft the FAQ section in the week you send the invitation, while the repeated questions are still fresh. Start free, publish the page, and let the answers quietly do their work.
