Scenarios vs. Knowledge Bases
In One Sentence
Use a Scenario when the agent needs a step-by-step conversational playbook to handle a customer workflow; use a Knowledge Base (KB) when the agent needs to search through documents and articles to answer factual questions.
Why This Guide Exists
A common builder pitfall is pasting large policy documents into scenario prompts or creating redundant scenarios for simple FAQ entries. Understanding when to use playbooks versus document libraries keeps your agent accurate, fast, and easy to maintain over time.
Side-by-Side Comparison
| Dimension | Scenario (Playbook) | Knowledge Base (Document Library) |
|---|---|---|
| Primary Purpose | Defines how to guide the customer through a process | Provides what factual information the agent can look up |
| Structure | Title, trigger description, and conversational prompt instructions | Folders of uploaded PDFs, text files, FAQs, and product manuals |
| Update Frequency | Workflow steps managed inside the agent builder | Dynamic business documentation uploaded and re-indexed |
| Runtime Mechanism | Intent matching activates the scenario prompt for that turn | Semantic retrieval searches indexed document chunks |
| Best Used For | Returns, subscription cancellations, order lookups, onboarding | Return policies, warranty terms, fee schedules, product specs |
| Scope | Configured directly on the agent draft | Shared across workspace; attached to agents or specific scenarios |
Decision Flowchart
When adding a new capability to your agent, use this decision framework:
1. Is this a step-by-step workflow?
If the agent must ask specific questions in order, verify data, or call live actions:
- Solution: Create a Scenario.
- Example: "Ask for order ID → check eligibility → issue refund via tool → send confirmation."
2. Is this factual information that changes over time?
If the agent needs reference material that operations teams update regularly without changing conversational logic:
- Solution: Upload to a Knowledge Base.
- Example: Detailed return policy text, product specification sheets, and international shipping rates.
3. Do you need both together?
For complex customer journeys, the scenario handles the conversation flow, while the attached Knowledge Base supplies the factual policy details.
- Solution: Create a Scenario and attach the relevant Knowledge Base.
- Example: The agent follows a "Return Request" scenario while searching the "Shipping & Returns KB" for policy exceptions.
4. Is it a strict security or compliance boundary?
If the instruction is an absolute mandate that must never be violated across any conversation:
- Solution: Add a Rule in the agent configuration.
- Example: "Never disclose customer PII without prior verification."
Next Steps
Now that your configuration and playbooks are established, test your agent interactively in Testing Agents.