Skip to main content
Zelto sits on top of your voice stack and turns raw calls into an analyzed, searchable record. This page follows a single call through the platform so you can see how the pieces fit together before you dive into any one of them.

​
The pipeline at a glance

1

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.
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.
3

Analysis examines the call

Each conversation runs through analysis, producing per-call analysis_findings and an on-demand summary.
4

Findings and changes capture what to fix

Recurring problems become findings — durable, org-level issues you triage — and a change records the fix that addresses them.

​
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.