# Tips & tricks for your agent

A sipgate AI agent is quick to set up and handles calls reliably. This article shows you how to optimize your **AI phone assistant** with realistic tests and proven best practices.

Among other things, you will learn how to **improve greetings**, **test conversation flows** and **reliably check call forwarding**.

### **Tip 1: Keep the greeting short**

The first few seconds make the difference. A good greeting is clear and concise. The agent states its name and explains how it can help. Nothing more is needed for a good start.

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

In certain cases, the greeting can also be used to point callers to a topic in a targeted way or to ask an initial simple opening question.

Pay attention to:

* Instead of "Good day, this is the sipgate Agent. I'm here to help you with your concerns," better: "Hello, this is Lisa, the digital assistant from sipgate Support. How can I help you?"
* Don't string greeting phrases together
* Get straight to the point<br>

### **Tip 2: One question at a time**

Several questions at once are overwhelming. Ask them one after the other.

Pay attention to:

* Not "What is your name and what is it about?" but first "What is your name?" and then "What is it about?"
* Each question should relate to only one piece of information

Short tests by colleagues or external people often provide more valuable feedback than running them yourself.

### Tips for testing

#### Tip 1: Deliberately vary conversation openings

Callers rarely start with a clear, perfectly worded request. Therefore, test different openings, such as very short greetings from callers, direct concerns, or hesitant starts.

Pay attention to:

* Does the agent reliably recognize the issue?
  * If necessary, supplement the agent's greeting to give callers help phrasing their request, or formulate the first task in the [playbook](/documentation/en/behavior/playbooks.md) so that the agent knows what type of issue to expect. The agent is able to help callers if it cannot assign the stated issue.
* Does the opening remain calm and understandable?
* Does the agent not steer the conversation too early?

#### Tip 2: Test different phrasings

The same issue can be phrased in many ways. Test synonyms, paraphrases, colloquial language, or slightly incorrect terms as well.

Pay attention to:

* Does the agent always lead to the same result?
* Does it ask sensibly or respond unnecessarily?

#### Tip 3: Include real conversation situations

Background noise, interruptions, or very fast speech are part of everyday life. Deliberately include such situations in the tests.

Pay attention to:

* Does the agent remain understandable?
* Does it respond plausibly?
* Does it lose the thread?

#### Tip 4: Review conversations afterward

Later, look at test conversations from the caller's perspective. It quickly becomes clear whether answers are too long, unclear, or redundant.

{% hint style="info" %}
Test conversations can be reviewed in the transcripts of the [analysis in the logged-in area](https://app.sipgate.com/frontdesk-analysis?) .
{% endhint %}

Pay attention to:

* Is the conversation flow logical?
* Are answers clear and not too verbose?
  * A common cause of overly verbose answers is responses that are too long in [customer questions](/documentation/en/behavior/kundenfragen.md) in this case, shorten the corresponding answer.

#### Tip 5: Check call forwarding specifically

When calls are transferred, the transition should work smoothly. Deliberately test call forwarding multiple times.

Pay attention to:

* Is it clearly communicated what happens next?
* Does the transfer also work outside business hours?

#### Tip 6: Test the agent's limits

An agent does not have to be able to solve every issue. What matters is how it handles situations it cannot cover.

Pay attention to:

* Does the agent communicate its limits clearly?
* Does it offer sensible alternatives or transfers?

#### Tip 7: Get external tests

Short tests by colleagues or external people often provide more valuable feedback than running them yourself.

Helpful questions afterward:

* What was unclear?
* Where did you get stuck?
* What worked well?

#### Tip 8: Test again after changes

After adjustments to knowledge, scenarios, or conversation flow, short tests should be part of the process. Three to five test calls after each major change have proven effective.


---

# Agent Instructions: 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:

```
GET https://help.sipgate.com/documentation/en/behavior/tipps-and-tricks-fur-ihren-agent.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.