For the member who organises things
Most communities have no mailing list, only chats that move too fast. One page, one stated time zone, a cap for the room, and a follow-up that reaches the members who missed the hour.
A club, a congregation, an association of former students — the usual distribution system is a group chat, a noticeboard and word of mouth. Nobody has a mailing list, which is why the standard webinar advice lands badly: it assumes you have somewhere to send things. You do not, and you would not want to build one for a handful of gatherings a year.
The workable version is a page and a link. You publish the session, paste the address into the chats where members already are, and put it on anything you print. Members register themselves with a name and an email, which builds the list as a by-product of the invitation rather than as a job you had to do first.
A community spread across countries has one recurring argument, and it is worth settling on the page. The zone shows as a label beside the start time; conversion for each visitor does not happen automatically, so spell it out.
Limit the places to what the meeting can hold. The page can show how many are left and says when it is full, which also settles the argument about whether to invite more.
Members arriving after the cap join the waitlist and are told an email comes if a spot opens. Useful when half the community wants to come and the room does not fit them.
Chapters with durations for whatever the evening is — a talk, a reading, introductions — and a speaker section with a name, title, photo and a short biography.
Everyone who registers receives their own access link in the confirmation email. The published address is the page, never the meeting, so a forwarded invitation cannot carry someone straight into the room.
Community links travel. Someone forwards the invitation to a cousin, the cousin mentions it in another group, and suddenly the evening has people in it who are not members. That is often fine, and sometimes it very much is not.
Two controls cover both cases. A password on the page means the address alone opens nothing, so you send the word to the members you actually mean. And because each registrant gets their own access link rather than one shared meeting address, a leaked invitation leads to a locked page instead of an open room. Neither control stops an invited member forwarding their link, which is why a session that must stay closed is also a conversation about trust.
The real difficulty with a community across time zones is that a third of the members cannot make the hour, however carefully you write the time. The list is what lets you do something about it. Registrants carry statuses — attended, no-show, cancelled — and you can send a message to a chosen segment, which is where the note to those who missed it belongs.
Send that segment what you have yourself: the recording you made, the reading for next time, the date of the following session. Reminders before the evening go out by email at twenty-four hours, an hour and fifteen minutes ahead, and nothing needs you to chase anyone by hand. Members never get an account to make, which is the main reason they actually reply.
How it works
What it is, the date, how long it runs, and who is hosting. Send that to Jitabi as a paragraph, or fill it in the web app, and let the page take shape around it.
The zone named in words, the equivalents you calculated yourself in the description, and the length. This is the step that prevents the argument afterwards.
Limit places to the size of the room, turn on a waitlist behind them, and gate the page when the session is for members only.
Drop the address in the chats where members are. Afterwards, message the no-show segment with the recording link you are supplying and the next date.
Questions
No automatic conversion happens, so it is worth writing the time out yourself. The zone appears as a label next to the start time, and the equivalents for the countries most members live in belong in the description.
There is no contact import. Members register themselves on the page with a name and email, and the list fills from those replies. That is usually less work than reconciling an imported sheet that has been stale since last year.
One page holds one session, so each date needs its own page and its own link to post. The agenda and host sections copy across, and the previous list is the audience for the next announcement.
Reminders are emails at twenty-four hours, an hour and fifteen minutes before the session, sent to registered members unless you switch them off. WhatsApp is used to notify you when someone registers, not to reach your members.
The page takes registrations, not money; there is no ticketing or payment in the webinar product. If a contribution is part of how the group works, collect it wherever you do that now and keep the registration free.
Get Started
You do not need a mailing list to run an evening for members. Publish the page, write the time honestly, post the link where the community already is.
