The pipeline at a glance
A provider sends a call
Your voice provider hands each call to Zelto — Vapi and
Retell over native webhooks, LiveKit and custom stacks by forwarding the
finished session to
/webhooks/calls. Every payload is recorded in the
append-only webhooks log first, so ingestion is always replayable.Zelto stores the conversation
The payload becomes a conversation with a turn-by-turn
transcript, and the recording is re-hosted on Zelto
storage so the audio outlives the provider’s TTL.
Analysis examines the call
Each conversation runs through analysis, producing per-call
analysis_findings and an on-demand summary.You operate
Buckets group related calls so your team can analyze or hand off
a set together.
Findings vs. solutions
These two nouns are easy to conflate. A finding is the durable record of a problem — “voicemail not detected on 12% of calls” — and it gathers its evidence from the calls you link to it. A solution is the record of the fix: an agent-scoped change that addresses one or more findings, with an owner and a workflow status. You triage findings; you ship solutions. See Findings and Solutions.What’s automatic, what’s yours
Zelto does the ingestion and analysis for you; the judgement stays with your team.| Automatic | Yours |
|---|---|
| Ingesting calls from connected providers | Grouping calls into buckets to analyze together |
| Storing transcripts and re-hosting recordings | Reading the transcripts and recordings behind a finding |
| Per-call analysis findings and summaries | Curating durable findings and proposing solutions |
| Re-hosting recordings past the provider’s TTL | Pushing findings to Linear and tracking them to done |
Where to next
Quickstart
Get your first transcript in five minutes.
Connect a voice provider
Pick the right integration and verify your first call.
Guides
Practical walkthroughs for triaging findings, auditing agents, and operating the platform.
Integrations
Every voice provider, notification channel, and issue tracker.