For the internal session people ignore
Calendar pings get shrugged off. The invitation colleagues actually answer says why this hour and not another, names their part in it, and collects names on a list you can check before the session starts.
Nobody opens an internal invite thinking it is unimportant; they open it, see no reason, and defer the decision to a later self who never arrives. The forward-only culture finishes the job — an acceptance means nothing when the person who accepted forwarded it to an assistant. An internal webinar has the same attendance problem as a public one and a worse one on top: the pressure of politeness, where everyone says yes on the shared calendar and no one appears.
The fix is not a louder ping. It is an invitation that states a reason, asks for a decision worth making, and puts the answer somewhere real. A webinar page does exactly that: colleagues register with their names, the list updates as replies come in, and before the session you open it and know — by name — who is actually coming. A registered list is not attendance, but it is the first honest draft of it.
Internal readers spend their day in meetings that could have been emails. One sentence on what the session replaces — a slide round, a long thread — makes registering feel like a discount, not a tax.
Bring your last supplier quote. Come ready to argue the boundary. A colleague with a role in the hour is a colleague who remembers it; a guest of honour is a no-show.
Someone has to approve the calendar move. One plain sentence about length, start time with its zone, and what the team gets out of it is the forwardable defence.
Replies die in threads. The page collects name and email in a minute, each person's access link arrives privately afterwards, and the list replaces the roll-call nobody trusts.
The same session worded for where internal readers actually look.
quote handling session, Tue 4 March, 9.30. 45 minutes, replacing the slide round we sat through in January — and it's a working session, bring your most annoying supplier thread. Register on the page so I know to expect your face: <page address>
On Tuesday 4 March at 9.30 we're running an internal hour on handling supplier quotes — Marta walking through the fixed-price boundary, then working through quotes you bring. It runs 45 minutes and replaces this month's slide round. Register on the page (name and email, a minute); your link to join arrives by email afterwards.
Looking at the list before I book the room: you haven't registered for Tuesday. If the morning genuinely doesn't work, say so and I'll note you as a no — silence is the one thing I can't plan around. <page address>
Internal meetings used to travel badly: the join URL pasted into the big channel, then into a reply, then into an event someone edited, until three different links circulated and the wrong meeting got opened. None of that happens when access is private — the invitation carries only the page address, and each colleague who registers gets their own link by email.
One planning note: next month's session needs its own page, because one page carries one session. A quarterly meeting with one merged, drifting list records nothing; a fresh page per date gives each hour its own names.
How it works
Start in the web app or message Jitabi: the internal session, the chapters, the start time with its zone, the cap at your room's size. Colleagues can register the moment you post, so the page goes live first.
The team-channel post leads with what the hour replaces and what colleagues bring. The page link is the only link in the message; the joining address stays private to registrants.
The list shows who registered while WhatsApp pings you as names arrive. The personal nudge to the five quiet ones beats a second broadcast — and gives you a real answer of yes or no.
Export before you start, mark attended and no-show after, and send the follow-up pack to the registrant segments that need it. The next session's invitation gets written from this record.
Questions
No account of any kind — they leave their name and email on the page, and their access link arrives privately afterwards. Ask for the team or role as one of the page's extra questions if you want the list to sort itself by department.
Yes, and that is the practice worth adopting. The attendee list updates as replies come in, and you can export it as CSV or PDF, so you walk into the meeting knowing who said yes by name rather than waiting to find out in the room.
It should not. The invitation carries the page address only; each registrant receives their own access link in their confirmation email. That is what stops the join URL circulating in five versions again.
It sits alongside it. The page's confirmation email offers an .ics file and a Google Calendar link, which each colleague can use on their own calendar. The real gain over a plain invite is the list — an acceptance you can check, not an assumption.
Get Started
An internal session earns attendance the same way any session does: a stated reason, a private way in, and a list you can actually look at before you start.
