For the blank section you keep walking past
Describe the session and the wording comes back drafted: description, agenda chapters, speaker lines. You edit until it sounds like you, because the join link, the time and the number of places are yours alone.
Ask it to write the parts of a webinar page that are prose, and it is useful. It turns your description into a first paragraph for the page. It shapes agenda chapters out of a rough running order and gives each a duration and a takeaway. It tidies a speaker biography so it reads as a paragraph rather than a curriculum vitae. In the build, a section you cannot face starts as a draft you react to; on WhatsApp, Jitabi does the same job from a message that simply describes the session.
Reacting is the point. A blank box invites postponement, a draft invites editing. Most hosts end up rewriting a good part of what comes back, which is a better hour than composing every line from nothing — and a much worse one than publishing what came back unread.
Message the session in ordinary words — what it is, when, who speaks, how many places — and the assistant drafts the page. You keep shaping it by replying in the same thread.
Inside the build, one action fills the section you are stuck on from what the other tabs already say. Change the instruction, take another attempt, keep the lines that sound like you.
There is no separate AI copy of your webinar sitting somewhere else. Drafts land in the same fields you would type into, and the address stays fixed once you publish.
Before publishing, read the page the way a stranger would, because a draft is only as careful as the description it was given. Times, claims about the speaker and any number on the page need your eyes on them. An undecided thing should stay visibly undecided. Nothing goes live on its own: an unpublished page is invisible to guests, so the review happens before anyone can read a sentence you never checked.
Where the text is thin, say so plainly and rewrite it. Hosts who treat the draft as a first opinion rather than a finished product end up with pages that sound like them, because the corrections they sent are exactly what the page finally carries.
How it works
To Jitabi in a message, or in the tabs with whatever details are settled. The subject, the date if fixed, the running order, the speaker, the size of the room.
Description, agenda chapters, the speaker line. Keep the attempt that reads closest to how you talk and mark the rest for rewriting.
Your join link and platform name, the start time with its zone label, the cap, and the questions the form asks. These are decisions, not sentences.
Every line passes your eyes before the address goes out. Then send it, and the register fills from wording you approved yourself.
Questions
It can draft most of the wording and lay the page out in the right sections. What stays with you: the join link, the time, the seat cap, the questions the form asks, and the final read before publishing.
Neither. Nothing is visible to guests until you publish, and sending is your job from your own email or chats. The drafting produces text; it does not put that text in front of anyone.
It should not, and the reliable habit is to say what is undecided in your own words. Gaps stay marked as gaps. If something reads as invented, that is the cue to stop and fix it before publishing.
On the prose sections, yes. A webinar page has fields a party page lacks: registration questions, a cap, chapters with durations, your own join link. Drafting helps with the sentences around those, not with the decisions themselves.
Yes. The address stays fixed while the page behind it keeps changing, so a reworded description or an extra chapter reaches everyone who opens the link next. Earlier registrants still have their own confirmation.
Get Started
Let the drafting clear the blank page. Keep the lines that sound like you, replace the ones that do not, and fill the boxes only a host can fill.
