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

# Behaviour and style

> Tell the agent how to behave, and adjust the tone so it sounds like you.

Your agent reads your guidelines every time it takes a call or a chat.

You'll find them on the agent under **Teach** → **Guidelines**.

> [!NOTE]
>
> Guidelines take effect when you publish the agent. See [Publishing your changes](https://help.verbu.com/en/getting-started/publishing.md).

## What the agent already does on its own

You don't need to write anything about ordinary conversation. The agent sounds like a person, is honest about what it knows and doesn't know, and keeps a natural rhythm.

Use the guidelines for what's specific to your business.

## The agent adapts to the channel

The same agent can take phone calls and chats. It knows on its own how to behave:

* **On the phone** it speaks naturally with pauses. It reads numbers, dates, and prices out loud the way you'd say them yourself. "Thursday the 14th of May", not "14/05".
* **In chat** it splits the answer into short paragraphs with bold words and links.

You don't need to do anything to make this work.

## Languages

If you've set up several languages under **Turn on** → **General**, the agent switches between them on its own as it goes. If the user starts in English halfway through a Danish call, it continues in English without asking.

You don't need to write anything about switching languages.

## General instructions

At the top of the page is **General instructions**. Click **Edit**, and write what the agent can't know on its own:

* Who the agent works for, and what role it plays
* What you sell or help with
* Things it **must not** do or promise
* The words you use for your products

A good example:

> You work as a receptionist for Acme Dental. Be friendly and a little formal.
>
> Never promise a price without checking with a dentist first.
>
> If the user has acute pain, transfer them to the on-call dentist right away.

Keep it short. Three to five sentences usually works best. If the list keeps growing, some of it probably belongs in [Agent knowledge and training](https://help.verbu.com/en/agent-behaviour/knowledge-and-training.md).

## Individual guidelines

Below the general instructions are three groups. Click **New** to create one, or choose the group from the menu next to the **New** button at the top.

| Group | Used for |
| - | - |
| **Communication style** | Tone and phrasing. These apply to chat conversations. On the phone, the agent follows the voice you've chosen |
| **Context and clarification** | When the agent should ask for more before it answers |
| **Content and sources** | What it may answer from, and what it should leave alone |

Each guideline has a **Title** and a text. Under **Applies to** you choose **All conversations** or **Chat conversations**.

If you type `@` in the text, you can refer to a workflow, a data connector, a built-in tool, or an integration action.

## What you shouldn't write

* "Be friendly". It already is.
* "Listen before you answer". It already does.
* "Don't say you're an AI". The agent is honest about what it is if someone asks. Guidelines can't change that.
* Long explanations of your products. Those belong in [Agent knowledge and training](https://help.verbu.com/en/agent-behaviour/knowledge-and-training.md).
* Word-for-word scripts. Guidelines are guidelines, not lines to read out.

## Adjust the tone

You write the tone in the same place. One sentence is often enough:

* **More warmth:** "Be warm and welcoming."
* **Shorter answers:** "Keep answers short, at most two sentences."
* **More formal:** "Be professional and a little formal."
* **More calm:** "Take your time, and let the user finish talking."

## How to test your way there

1. Go to **Test** → **Live test** on the agent.
2. Start a phone or chat conversation, and ask three or four realistic questions.
3. Listen for the feel, not just for mistakes. Does it sound like you?
4. Fix one thing at a time, and try again.

You don't need to publish to test. Live test uses your draft.

## If something still doesn't work

| Symptom | Try this |
| - | - |
| The agent promises things it shouldn't | Spell it out clearly. "Never promise a price" works better than "Be careful with prices" |
| It sounds cold | Write "Be warm and welcoming" |
| It talks too long | Write "Keep answers short, at most two sentences" |
| It asks "Did that answer your question?" every time | Write "Only ask if the answer was enough when the user sounds unsure" |
| It uses the wrong words for your products | Add them under [Pronunciation](https://help.verbu.com/en/agent-behaviour/pronunciation.md) |
| None of it works | Check that you've clicked **Publish** |

## Next steps

* Make sure the agent knows what it's talking about: [Agent knowledge and training](https://help.verbu.com/en/agent-behaviour/knowledge-and-training.md)
* Get it to say names correctly: [Pronunciation](https://help.verbu.com/en/agent-behaviour/pronunciation.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.