> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zelto.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How Zelto works

> From a connected provider to conversations, findings, and solutions — the whole platform end to end.

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

<Steps>
  <Step title="A provider sends a call">
    Your [voice provider](/docs/integrations) 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.
  </Step>

  <Step title="Zelto stores the conversation">
    The payload becomes a [conversation](/docs/conversations) with a turn-by-turn
    [transcript](/docs/conversations), and the recording is re-hosted on Zelto
    storage so the audio outlives the provider's TTL.
  </Step>

  <Step title="Analysis examines the call">
    Each conversation runs through analysis, producing per-call
    `analysis_findings` and an on-demand summary.
  </Step>

  <Step title="Findings and solutions capture what to fix">
    Recurring problems become [findings](/docs/findings) — durable, org-level issues
    you triage — and a [solution](/docs/solutions) records the fix that addresses
    them.
  </Step>

  <Step title="You operate">
    [Buckets](/docs/buckets) group related calls so your team can analyze or hand off
    a set together.
  </Step>
</Steps>

## 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](/docs/findings) and [Solutions](/docs/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](/docs/buckets) to analyze together                       |
| Storing transcripts and re-hosting recordings | Reading the transcripts and recordings behind a [finding](/docs/findings)              |
| Per-call analysis findings and summaries      | Curating durable [findings](/docs/findings) and proposing [solutions](/docs/solutions) |
| Re-hosting recordings past the provider's TTL | Pushing findings to [Linear](/docs/integrations/linear) and tracking them to done      |

## Where to next

<Columns cols={2}>
  <Card title="Quickstart" href="/docs/quickstart" icon="rocket">
    Get your first transcript in five minutes.
  </Card>

  <Card title="Connect a voice provider" href="/docs/guides/connect-a-voice-provider" icon="phone">
    Pick the right integration and verify your first call.
  </Card>

  <Card title="Guides" href="/docs/guides/triage-findings" icon="book-open">
    Practical walkthroughs for triaging findings, auditing agents, and operating the platform.
  </Card>

  <Card title="Integrations" href="/docs/integrations" icon="plug">
    Every voice provider, notification channel, and issue tracker.
  </Card>
</Columns>