For the small print people actually read
Is it recorded, how long, what do I need, can I ask things? The short answers beneath the form that remove the last reasons not to register — and how many of them is right.
Nobody reads a webinar page in order. They read the title, check the time, look at who is speaking, and then hunt for the thing that stops them committing an evening. That hunt usually ends at the form, and for a meaningful number of people it ends there without a registration because one small question went unanswered: how long, what do I need to have in front of me, is it going to be put online without my knowing.
An answers block is the cheapest fix available, because it works on objections you already know about. The proof is in your own inbox: every question that has arrived by email since your last session is a line a stranger will wonder about tonight. Write those down in the words people use, answer each in two or three honest sentences, and place them where the hesitation happens.
Sample wording, in the plain voice that makes an answer believable.
Fifty minutes, then the host keeps ten for questions. The chapters and their times are listed above, so the hour has a shape rather than a promise.
A browser and the link that arrives in your confirmation email. The session says which service we present on; nothing needs installing and no account is needed to watch.
Only if we record it ourselves. Some hosts send a replay link to registered attendees afterwards — check the description, and if it does not say, assume the hour is live only.
How questions are handled is up to the host, and the description says what they have planned for this session. Email us before the evening if there is something you want covered.
No. Registering takes a name and an email on this page, and that is the whole process. Your way in comes to you rather than being posted where anyone can find it.
One start time, written with its zone beside it. If the label says 19:00 Central European, that is the moment on any clock; check your own before the evening rather than assuming the page converted it.
Then you are on the waitlist, and an email reaches you if a place opens. Nothing else is required and you have not committed to arriving at a session you may not get into.
Not from this page. Some hosts send a link to a certificate after a training session; whether one exists for this one is stated in the description.
A blanket it will be available afterwards is untrue unless you are genuinely recording and sending the link, and it quietly changes who turns up. Say what is planned, and say it in the description so the two places agree.
Guests need their own address and nothing else. Do not describe the page as connected to a service it merely presents on, and do not imply the join address is printed for the world to see.
The accurate line is that the confirmation email carries a calendar file and a Google Calendar link, so the date lands in front of them without retyping. It is not a sync, and the smaller claim reads as the more reliable one.
Emails go out before the start to everyone registered, and the host can switch them off. Do not promise messages on WhatsApp to attendees; that channel notifies the host that somebody registered.
Put it under the form. The questions it answers arrive after somebody has decided to commit an evening but before they are sure about the mechanics, and an answer block above the button interrupts the copy that has to persuade them. Underneath also works for returning visitors, since a registered guest rereads the practical lines on the morning of the session and looks for them below what they already filled in.
It is not, however, an inbox. Answers on a page still give guests no way to talk back mid-scroll: there is no chat widget and no question board, and anything a registrant wants to ask reaches you as an email you answer yourself. One line saying where to send questions is enough to make that clear without inviting a conversation the page cannot hold.
How it works
From the last session's email and WhatsApp messages. Write them in the guest's words, not in yours, and resist adding the ones nobody asked.
If the answer depends on a decision you have not made, say that. An uncertain line still beats an absent one, and it stops a registrant assuming the worst.
Draft the page in the app or ask Jitabi to lay it out, then check the answers do not contradict the description or the agenda above them.
The page stays editable at the same address, so a question that reaches you twice becomes a third answer without reprinting anything or sending anyone a new link.
Questions
No, and the two should not repeat each other. The description makes the case for the hour and names who it is for; the answers handle the practical hesitation after somebody is interested. Where a line appears in both, one of them is in the wrong place.
Not on the page itself — there is no chat or question tool attached to it. Guests email you, and how questions are handled during the session is the host's own arrangement. Say where to send them and the block stays honest.
It can, in the host's own words, if it genuinely helps people prepare. Nothing is connected to it, so the useful answer is what a guest needs rather than a brand: a browser and the link in their confirmation email.
Mostly not, because they describe the session rather than its outcome. Lines about a replay or a follow-up email are the ones that change, and if a link you promised after the session went to registered attendees, that is worth stating accurately in the answer.
Yes, arguably more so. A locked page means every visitor arrived deliberately and the friction is about trusting the session rather than finding it, so short answers about length, joining and what happens afterwards do quiet work under the form.
Get Started
Five to eight short, honest lines under the button remove the last reasons not to register — and the questions you have already answered by email tell you exactly which ones.
