Summary
Additional Context adds fixed subject + text blocks to your knowledge. Context Sources are trigger-based Q&A entries retrieved when user questions match a description. Both require Rebuild Bot after changes.
Prerequisites
- Edit chatbot → Additional Context or Context Sources tab
Additional Context
Purpose
Store structured extra facts (policies, pricing notes, FAQs) as subject + body text.
Step-by-step
- Open Additional Context
- Click add entry
- Enter Subject (short label)
- Enter Text (up to 10,000 characters)
- Save entry
- Click Rebuild Bot
Features
- Search and filter entries
- Edit or delete existing entries
Context Sources
Purpose
Unlimited entries with:
- Title
- Context Source Description (when to use this entry)
- Response text (what the bot should know)
The bot matches user questions to descriptions and injects response text.
Retrieval modes
| Mode | Behavior |
|---|---|
| Always | Retrieve on every related question |
| When relevant | Only if question matches a source topic |
| When missing | If relevant and answer not already in context (default) |
Step-by-step
- Open Context Sources
- Select retrieval mode at top
- Fill Title, Description, and response fields
- Add entry
- Rebuild Bot
Difference at a glance
| Feature | Additional Context | Context Sources |
|---|---|---|
| Structure | Subject + text | Title + trigger + response |
| Matching | Always in knowledge index | Description-based retrieval |
| Best for | Static facts | Conditional / situational answers |
What triggers a rebuild
| Action | Rebuild needed? |
|---|---|
| Add/edit/delete either type | Yes |
| Change retrieval mode only | Yes |
Limitations
- 10,000 character max per Additional Context entry
- Context Sources depend on description quality — write clear triggers
- Neither replaces main Knowledge Sources for full-site content
Troubleshooting
Symptom: Context source never used
Cause: Description too vague or mode When missing with answer already in KB.
Fix: Sharpen description; try When relevant or Always.
Symptom: Conflicting answers
Cause: Overlapping context and website content.
Fix: Remove duplicate entries; align wording.