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

# Built-In Tools

> Platform-native tools that are available in every agent without configuration.

**Built-in tools** (also called *system tools*) are tools that msg.Hello ships with itself. They are **automatically available in every agent**, need **no connector**, **no base URL**, and **no credentials**, and they talk to **no external system**. Their logic runs entirely on the platform.

<Info>
  Because built-in tools are available without configuration, they do **not** appear in the connector selection. You enable them directly in the [flow](/en/flows-bauen) at the respective state.
</Info>

## `classify` – classify the request

The central built-in tool is **`classify`**. With it the agent assigns the caller's request to **exactly one** of the categories you have defined. The chosen category becomes the **response code** on which your flow transitions branch.

<CardGroup cols={2}>
  <Card title="What it does" icon="tags">
    Picks the matching one from your categories (e.g. `termin`, `rezept`, `sonstiges`) and returns it as a branching code.
  </Card>

  <Card title="When the agent calls it" icon="clock">
    Only once the category is unambiguously established. When in doubt, the agent keeps asking instead of guessing.
  </Card>
</CardGroup>

### How you use it in the flow

<Steps>
  <Step title="Define categories">
    Set the allowed categories at a state – these are the possible results of the classification.
  </Step>

  <Step title="Link transitions">
    Connect each category to the target state the agent should switch to for that request.
  </Step>

  <Step title="Test">
    Check with a [test call](/en/agenten-testen) whether typical requests are classified correctly.
  </Step>
</Steps>

```
[Greeting & request]
   ── classify → "termin"    →  [Book appointment]
   ── classify → "sonstiges" →  [Forward: to practice]
```

<Note>
  `classify` is **fully live**. It works locally and without side effects: no external call, no database, no stored states.
</Note>

## Distinction: forwarding & hanging up

**Forwarding** to a human and **hanging up** are not tools but **terminal states** in the flow. They also work without any integration. Details on this in the [Building flows](/en/flows-bauen) chapter.

<Tip>
  A useful entry-level agent combines only built-in capabilities: greet, recognize the request with `classify`, and forward if needed. You build out domain-specific automation via [connectors](/en/connectoren) or [MCP servers](/en/mcp-server) afterwards, step by step.
</Tip>