
How it fits together
Every call your agents handle becomes a conversation with a turn-by-turn transcript and its recording. Analysis surfaces per-call observations; you promote the recurring ones into findings — durable, shareable issues — and record the fix as a change. For the whole pipeline end to end, see How Zelto works.The core ideas
- Agents — the voice and human agents in your organization.
- Conversations — each call’s turn-by-turn transcript and recording, with on-demand AI summaries.
- Findings — durable issues attached to the exact transcript moments that caused them.
- Changes — agent-scoped fixes for one or more findings.
- Experiments — compare real calls from two prompt-version groups on the monitors that matter to a change.
- Integrations — voice ingest, Slack and Google Chat notifications, Linear issue-from-finding, and open API / MCP access.
Works with your stack
Connect Vapi or Retell with an API key and a webhook URL you paste into the provider, forward finished sessions from a LiveKit worker, or POST calls from any other stack — Bland, Pipecat, or your own. They all land in the same place, tagged with the originating agent. Not sure which path is yours? See Connect a voice provider.Where to go next
Quickstart
Connect a provider and see your first transcript in five minutes.
How Zelto works
The whole pipeline end to end, from call to finding to change.
Guides
Triage findings, audit agents, and operate the platform.
API & MCP
Read everything programmatically over REST or MCP.

