How the wizard works
Instead of manually writing complex instructions, the wizard leads you step by step. It knows your current setup (deployed instruction and available tools), guides you through targeted questions, creates instruction drafts from scratch or building on existing ones, battle-tests changes, and manages versions for easy deployment.
Getting started
Open the wizard via Manage Instructions. It first asks for the agent's primary language, then offers to build on your existing deployed instruction or start from scratch. Building on an existing one is ideal to modify greetings or tone, adjust sales scripts and flow, add edge-case handling, refine product search, or update lead qualification.
The instruction building process
1. Business context. The wizard asks questions like "What's your store brand name, and what do you sell?".
2. Draft creation. It builds a draft with Role and Objectives, Greeting Protocols, Lead Qualification (from your statuses and tags), Product Search Protocol, Tool Usage Guidelines and Error Handling.
3. Customization. Request targeted changes (e.g. "remove sample greeting phrases") and the wizard patches the instruction.
Battle testing
Battle testing validates changes via simulated scenarios: a test persona interacts with your agent, the agent responds using the draft instruction (not the deployed one), and the wizard checks whether it follows the new instructions. This validates changes, prevents breaks before deployment, and can run several scenarios at once.
Deployment & versions
When satisfied, click Deploy: the instruction gets a version number (V2, V3…), becomes active for customers, and syncs to your dashboard. The wizard keeps a version history so you can deploy any version, compare changes, and make incremental updates.
Scope & limitations
The wizard configures sales agent instructions: behavior, conversation flow, sales scripts, tool usage, response patterns and error handling. It works with an abstract set of tools (product search, lead management, scheduling) regardless of the underlying system.
It cannot configure channel-specific settings, attachment handling, integration details (CRM field mappings, API credentials), knowledge base content, or system configurations, those live in their dedicated tabs.
Message usage & best practices
All wizard interactions count toward your message usage; event history is kept for 60 days. Be specific, give context and request examples; start simple and test frequently; deploy incrementally and keep version control.