For the copy that closes the hesitation
The description is the paragraph between the title and the button, and it does most of the persuading. Four worked examples, then the four things it has to settle.
Under the title sits one paragraph, and it is the only part of a webinar page most visitors treat as writing rather than as structure. The agenda they scan, the biographies they skim, the time they check. The description they actually read — which makes it the place to put the things a person needs before agreeing to give you an evening: who this hour is for, what they will be able to do afterwards, how long it runs and what happens the moment they press the button.
That is also why it should not be a summary of the speaker's career, a list of bullet-point benefits or an apology for the subject. Write it as you would describe the session to one specific person you know would benefit, in the plain sentences you would use out loud, and it reads like an invitation rather than a brochure.
Invented sessions, each doing the same four jobs in a different voice.
A short workshop for bookkeepers and office managers at charities who run payroll alongside everything else. In fifty minutes Lena Hofmann covers the January checks she does every year and the two reports she would never skip, then takes questions on the call. You will leave with a list you can work through on Monday morning. Registering takes your name and email, and a reminder arrives the day before.
No slides and no sales pitch: Marek Novák builds next month's night rota on our ward template, live, and explains each change as he makes it. It runs an hour and half of that is on the screen. If you have ever argued about a Tuesday handover, this is the hour for it.
The expense rules changed on the first and some travel claims will now come back. Petra Kowalski reads the new travel section line by line, shows the three forms of it people get wrong, and answers questions there and then rather than by email. Colleagues in the Utrecht office do not need to register separately, but everyone else does.
One grant application, from its first paragraph to the refusal letter it actually received. Sofie Marchand reads it aloud and marks where it was lost, then shows the same submission rewritten. Bring an application you have had refused if you can share it; nothing you send us is published, and the session stays as long as the room is.
Named in ordinary words — bookkeepers at charities, rota holders on a ward, anyone whose claims will come back. This line belongs in the description rather than in a separate panel, because the description is the copy that genuinely reaches the reader.
A list to work through on Monday, a template they can copy the shape of, a section of rules they can now read without guessing. Outcomes phrased as things you can do, not as transformations.
Fifty minutes and questions, or an hour with half on the screen. Length is an objection guests carry into every session, and a sentence about shape answers it better than a promise to keep it short.
That they leave a name and an email, that their place is held on the list, that a confirmation with the joining details arrives straight away. Saying it costs two lines and removes the hesitation about what a registration commits them to.
Fifty to a hundred and twenty words is the working range. Below it, you have written a subtitle and left the objections unanswered; above it, the paragraph pushes the agenda and the names below a fold that mobile readers do not scroll. Two short paragraphs read easier than one dense block, and both stay above the button.
The description also travels. It is the copy guests look for again in their confirmation, and the summary of what they signed up for when the reminder arrives the next day, so keep it consistent with the title above it and the chapters below it. Where the two disagree, registrants assume the agenda is right and arrive for the shorter evening than the one you planned.
How it works
Who, what afterwards, how long, what happens on pressing the button. Do not polish yet; the shape is what tells you whether the session is describable.
Audience and outcome in the first, shape and length in the second. Every clause a stranger could not picture goes.
Message Jitabi or build it in the app, then look at the description under your title with the agenda immediately below. Overlap between the two becomes visible there.
Questions landing by email are the description's missing sentences. Add them to the page and, if they keep coming, let the answers into the FAQ block as well.
Questions
Fifty to a hundred and twenty words, in one or two short paragraphs. Long enough to name the audience, the outcome and the length; short enough to stay above the agenda on a phone. If it needs more, the extra detail belongs in the agenda chapters or in the answers on the page.
Only if you genuinely intend to record and send it, and then as your own doing. Some hosts add a replay link for registrants after the session, alongside links to slides or resources; the platform does not capture or store a recording for you, so an unqualified promise is the wrong way to write it.
The confirmation is where registrants look for the time and their way in, so write the description to survive being reread: the length, the shape, and what happens next. Keep it consistent with the title, since both travel with the registration.
Put that line inside the description text itself. It is the copy guests reliably read, whereas a standalone audience or outcomes panel is not something the page renders for visitors, so the words you write there would reach nobody.
That is the normal way most hosts work now: describe the session, read what comes back, then rewrite the sentences that sound like marketing. The first draft is for structure — who, what afterwards, how long — and your own wording is the part worth protecting.
Get Started
Who it is for, what they can do afterwards, how long it runs, what registering commits them to. Four sentences in plain words and the paragraph does its job.
