Research Note CA-2026-04
Which voice AI platforms can start a call from a business event?
A comparison of inbound business-event coverage across voice-AI platforms, measured against Callable's production catalogue of 83 triggers and 30 days of live event traffic.
Published · Measured 19 July – 17 August 2026
83 triggers
Measured — published methodCallableAI holds a bindable catalogue of 83 inbound business-event triggers across 14 applications — CRM, email, calendar, spreadsheet and billing events that start a phone call directly, with no Zapier, Make or n8n layer in between. In a scan of published vendor documentation we found no other voice platform shipping any.
Measured Catalogue counted 17 August 2026
Method
- Counted from the production trigger registry on 17 August 2026, restricted to current and enabled definitions. Superseded versions and disabled entries are excluded.
- The distinction being counted matters, because two different things are both called “webhooks”. Call-lifecycle webhooks point outward: the platform tells your server that a call it already placed has started, ended or been analysed. Every vendor ships those. They are reporting, not initiation.
- An inbound business-event trigger points the other way: something happens in your stack — a deal moves stage, a form email lands, an invoice fails — and that event causes a call to be placed. It needs OAuth to the source app, a subscription per watched resource, resolution of the event to a dialable number, and enqueueing against the right agent and calling window.
- Competitor figures were read directly from each vendor's public documentation in August 2026, not inferred.
Inbound business-event triggers, by platform — competing platforms, not parts of Callable
| Platform | Documented event surface | Inbound triggers | How a CRM event starts a call |
|---|---|---|---|
| Retell AI | 3 webhook events (call started, ended, analyzed) | 0 | Your own integration calls the create-call API |
| Vapi | ~15 server-message types, all describing its own call | 0 | Your own integration calls the create-call API |
| Bland AI | Post-call webhook; mid-call tools via REST | 0 | Vendor positions Zapier as the connective layer |
| ElevenLabs Agents | Post-call webhook, fires on completion | 0 | Third-party automation |
| Synthflow | Call webhooks; app coverage via Zapier/Make listings | 0 first-party | Zapier or Make workflow |
| Callable | Call-lifecycle events plus a per-agent inbound catalogue | 83 across 14 apps | Bind the trigger to the agent; the event enqueues the dial |
The catalogue
| Application | Triggers | Examples |
|---|---|---|
| HubSpot | 26 | New or updated contact, deal, company, ticket; form submission |
| Stripe | 11 | New subscription, failed payment, abandoned cart, dispute |
| Streak | 11 | Box created or moved, stage change, new task |
| Pipedrive | 6 | New deal, updated person, stage movement |
| Gmail | 5 | New email, new labelled email, new attachment |
| Google Calendar | 5 | Event created, cancelled, starting soon, ended |
| Outlook Calendar | 4 | Event created, updated, cancelled |
| Aircall | 4 | Call ended, voicemail left, contact created |
| Google Sheets | 3 | New row, row updated |
| Microsoft Outlook | 3 | New email, new contact |
| GoHighLevel | 2 | New or updated contact, opportunity change |
| Microsoft Excel | 1 | New worksheet row |
| Callable native | 2 | Platform-generated and canary triggers |
What this number does not say
- “0 inbound triggers” means none documented publicly, established by reading official docs in August 2026. It is not proof that no private or beta capability exists, and vendors ship continuously — a first-party catalogue could appear at any time.
- General automation tools have far more triggers than 83. None of them can dial. The claim is not that we have the most triggers; it is that we are the only voice platform where the trigger and the phone call are the same product.
- Competitors do have webhooks. They are call-lifecycle webhooks that report on calls you already launched, not inbound triggers that launch one. Saying they “have no webhooks” would be wrong.
Cite this
Research Note CA-2026-04 (PDF, 3 pages)Callable AI (2026). The trigger-surface gap: which voice AI platforms can start a call from a business event? Research Note CA-2026-04, 17 August 2026.
0.19 seconds
Measured — published methodMedian time from receiving a business event to the resulting call being queued for dialling — measured across 3,368 live customer webhook events over 30 days. The 90th percentile is 0.32 seconds, and 94.8% queue within one second.
Measured 19 July – 17 August 2026
Method
- The production event log for the 30 days to 17 August 2026: 3,522 real customer events across 49 deployed listeners. 3,400 fired a call, 120 were correctly gated by calling window, consent or duplicate suppression, and 2 failed their configured condition.
- Latency is measured from webhook receipt to dial enqueue. 154 scheduled and polling triggers are excluded because their timing is set by the customer, leaving 3,368 webhook-sourced events.
- Medians and percentiles are reported rather than means because a 3.6% tail (121 events) exceeded 60 seconds. Those are replays and backfills of previously received events, not live delivery.
By source
| Source | Events (30d) | Median receipt → dial queued |
|---|---|---|
| Gmail | 2,157 | 0.19 s |
| Google Calendar | 1,080 | 0.17 s |
| HubSpot | 70 | 0.22 s |
| Stripe | 20 | 0.18 s |
| Google Sheets | 17 | 0.20 s |
| Streak | 13 | 0.20 s |
| Pipedrive | 11 | 0.20 s |
| All webhook sources | 3,368 | 0.19 s median · 0.32 s at p90 |
What this number does not say
- This measures one hop — event received to dial queued — not end-to-end speed to lead. It does not include the time the source application took to emit the event, nor the time from queue to the phone actually ringing. Do not present it as time-to-contact; those are different quantities and our end-to-end figure is still a product target rather than a measurement.
- Event volumes reflect current adoption of the trigger surface among CallableAI tenants, not platform capacity.
- The useful comparison is not against a stopwatch but against the alternative architecture: a polling automation on a standard plan checks for new records on an interval measured in minutes, which spends most of the speed-to-lead window before anything dials.
Cite this note
Callable AI (2026). The trigger-surface gap: which voice AI platforms can start a call from a business event? Research Note CA-2026-04, 17 August 2026.
Deployed white glove. Backed by an SLA.
CallableAI works with organisations that need quality, volume and compliance to hold at once. Bring us your requirements — we'll scope the deployment, the rollout and the SLA with you.