The chat-to-site pipeline, walked through
The whole build happens in one chat. Send the details, get a real event website back with sections written and a link ready, then keep shaping it by replying while answers track themselves.
It is worth following the line end to end, because the length of it is the point. Most invitation tools make you carry the work across several places: a designer for the look, a form builder for the replies, a spreadsheet to reconcile them, a messaging app to send it all. The Jitabi assistant collapses that into a single conversation, and the conversation runs all the way to a published site.
You begin with a message. Jitabi returns a draft page with the sections a real invitation carries. You reply with corrections, and the same page updates. You publish, and it gets a live myjoyfullday.site link. You paste that link into WhatsApp, and every guest answer writes itself onto a tracked list. No export, no re-upload, no second tool holding a copy that quietly drifts out of date.
Who it is for, the date, a rough time, the place, and anything about the tone. A paragraph, not a specification; gaps get marked honestly.
The invitation, the details, an FAQ worth settling early and a reply button appear, laid out in the structure the occasion normally uses.
Change the time, add the line about gifts, ask for a warmer welcome. One message can carry five edits, and the draft answers like a text.
The page goes live at its own address. Until that moment it stays private to you, so the half-finished version never reaches a guest.
Yeses, nos and plus-ones inside your cap land on one guest list, with meal notes on the occasions that support them.
The pipeline ends where it should: with a guest who does not know or care how the page was made. They open the link from a normal WhatsApp message, read the invitation, press reply, and are done. There is no app to install, no account to create, no bot to talk to. All the machinery — the drafting, the sections, the counting — sits behind the link, and the only person who ever has to understand it is you, and only for as long as it takes to send a first message.
How it works
Message Jitabi the who, when and where. It is a real wedding, a birthday, a launch — the words you use are the brief the page is built from.
Scroll what comes back and answer it like a message. Send the changes you were saving up until the wording reads like you wrote it.
Publish, copy the myjoyfullday.site address, and post it into the family group or a private thread. The same link works for one guest or a hundred.
Answers gather onto the guest list with names and plus-ones counted, so planning the food and the seats has real numbers behind it.
Questions
A real one. The page it drafts is the same multi-section event site the web editor produces, published at its own myjoyfullday.site address. The chat is how you start and refine it, not a lighter substitute.
Yes. Reply with the new time or venue and the live page updates while the address stays fixed, so everyone who opens it next reads the current version. Before publishing, drafts are hidden from guests entirely.
They keep landing on the guest list with nothing for you to do. Plus-ones are counted against the limits you set, and the list shows who has not answered so a reminder can go out later.
No. Chat and app work on one event, not copies of it. Hosts often start in the thread on the commute and open the same page in the web app later for a gallery or a seating change.
You start free and build the invitation for real. The upgrade conversation begins as your guest list grows, not to unlock the chat; the plan details live on the pricing page.
Get Started
From a sentence to a published site with a reply button on it, all inside the chat you already have open. Send the details and read the draft back.
