# Does this work on my webinar platform?

URL: https://callhush.com/platforms
Last updated: 2026-07-27

Ten webinar platforms, five capabilities, an honest yes / partial / no in every cell, compiled from each platform's own developer documentation. Including the one capability that is a no everywhere, Zoom included, and why.

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.

- **10**: Platforms in the table below, each read from its own developer documentation
- **5**: Capabilities checked separately: a join event was never counted as evidence of a leave event
- **0**: Rows where mid-session exit detection is a yes. Zoom is not an exception to this

## 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 each part of the sequence needs from your webinar platform*

| 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. |

- **9 of 10**: Platforms above that push a registration event as it happens
- **7 of 10**: Platforms that report a join during the live session, which is what stops us contacting someone already watching
- **0 of 10**: Platforms that report a departure during the live session reliably enough to act on it

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”](https://support.webinarjam.com/en/articles/15369997-create-autoresponder-automation-rules-for-your-webinar), 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”](https://devforum.zoom.us/t/bug-webinar-participant-left-webhook-sometimes-not-fired/69552) 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:** Silent is the operative word. A loud failure is survivable: you see it, you fall back, you tell the client. A silent one means neither we nor you can tell the difference between “nobody left” and “the event stopped arriving,” which makes every report built on it unfalsifiable. That is why this is a no rather than a partial, and why it is not on a roadmap. The people who walked out are picked up with everyone else who did not stay, after the session, from attendance data that does arrive.

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”](https://aevent.com/webinar-behavior-triggers/), 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.

1. **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.
2. **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.
3. **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.
4. **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](https://help.zapier.com/hc/en-us/articles/8496244568589-How-Zap-triggers-work), and the approval terms from [WebinarJam’s API application page](https://support.webinarjam.com/en/articles/15370143-apply-for-an-api-key-for-webinarjam-or-everwebinar). Neither is a claim about how fast anything of ours happens, and you will not find one of those anywhere on this site.

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](https://callhush.com/platforms/zoom-webinars) and [EverWebinar](https://callhush.com/platforms/everwebinar). If you run automated sessions rather than scheduled ones, start with [evergreen webinars](https://callhush.com/evergreen-webinars): it is the page that tells you honestly which half of this fits you. Or [book a call](https://ainora.lt/contact?from=callhush) and bring the name of your platform.

## Pages in this section

- [BigMarker's API: No Leave Webhook, and No Phone Field Either](https://callhush.com/platforms/bigmarker): https://callhush.com/md/platforms/bigmarker.md
- [Demio and Webhooks: What Its API Reports, and When](https://callhush.com/platforms/demio): https://callhush.com/md/platforms/demio.md
- [EverWebinar Webhooks and API: What Is Real-Time and What Is Evaluated Later](https://callhush.com/platforms/everwebinar): https://callhush.com/md/platforms/everwebinar.md
- [StealthSeminar's Leave Webhook: The Event Exists, the Timing Is Undocumented](https://callhush.com/platforms/stealthseminar): https://callhush.com/md/platforms/stealthseminar.md
- [WebinarJam API: Is There a Webhook for an Attendee Leaving Mid-Session?](https://callhush.com/platforms/webinarjam): https://callhush.com/md/platforms/webinarjam.md
- [Zoom Webinar API: Is the Attendee-Left Event a Real-Time Webhook or Polling?](https://callhush.com/platforms/zoom-webinars): https://callhush.com/md/platforms/zoom-webinars.md

## Frequently asked questions

### My platform is not in your table. Does that mean no?

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.

### Do you support Zoom Events?

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.

### Is the mid-session exit column ever going to become a yes?

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.

### Which platform should I be on if I want all of this to work?

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.

### How current is this table?

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.

---

CallHush is operated by AINORA, MB (Vilnius, Lithuania). Book a call: https://ainora.lt/contact?from=callhush