The pipeline at a glance
1
A provider sends a call
Zelto pulls calls from connected Vapi, Retell, and ElevenLabs accounts;
optional provider webhooks can deliver them sooner. LiveKit and custom stacks
forward the finished session to
/webhooks/calls. Each path produces the
same normalized conversation for downstream analysis.2
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. If your organization uses
Companies, Zelto also attributes the call to the client or
brand supplied by the provider, or to the agent’s default company.
3
Analysis examines the call
Each conversation runs through analysis, producing per-call
analysis_findings and an on-demand summary.Findings vs. changes
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 change 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 changes. See Findings and Changes.What’s automatic, what’s yours
Zelto does the ingestion and analysis for you; the judgement stays with your team.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.