21 platforms. Three ways in.
This page is generated from the same catalog our coverage map runs on — if the product can’t capture it, this page doesn’t claim it. Three ways in, in order of preference:
- Native
- Paste an API key once; the platform's signed webhooks flow straight in.
- One URL
- Paste your capture URL into the platform's webhook setting — exact click-paths provided. Every payload is kept raw, then decoded.
- Email-forward
- Auto-forward the platform's summary emails to your capture address. Summary-only sources are recorded one-sided, and the record says so.
Keep whatever AI you have. Route your number through Anzuna.
Some phone AIs live inside all-in-one platforms that keep their conversations to themselves. The number is the way past that. Forward your business line to an Anzuna number, or move your number over; we answer with a recording notice and pass the call straight through to your AI, untouched. Every call is monitored against your rulebook.
Because it works at the carrier level, one number covers every voice vendor you run — and any you add later.
Voice agents
Connect natively — paste your Retell API key
Connect natively — Vapi webhook integration
Recipe — point its post-call webhook at your capture URL
Recipe — point its call-completion webhook at your capture URL
Recipe — point its post-call webhook at your capture URL
Chat agents
Recipe — webhook or email-forward from Tidio
Recipe — forward Chatbase conversations to your capture URL
Recipe — Intercom webhook to your capture URL
Recipe — Botpress webhook to your capture URL
Recipe — Crisp webhook to your capture URL
Recipe — forward Voiceflow transcripts to your capture URL
AI receptionists
Recipe — workflow Custom Webhook to your capture URL
Recipe — point its post-call webhook at your capture URL
Recipe — via Zapier to your capture URL
Caveat Goodcall's data feed doesn't include transcripts, so coverage stays partial — you'll see that calls happened, not what was said.
Auto-forward its summary emails to your capture address
Recipe — point its webhook at your capture URL
Auto-forward its summary emails to your capture address
Phone systems
Recipe — Dialpad webhook to your capture URL
Auto-forward its call summary emails to your capture address
Auto-forward its call summary emails to your capture address
Messaging
Connect your business email — mail your AI sends or receives is captured automatically
Caveat Only mail your AI sent or received is kept. Personal mail is never stored — the check happens before anything is saved.
ManyChat offers no conversation export today — no API for message history, no summary emails. The moment a path exists, it joins this page. Tell us it matters and we’ll push on it.
Built your own agent? Send us its traces.
Instrumented custom agents can export OpenTelemetry GenAI traces straight to Anzuna: point your OTLP/HTTP exporter (JSON) at /api/otlp/v1/traces with your capture token as the bearer. Spans carrying gen_ai.* prompt/completion attributes or message events become monitored conversations; everything else is kept as raw evidence. The GenAI conventions are still pre-stable, so we pin the version we decode; unrecognized shapes are kept raw and decoded as they’re recognized.
Run something else?
The capture URL accepts any platform that can send a webhook — unknown formats are kept raw, decoded as they’re recognized, and nothing is thrown away. And “request a platform” inside the app writes a ledgered demand signal that steers what we build next.