> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/ai-agents/en/behavior/tipps-and-tricks-fur-ihren-agent.md).

# Tips & tricks for your agent

A sipgate AI Agent is set up quickly and handles calls reliably. This article shows how you can **optimize it specifically** and test the agent with **realistic tests** .

### Optimize conversation flow

<details>

<summary><strong>Keep the greeting short</strong></summary>

A good greeting is clear, direct, and phrased naturally. The agent should briefly introduce itself and explain how it can help.

**Example:** “Hello, this is Lisa, the digital assistant from sipgate. How can I help you?”

Avoid:

* long greeting phrases
* multiple pieces of information at once
* unnecessary introductions

{% hint style="info" %}
Make sure to phrase the greeting in spoken language. The text will be read out exactly as it appears here.
{% endhint %}

</details>

<details>

<summary><strong>One question at a time</strong></summary>

Several questions at once make it harder to get the conversation started. Each question should relate to only one piece of information

Instead of: **“What is your name and what is it about?”**\
Better: **“What is your name?”, “What is it about?”**

</details>

### Carry out tests

<details>

<summary><strong>Test different ways of starting a conversation</strong></summary>

Callers phrase their concerns differently.

**Test:**

* direct concerns
* short answers
* unclear wording
* uncertain conversation starters

**Check:**

* does the agent reliably recognize the concern?
* does the conversation remain understandable?
* does the agent ask sensible follow-up questions?

</details>

<details>

<summary><strong>Test different wordings</strong></summary>

The same concern can be described in different ways.

**Test:**

* Synonyms
* colloquial language
* alternative terms
* incomplete statements

The agent should respond as consistently as possible.

</details>

<details>

<summary><strong>Simulate real conversation situations</strong></summary>

Deliberately include typical disturbances in tests.

**For example:**

* background noise
* interruptions
* fast speaking

**Check:**

* does the agent remain understandable?
* does it respond plausibly?
* does the conversation flow remain stable?

</details>

<details>

<summary><strong>Review conversations afterward</strong></summary>

Then analyze test conversations in the transcripts.

**Pay attention to:**

* Are the answers understandable?
* Are the answers too long?
* Does the agent repeat itself unnecessarily?
* Is the conversation flow logical?

Long or unclear answers can often be improved by shorter customer questions or more precise answers.

</details>

<details>

<summary><strong>Test again after changes</strong></summary>

After changes to knowledge, scenarios, or conversation flow, short test calls should be carried out.

It has proven effective to have **3–5 test calls** after each major change.

</details>

### Check transfers & limits

<details>

<summary><strong>Test transfers</strong></summary>

Deliberately test transfers several times and in different situations.

**Check:**

* is the transition announced clearly?
* does the transfer work reliably?
* does the handover also work outside business hours?

</details>

<details>

<summary><strong>Test the agent’s limits</strong></summary>

An agent does not solve every issue. What matters, however, is how it handles unclear or unsupported situations.

**Check:**

* does the agent communicate its limits clearly?
* does it ask sensible follow-up questions?
* does it offer suitable alternatives or transfers?

</details>

<details>

<summary><strong>Conduct external tests</strong></summary>

Tests by colleagues or external people often provide more realistic feedback than your own runs.

**Helpful questions:**

* What was unclear?
* Where did the conversation get stuck?
* Which answers seemed unnatural?
* What worked well?

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.de/ai-agents/en/behavior/tipps-and-tricks-fur-ihren-agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.