Configuration

Configuration is project-level. The settings you define here apply to all your agents - every conversational agent and every guided agent in the bot inherits them. It is where you set the behaviour that shapes every conversation: persona and identity, conversation rules, routing logic, memory, fallback, lifecycle hooks, AI safety, and voice.

Every incoming message is read and routed to the right place - answered directly, handed off to one of your conversational agents, reached through a guided agent, or resolved with a tool - and the response is shaped by these project-level settings. Configuring them well is the single highest-leverage thing you can do for your bot's quality.

This page is the map of the Configuration category. Each section below has its own sub-page; the order shown is the one we recommend you fill them out in.

Note: If you came from the legacy platform, you'll find the same fields here with a few additions for Nexus.

Nexus Tip

Stuck on the wording? Ask Nexus to draft your bot identity from a one-line description, then refine it. It can also tighten an existing identity or add a "never do" rule for you.

Ask the AI layerDraft a bot identity for a calm, professional logistics support assistant that never quotes pricing

Open the Configuration page

In your bot, click AI Agent → Configuration. The page has a left menu grouped into three sections:

• General
  • Profile settings
  • Conversation rules
• Agents
  • Routing logic
  • Memory
  • Lifecycle hooks
  • Fallback
• Others
  • AI safety & conduct (if enabled for your account)
  • Voice settings

Start at Profile settings and work down the list.

What each section does

Section	What it controls	Sub-page
Profile	Persona, bot identity, and welcome message - who your bot is and how it greets users.	Profile
Conversation rules	Persona-level always do / never do guidelines applied to every reply (max 30).	Conversation rules
Routing Logic	Optional plain-English rules that override or refine how each message is routed between agents and tools.	Routing Logic
Memory	Variables shared by all agents across conversations - customer_id, account_tier, and similar shared context.	Memory
Fallback	What the bot does when it can't handle a request, plus retry behaviour for failed input validation.	Fallback
Lifecycle hooks	Optional cross-cutting behaviour - on session start and on inactivity - for nudges, logging, and context injection.	Lifecycle hooks
AI safety & conduct	Content-safety filters on user inputs and bot responses (if enabled for your account).	AI safety & conduct
Voice settings	TTS provider and voice, voice instructions, and VAD tuning for voice channels.	Voice settings

Tip - You don't have to fill in every section. Profile is the only one most bots can't skip; Routing Logic, Lifecycle hooks, and Voice settings are optional and only matter when your use case needs them.

Save and test

After editing any section, click Save. Then go to AI Agent → Agents, click the play (▶) icon on any agent to open the Playground, and send a few test messages. Read each response to confirm the bot is behaving as you intended. For deeper checks - adversarial prompts, regression suites - use the Testing Lab.

If something looks off, it's almost always one of:

• Bot identity too vague → tighten it in Profile.
• Conversation rules contradict → simplify them in Conversation rules.
• Routing is sending messages to the wrong place → add a rule in Routing Logic.

---

Next: Profile - pick a persona, write the bot identity, and set the welcome message.