Behavior

This tutorial walks you through configuring the Behavior section for Atlas, Kirana Group's operations assistant for employees. The three fields you set here (Mission, Personality, and Interaction) are injected directly into the AI's context and have the greatest influence on the quality and tone of every response.

Before you start

• Give the agent a name and avatar in Profile, so you can recognise it in the preview.
• Write down, in a sentence or two, who the agent serves and what it should (and should not) help with. That becomes your Mission.

Scenario used in this tutorial

Two ways to fill in the fields

Each field in the Behavior section can be filled in two ways:

• Type directly. Write your own text in the field. This gives you full control over wording and detail.
• Let AI help. Type a rough idea (or use the existing placeholder), then click the Modify button below the field. The AI rewrites the content to be clearer and better aligned with best practices.

Tip: A practical approach is to write a short rough draft first, then click Modify to have the AI refine it. Review the result and adjust further if needed. For Atlas, the texts below are final, so you can paste them as they are.

Step 1: Open Persona → Behavior

Move your pointer over the icon sidebar on the left edge of the CMS to expand it (on a narrow screen, click the menu button (☰) at the top left instead). Expand the Persona section, then click Behavior.

The Agent Behavior page opens with three editable fields: Mission, Personality, and Interaction. Each one has a short description above it and a Modify button below it.

Step 2: Write the Mission

The Mission field defines what the agent is here to do. It sets the goal and scope for every conversation.

1. Click inside the Mission text area.
2. Replace the existing text with a clear, specific purpose statement.

Scenario value for Atlas:

Atlas helps Kirana Group employees get operational work done right the first time. It answers questions about approval limits, procurement, travel and expense claims, and site safety from Kirana's official SOPs, checks the status of projects and purchase requests, and tells people exactly who has to sign off and what to prepare. It serves project managers, site supervisors, and procurement and finance staff across Kirana's offices and project sites.

Tips for writing an effective mission:

• State the subject area or domain (operations, HR, IT support, and so on).
• Describe the type of help the agent provides (policy answers, status checks, troubleshooting).
• Name who it serves. Atlas lists its users by role, so it can pitch answers at the right level.
• Mention constraints where relevant. Atlas answers "from Kirana's official SOPs", not from general knowledge.

Step 3: Define the Personality

The Personality field specifies the agent's character traits. These traits guide tone, word choice, and level of formality in every response.

1. Click inside the Personality text area.
2. List the traits that match the intended audience and use case.

Scenario value for Atlas:

Precise, calm, and dependable. Atlas is policy-first: it never guesses a rule, says plainly when something is not covered by the SOPs, and points to the person who can decide. Friendly and respectful, but businesslike.

"Never guesses a rule" matters for an operations assistant. A wrong approval chain costs more than an honest "the SOPs do not cover this".

Common trait combinations to consider:

Step 4: Describe the Interaction style

The Interaction field explains how the agent communicates: its approach and methods for helping users. This is different from personality. It describes behavior patterns, not character traits.

1. Scroll down to the Interaction field.
2. Describe how the agent structures responses, handles ambiguity, and manages edge cases.

Scenario value for Atlas:

Keep answers short and actionable: lead with the answer (who approves, what to do next), then the conditions. Name the SOP section the answer is based on. When an amount, department, or site changes the answer, ask for it first. Use bullet lists for steps and approval chains. Reply in the user's language.

Things to specify in Interaction:

• Whether the agent asks clarifying questions before answering (Atlas asks for the amount, department, or site when it changes the answer)
• How it structures long answers (numbered steps, headers, bullets)
• How it handles off-topic or sensitive questions
• Whether it proactively suggests next steps or waits to be asked

Step 5: Save changes

1. Click Save at the bottom of the page.
2. The CMS asks Are you sure to save your changes?
3. Click Yes.

Check the result

The updated Mission, Personality, and Interaction values are injected into the agent's system context the next time a conversation is started. Existing active conversations are not affected until they begin a new session.

To verify the changes, use the preview panel on the right side of the page. Click its reload button to start a fresh conversation, then ask something outside the mission:

Can you help me with my personal tax return?

Atlas should decline politely, explain that its role is limited to Kirana's operational procedures, and point you somewhere more suitable.

You can also ask a question inside the mission, for example "Who has to approve a project worth $2.5 million?". At this point Atlas has no SOPs yet, so it should say it cannot confirm the approver rather than invent a rule. That honest answer is the personality at work. You give it the real policy in Documents.

The preview runs your draft. To let end users see the new behavior, publish the agent (see Preview and Publish Changes).

Next steps

• Appearance: match the chat colors to your brand (next step).
• Introduction: write the welcome message that matches this personality.
• Give Your Agent an Identity: see all four Persona pages at a glance.