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

# Quickstart: start analyzing calls in five minutes

> Sign up, connect your voice provider, and watch your first call land as an analyzed conversation.

Connect your voice provider, place one test call, and watch it land in Zelto as
a transcribed, analyzed [conversation](/docs/conversations). Start to finish, about
five minutes — and none of it changes how your agents run.

<Steps>
  <Step title="Create an account">
    Sign up at [dashboard.zelto.ai/signup](https://dashboard.zelto.ai/signup) with your email or
    Google. Email sign-up sets a password and emails a 6-digit code — paste it
    back to verify.
  </Step>

  <Step title="Create or join an organization">
    After verifying, answer a few short profile questions, then name your
    organization to create it — your URL becomes `dashboard.zelto.ai/org/<slug>`. If a
    teammate already invited you, or your email domain matches an existing Zelto
    org with domain join enabled, you'll be offered that instead.
  </Step>

  <Step title="Connect your voice provider">
    Go to **Settings → Integrations** and connect the stack your agents run on:

    * [**Vapi**](/docs/integrations/vapi) and [**Retell**](/docs/integrations/retell) —
      paste your provider API key, then copy the webhook URL Zelto shows back
      into the provider. Zelto pulls recordings and metadata for you.
    * [**LiveKit**](/docs/integrations/livekit) or any other stack — Bland, Pipecat,
      in-house — mint an API key and POST each finished call
      to `/webhooks/calls`. See
      [Custom & other providers](/docs/integrations/api-call-upload).

    Not sure which is yours?
    [Connect a voice provider](/docs/guides/connect-a-voice-provider) has a one-table
    decision guide.
  </Step>

  <Step title="See your first conversation">
    Place a test call to your agent — or POST one to `/webhooks/calls` if you
    took the custom path. Within a few seconds a new
    [conversation](/docs/conversations) appears with the transcript and, when
    present, the recording — kept playable even after the provider's link
    expires.

    <Tip>
      Nothing showing up? Open the [agent](/docs/agents) and check its **Connections**
      card — it shows when the last call arrived, or flags an error, so you can
      confirm at a glance that calls are reaching Zelto. See
      [Connect a voice provider](/docs/guides/connect-a-voice-provider#troubleshoot-a-missing-call)
      for the full check.
    </Tip>
  </Step>

  <Step title="Let Zelto surface findings">
    As your calls flow in, Zelto analyzes each one and surfaces
    [findings](/docs/findings) for you — a recurring script failure, a
    mispronounced product name, a tool the agent keeps misusing — grouped into
    durable, org-level issues, so you don't have to read every transcript
    yourself.

    From there, make them yours:

    * Invite teammates from **Settings → Members** so the right people see each
      finding — see [Manage your team](/docs/guides/manage-your-team).
    * Open a [finding](/docs/findings) to see the calls behind it and read the exact
      transcript moments that triggered it.
    * Push any finding to [Linear](/docs/integrations/linear) from the finding's
      panel to hand it to the team that owns the fix.
  </Step>
</Steps>

## Where to go next

* [How Zelto works](/docs/how-it-works) — the whole pipeline, from call to finding to fix.
* [Connect Slack](/docs/integrations/slack) — chat with Zelto and get each agent's
  daily status posted to a channel.
* Script against your data over the [REST API](/api-reference/agents/list-agents) or [MCP](/docs/mcp),
  using a key minted under **Settings → Integrations → API Call Upload**.