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

# Quickstart

> Your first agent in 5 minutes.

In just a few minutes, build your first voice agent: it greets callers, recognizes their request and transfers them to the right team – with no connection to a business system at all.

<Frame caption="In under 2 minutes: create and configure an agent in the portal.">
  <img src="https://mintcdn.com/msg-hello/N3O-B12QNjCabj-J/images/schnellstart-placeholder.svg?fit=max&auto=format&n=N3O-B12QNjCabj-J&q=85&s=05d781bace40f95128edd86db2ac2c19" alt="Quickstart video – coming soon" width="1280" height="720" data-path="images/schnellstart-placeholder.svg" />
</Frame>

## Your first agent in 5 steps

As an example, we build a **reception agent** that transfers callers to the right team depending on their request.

<Steps>
  <Step title="Create the agent">
    Create a new agent through the **agent wizard**. Give it a name and add a short **greeting**, e.g. "Hello, you have reached reception. How can I help?"
  </Step>

  <Step title="Recognize the request">
    In the **flow editor**, add a conversation state where the agent uses the built-in tool **`classify`**. Define the possible categories – e.g. `vertrieb`, `support`, `sonstiges`. The agent assigns the request to exactly one of them.
  </Step>

  <Step title="Transfer">
    Connect each category to a target: add one **transfer** state each with the matching **phone number** (sales, support, front desk). For unclear cases you can instead ask a follow-up question or **hang up**.
  </Step>

  <Step title="Test call">
    Check the agent with a **test call right in the browser** – with no real call. Speak typical requests and see whether they are classified and transferred correctly. Details: [Test agents](/en/agenten-testen).
  </Step>

  <Step title="Publish & assign a phone number">
    Publish the flow as a **version**, activate it and assign the agent a **phone number**. From then on, new calls use the active version.
  </Step>
</Steps>

## Done – what now?

Your agent answers calls, recognizes the request and transfers reliably. From here you extend it step by step:

<CardGroup cols={2}>
  <Card title="Refine conversations" icon="diagram-project" href="/en/flows-bauen">
    More states, follow-up questions and branches in the flow editor.
  </Card>

  <Card title="Connect business systems & tools" icon="plug" href="/en/connectoren">
    Handle real cases – such as booking appointments – via connectors or MCP servers.
  </Card>
</CardGroup>