Behaviour Settings

The Behaviour tab controls how the assistant thinks and acts — its tone, its language, its boundaries, and its memory across conversations. The behaviour instructions (the system prompt) are the single biggest lever on answer quality.

Settings

Setting	Default	What it does
Assistant behaviour (context)	empty	The system instructions. This is the prompt that shapes every answer — tone, language, rules, and boundaries. Supports Markdown (headings, bold, lists, code).
Persist conversation between sessions	on	When on, a returning visitor sees their previous conversation. When off, every session starts fresh.
Pass previous conversation as context	on	When on, earlier turns are sent to the model so it can reference what was already discussed. When off, only the current question is considered — each answer stands alone.

Writing Good Instructions

Think of behaviour instructions as a brief you hand to a new team member: tell them what they should do, how they should sound, and what they should never do. Keep them short, direct, and specific.

Instructions that work well:

Answer in the user's language.
Keep a friendly, concise tone — no more than 3 paragraphs per answer.
Only answer from the connected knowledge base. If you don't know, say so
and suggest the user contacts support@acme.com.
Never discuss competitors or share pricing not in the dataset.
When a question is unclear, ask a follow-up before guessing.

Instructions that don't work well:

You are a helpful assistant.
Be nice.
Answer questions.

The first example gives the assistant concrete rules it can follow or break; the second is so vague it changes nothing.

Conversation Memory

The two memory settings work together:

Persist + Pass context = on — the assistant remembers across sessions and

references earlier turns. Best for ongoing support where a visitor returns to the same topic over days.

Persist = on, Pass context = off — the conversation is saved (the visitor

sees it), but each answer is built from scratch. Good when you want a history log without the cost of long context.

Both off — every visit is a clean slate. Good for public kiosks, anonymous

help centers, or when privacy matters most.

Examples

For a customer-support assistant:

You are the Acme support assistant. Answer only from the knowledge base.
If the answer is not in the knowledge base, say: "I'm not sure about that —
please contact support@acme.com and we'll help you directly."
Keep a warm, professional tone. Use short paragraphs.
Answer in the user's language.

For a product catalog assistant:

You help visitors find the right product. When someone describes a need,
suggest matching products from the catalog and include the price and
a direct link.
If no product matches, say so honestly — don't invent features.
Always show the product name in bold.

For a blog / content discovery assistant:

You help readers find articles and topics on our blog.
When answering, cite the article title and link so the reader can go deeper.
Keep answers brief — two or three sentences, then point to the full article.
Answer in the user's language.

Troubleshooting

If the assistant ignores your instructions, check for conflicting rules — short and clear beats long and clever.
If nothing seems to change after saving, refresh the playground preview.
Markdown formatting (bold, lists, headings) works inside the instructions field.

Test the Assistant Playground