For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tips & tricks for your agent

An agent is set up quickly and handles calls reliably. This article shows how to optimize specifically and test the agent with realistic tests to check.

Optimize call handling

Keep the greeting short

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 sona. How can I help you?”

Avoid:

  • long greeting phrases

  • several pieces of information at once

  • unnecessary introductions

Make sure to phrase the greeting in spoken language. The text is read aloud exactly as it appears here.

One question at a time

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

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

Run tests

Test different conversation starters

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 follow-up questions appropriately?

Test different wording

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.

Simulate real conversation situations

Intentionally include typical disruptions in tests.

For example:

  • background noise

  • interruptions

  • speaking quickly

Check:

  • does the agent remain understandable?

  • does it respond in a comprehensible way?

  • does the conversation flow remain stable?

Review conversations afterward

Then analyze the 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 flow of the conversation logical?

Long or unclear answers can often be improved with shorter customer questions and more precise content in customer questions or the knowledge base. Check whether information is formulated redundantly, too generally, or contradictorily.

Test again after changes

After changes to knowledge, scenarios, or call handling, short test calls should be made.

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

Check transfers & limitations

Test transfers

Deliberately test transfers multiple times and in different situations.

Check:

  • is the transition announced clearly?

  • does the transfer work reliably?

  • does the handoff work outside business hours too?

Test the agent’s limitations

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

Check:

  • does the agent communicate its limitations clearly?

  • does it ask sensible follow-up questions?

  • does it offer suitable alternatives or transfers?

Carry out external tests

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?

Last updated