Does this work on my webinar platform?
Usually the honest answer is “most of it, and here is the part that does not.” So here is the whole table rather than the sentence.
Ten webinar platforms, five capabilities, one honest yes / partial / no per cell, read out of each platform’s own developer documentation rather than its marketing pages. Two of the five are a yes almost everywhere, and the part of the sequence with the strongest evidence behind it — the call before the session — needs no platform events at all. One capability is a no on every single row, Zoom included, and the reason is in the table rather than in a footnote.
The matrix
What can each platform actually tell us?
Where a platform's documentation does not state that something works, it is recorded as a no rather than assumed. Six platforms have a page of their own: Zoom Webinars, because it is the only one where a leave event is pushed at all; EverWebinar and WebinarJam, whose trigger names promise something their own documentation withdraws; and Demio, StealthSeminar and BigMarker, where what is missing matters more than what is there.
| Platform | Text the moment they register | Phone number on the form | Live join signal | Mid-session exit signal | Access without a gatekeeper |
|---|---|---|---|---|---|
| Zoom Webinars | Yes | PartialStandard registrant field, but the host has to switch it on in the form. | Yes | NoA live push event exists and fails silently. Delays of 7–10 minutes are reported. | PartialA Zoom admin has to grant the scopes; one shared app needs Marketplace review. |
| Zoom Events | Yes | NoNo phone field found anywhere in the ticketing API. Unverified is recorded as no. | NoThe event catalogue has no attendee join event at all. | NoNo attendee leave event either. Zoom Events is not classic Zoom Webinars. | PartialNeeds a Zoom Events licence, then the same app-approval path as Zoom Webinars. |
| WebinarJam | Yes | Yes | Yes | No"If they leave early" is evaluated after the session ends, not during it. | NoAPI access is approved by hand, paid subscribers only, about two business days. |
| EverWebinar | Yes | Yes | Yes | NoSame engine as WebinarJam: leaving early is evaluated after the session ends. | NoSame approval process as WebinarJam; one key covers both products. |
| Demio | NoNo webhooks in the official API at all. Everything arrives by Zapier polling. | Yes | NoJoins arrive through a polled Zapier trigger, so the lag is not ours to control. | NoThe only leave signal is a "left early" status in the post-session report. | Yes |
| StealthSeminar | Yes | Yes | Yes | NoA named leave webhook exists, but nothing documents how quickly it fires. | PartialThe API is free; the attendance triggers sit behind the Advanced plugin. |
| eWebinar | Yes | PartialA built-in merge field, but it reaches us inside the custom registration answers. | Yes | NoA "Left" value exists; no document says how soon after leaving it is sent. | PartialThe key is self-serve, but webhooks are configured by hand in the UI only. |
| BigMarker | Yes | NoNo phone field in the API. It takes a per-webinar text field, set up by hand. | Yes | NoNo leave webhook. A live endpoint can be polled, inside 100 calls a minute. | PartialThe key is self-serve; most of the webhooks are Enterprise or Event Package only. |
| GoTo Webinar | Yes | Yes | Yes | NoA leave time exists only in the attendance report pulled after the session. | Yes |
| Livestorm | Yes | Yes | NoNo join event exists. The attendance event fires once the session has ended. | NoNo leave event exists either, for the same reason. | PartialAvailable on all plans, but the workspace has to be validated by their support. |
| Read the mid-session exit column as a no everywhere, including Zoom. Zoom is the only platform on this list with a live push event for it, and that event fails silently — no error, no log entry, nothing to alert on. A signal that can quietly stop arriving is not something to build a promise on. | |||||
- Text the moment they register
- Does the platform push a registration event as it happens, so the first message goes out in the same minute? A platform we have to poll on a timer adds a delay nobody controls.
- Phone number on the form
- Does the registration form carry a phone field the API actually returns? Without one there is nothing to text and nothing to call, whatever else the platform can do.
- Live join signal
- Does the platform tell us during the session that a registrant has joined? This is what stops us calling somebody who is already watching.
- Mid-session exit signal
- Can we be told, during the live session, that someone has just left — reliably enough to reach them before the pitch? Read the note under the table before reading this column.
- Access without a gatekeeper
- Can the operator switch the integration on themselves, or does it need an approval queue, a sales rep or an enterprise tier?
Which platforms can this NOT work on?
The question is easier to answer once you split what we do into the parts that need something from your platform and the parts that do not. Most of it does not. The call before the session — the piece with the strongest evidence behind it — runs off your session time and our own timer, so it behaves identically on every row of the table above.
| What happens | What your platform has to provide |
|---|---|
| A text goes out when someone registers | A registration event, or a registration list we can read. Nine of the ten platforms above push it; Demio has no webhooks in its official API at all. |
| A call before the session, and a text carrying the join link | Nothing. This runs off the session time and our own timer. It is the same on every platform in the table. |
| We stop calling someone who is already watching | A join signal during the session. Seven of the ten have one. Zoom Events, Demio and Livestorm do not. |
| A call to someone who walked out mid-session | A leave signal that arrives during the session and can be trusted. Nothing in the table provides one — see below. |
| Working the people who did not show, after the event | Attendance data once the session has ended. Every platform in the table has this. |
Two rows in the table are worth reading before you assume you are fine. Zoom Events is not Zoom Webinars — they are separate products, and the newer one has no attendee join or leave event at all. And a phone field being available is not the same as it being switched on: on several platforms it is optional on the registration form, and without a number there is nothing to text and nothing to call.
If your platform is not in the table, that is not a polite no. It means we have not read its documentation end to end, and we would rather say that than guess on your behalf.
Why is the mid-session exit column a no everywhere, including Zoom?
On most of the table it is a no for a boring reason: the leave signal is a status in a report you pull after the session, or a trigger the vendor evaluates once the session has concluded. WebinarJam and EverWebinar are explicit about it in their own documentation — “Negative triggers are evaluated after the webinar session concludes”[1], and “If they leave early” is on their list of negative triggers.
Zoom is the interesting one, and it is a no as well. Zoom does push a leave event during the session. It has also been reported simply not arriving — a bug report on Zoom’s own developer forum titled “BUG: webinar.participant_left webhook sometimes not fired”[2] describes the notifications not being sent, with no connection to the developer’s server and no record in Zoom’s own webhook logs. No Zoom staff member replied. The thread auto-closed thirty days after the last reply, unresolved.
A signal that can quietly stop arriving is not something to sell
For what it is worth, nobody else appears to be shipping it either. The closest thing on the market names triggers like “Dropped off at pricing slide” and “Left before the core CTA”[3], and then routes them to tags, email, SMS and Slack. A phone call is not among its outputs.
How do I check what my own setup does?
Four questions settle it, and they are the same four we would ask you on a call. Every one of them can be answered from your own account in an afternoon, without talking to us.
Name the exact product, not the brand
Zoom Webinars and Zoom Events are two different products with two different webhook catalogues, and the newer one has no attendee join or leave event at all. The same care applies to platforms that ship a live product and an automated one under one brand.
Open your registration form and look for the phone field
On several platforms it exists but is off by default, and the consent language beside it is a separate question again. Without a number that the API actually returns, nothing else on this page matters.
Ask whether the trigger is pushed to us or pulled on a timer
This is the question worth asking every vendor you talk to, including us. A polled trigger is not a live one: Zapier's own documentation puts polling at 15 minutes on the free plan and 2 minutes on Professional, while instant triggers send a webhook as soon as the data is created.
Find out whether you can switch the API on yourself
Some platforms hand you a key in account settings. WebinarJam and EverWebinar require an application, are open to paid subscribers only, and say requests are typically processed within two business days. That is a scheduling fact, not a blocker, but it is better known in week one.
The polling numbers above come from Zapier’s own trigger documentation[4], and the approval terms from WebinarJam’s API application page[5]. Neither is a claim about how fast anything of ours happens, and you will not find one of those anywhere on this site.
Frequently asked questions
It means not checked. The ten platforms in the table were read from their own developer documentation end to end; anything outside it has not been, and we would rather write “not checked” than infer a verdict from a similar-looking product. Tell us what you run and we will read the docs before we answer.
For the parts that need no platform events, yes. For the parts that do, Zoom Events is a different product from Zoom Webinars and its webhook catalogue is lifecycle and ticketing only — there is no attendee join event and no attendee leave event in it. This is worth confirming before anything is built, because the two are easy to conflate.
Not on the evidence in this table, and it is not on a roadmap. On most platforms the leave signal is evaluated after the session ends by design. On Zoom, where the event is pushed during the session, it has been reported failing silently with no entry in Zoom's own webhook logs and no vendor response. We do not sell it, we do not price it, and we would rather you heard that here than after signing something.
We are not going to tell you to migrate your webinar platform to buy a service from us, and any vendor who does is selling you their integration rather than your outcome. The parts of the sequence with the strongest evidence behind them need nothing from your platform at all.
The date it was last checked end to end is printed under it, and it is printed because these APIs move and a capability matrix without a date is a claim with no shelf life. If a platform ships a change that moves a cell, the cell moves and the date moves with it.
You run a webinar. We come in and increase your show-up rate and your post-webinar sales, with our AI voice and SMS system — and you finally know why every registrant signed up. Six platforms have a page of their own, going deeper on what their own documentation does and does not commit to: Zoom Webinars and EverWebinar. If you run automated sessions rather than scheduled ones, start with evergreen webinars — it is the page that tells you honestly which half of this fits you. Or book a call and bring the name of your platform.
Founder & Operator, CallHush
Founder and operator of CallHush. The offer is one sentence: you run a webinar, and we increase your show-up rate and your post-webinar sales with an AI voice and SMS system. CallHush has no closed clients yet — the first engagement is a pilot run as a split of the client’s own registrant list, and nothing on this site is presented as a client result.
View all articles