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

# Quickstart

> Sign up, connect a Retell agent, approve its brief, import calls and read your first issues.

This takes you from nothing to a ranked list of problems in your own agent. You need a Retell account with at least one agent, and permission to copy an API key from Retell.

<Note>
  No Retell account yet? New workspaces open on **Northwind Dental**, a read-only demo agent built from synthetic calls across two versions. A banner says so, and its **Connect your agent** button takes you to step 2. Nothing you do there writes to it.
</Note>

<Steps>
  <Step title="Sign up and choose a workspace">
    Open [first-signal-web.pages.dev](https://first-signal-web.pages.dev) and use the sign-up link on **Sign in** to create your account with your work email.

    A workspace holds your agents, calls and issues. You start in a personal workspace. To work with teammates, create an organization from the switcher at the top of the sidebar, then invite people from the **Organization** page. Everyone in an organization sees the same agents.

    <Warning>
      An agent belongs to the workspace it was connected in and cannot be moved. If you will share the agent, create the organization and switch to it before you connect.
    </Warning>

    Paid plans are billed per organization, and a personal workspace stays on the free plan. See [Pricing](/billing/pricing).
  </Step>

  <Step title="Connect a Retell agent">
    Open **Agent config** in the sidebar. On a workspace with no agents of its own the page is titled **Get started**, with a progress bar for **Connect**, **Review brief**, **Import calls** and **See issues**.

    In the **Connect your agent** panel:

    1. Paste your Retell API key (it starts with `key_`) into **Retell key**. Optionally give it a **Name**.
    2. Wait for "Key accepted." Signal asks Retell which agents the key can see.
    3. Choose the agent from **Agent**. If the key can see only one unconnected agent, it is chosen for you.
    4. Select **Connect**.

    Signal reads the agent's configuration and moves on to the brief. Keys, webhooks and more than one agent are covered in [Connect Retell](/guides/connect-retell).
  </Step>

  <Step title="Review and approve the brief">
    While Signal reads the configuration the page says "Drafting the brief". Then **The brief** panel shows a short document: what the agent does, why people call, what a good call is, how calls can end and which parts matter most. Signal cannot know your business, so it asks questions in the **Calibrate** panel beside it. You can also select **Edit** and change the text directly.

    Check three things before you approve:

    * **A call worked when**: the one line every success rate is measured against.
    * **How a call can end**: a transfer stops counting as a failed call only when every transfer ending is marked **Good ending**.
    * **Not this agent's job**: what callers ask for that the agent is not meant to handle.

    Then select **Approve and import**. See [The brief](/concepts/the-brief).
  </Step>

  <Step title="Import calls">
    Approving brings in the latest 500 ended calls from the last 30 days, newest first, then opens **Overview**, which shows the import and then the analysis with counts such as "Imported 240 calls…". The time depends on how many calls there are and how long they are. If a step stops, the page says which one and offers **Import again** or **Analyze again**.

    If the import cannot start, the brief stays approved and **Import production calls** on **Agent config** says why. Calls past your plan's analysed-call allowance are stored and wait for analysis until the period resets or you upgrade.

    After this first import you do not need to import again: Signal brings in new calls on its own. To bring in a different window, see [Connect Retell](/guides/connect-retell#import-calls).
  </Step>

  <Step title="Read your first issues">
    While analysis runs, **Overview** lists **First issues so far**, ranked on the calls analysed up to that point. The order can change as the rest are read.

    When analysis finishes, **Overview** shows **Fix**, the top 3 confirmed defects in priority order, and **Improve**, changes you control that move your numbers. **Issues** in the sidebar has the full lists, and you can narrow **To fix** to **Technical**, **Flow** or **Content**. Patterns whose cause is not established are listed at the bottom of **Issues**, under **Cause not established**. If **Issues** says "Nothing to fix here yet", Signal has not confirmed a defect with an established cause so far. See [Issues](/concepts/issues).

    Open an issue. It names the place, the **Cause**, a **Suggested fix**, **Evidence** quoted from calls, and **By version**, the share of each version's calls with the problem.
  </Step>

  <Step title="Fix one issue, then check it worked">
    Take the top issue and make the change it points to in Retell. [Fix an issue](/guides/fix-an-issue) walks through it, and the [lane](/concepts/lanes) on the issue says who should own it.

    New calls show up on their own within about 15 minutes of ending, and Signal picks up the new version within about 10 minutes of publishing. Once both versions have enough calls, **Agent config** shows what changed and what happened to the numbers, and the issue page says whether the live version fixed the issue. See [Compare versions](/guides/compare-versions).
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Connect Retell" icon="plug" href="/guides/connect-retell">
    Keys, the webhook, importing and more than one agent.
  </Card>

  <Card title="The brief" icon="file-lines" href="/concepts/the-brief">
    What to check before you approve, and what changes when you edit it.
  </Card>

  <Card title="Fix an issue" icon="wrench" href="/guides/fix-an-issue">
    From the board to a change in Retell.
  </Card>

  <Card title="Compare versions" icon="code-compare" href="/guides/compare-versions">
    Read a before and after, and know when to trust it.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.