For hosts who want the site, not a blurb
The output is not a clever message, it is a full event website — headline, schedule, venue notes, FAQ and a reply button. You start the whole thing from your phone with a single message.
Plenty of tools will write you a pretty paragraph of invitation text and stop there. Jitabi does not build messages; it builds websites, and the distinction is the whole reason it is useful. What appears at the end of the chat is a real event page — the same multi-section format a wedding or birthday site uses — published at its own address and ready for guests to read, answer and share.
You start it from wherever you happen to be, because the interface is a conversation rather than a canvas. Message the details from the sofa or the bus, and the sections assemble themselves around what you described. The keyboard stays where you left it; the site still gets made.
The who, the when and the shape of the day, in complete sentences rather than placeholders. Reply with the tone you want and the welcome rewords itself.
On occasions that run to a plan — a wedding's ceremony, vows, drinks, dinner — the timeline drafts itself from what you described, and edits keep working by reply.
The place, with room for parking notes and a line for travellers. Undecided? Mark it to be confirmed and fill the gap in a later message.
The questions guests always send get answered up front — what to wear, whether children come, when it finishes — so they read the page instead of messaging you.
Bottom of the page, doing the quiet work: every yes, no and plus-one lands on your guest list within whatever limits you set.
There is a practical reason to build the whole site rather than a paragraph: guests read invitations on phones, and a page sized for a phone answers them properly. You preview it on the same small screen they will use, so the schedule, the directions and the reply button all sit where they belong before the link ever leaves your chat. It is a website in the ordinary sense — you could bookmark it, forward it or print its QR — and it took a message and a few replies to make.
How it works
Say what is happening, when and where. You are writing a description; Jitabi is choosing which sections the occasion needs and filling them.
Check the schedule against your plan and the FAQ against the questions you expect. Reply with what moved or what is missing; the site adjusts.
The completed page goes live at its own myjoyfullday.site link. Until you publish it, the whole thing stays invisible to guests.
Guests read the details, press reply, and land on your list; the venue and FAQ hold their questions so fewer reach your phone.
Questions
A full one, in the same multi-section format the designed pages use: a welcome, the details and directions, an FAQ where it helps, and a reply button. The chat is simply how you commission and revise it.
Yes — that is the intended way. You message the details and edit by replying, then preview the page on your own phone, which is the size of screen most guests will read it on.
Not from the thread. The draft comes in a sensible structure the assistant picks for the occasion. To reorder sections or change designs, open the same event in the web app, where the layout controls live.
No. They open the link in their browser and press the reply button. Nothing to install and nothing to register for mid-scroll, which is a large part of why more people actually answer.
Weddings, birthdays, baby showers and graduations have dedicated designs and full section sets. Other gatherings still get a proper event site with replies tracked; a webinar is a separate product with real registration.
Get Started
One message sets the sections; a few replies fill them; publishing hands you the link. That link is the invitation your guests will actually read.
