Manage Chatbots
What Management Covers
After creation, management focuses on:
- Updating basic fields (name, description, use case)
- Updating knowledge sources (text, website, Q&A, files)
- Controlling lifecycle status
- Monitoring behavior and quality
Editing Knowledge Sources
Use the same Knowledge Sources tabs used in create flow:
- Text
- Website
- Q&A
- Files
Rules still apply on update:
- At least one source must remain
- Limits are enforced:
- 200,000 chars text
- 50 files
- 300 Q&A pairs
Status Management
Use status intentionally:
Draft: not ready for productionTraining: knowledge rebuild in progressActive: should answer normallyOnHold: must not answer
Set OnHold during major source changes, policy reviews, or incident handling.
Operational Notes
- Knowledge updates can trigger expensive rebuild operations.
- Status transitions should be visible to operators.
- Keep source data clean to improve retrieval quality.
What Not To Do Here
Do not use chatbot config as a replacement for agent orchestration.
For:
- Conditional tool execution
- Human approvals
- Multi-step agent reasoning
Use Workflows and agentic nodes.
Recommended Process
- Duplicate/prepare changes in non-production flow (if needed).
- Update sources.
- Move through
Training. - Validate with test conversations.
- Set
Active. - Use
OnHoldimmediately if behavior is unsafe.
Screens In This Flow





