Appearance
Teach Your Agent About Your Company
Upload context files and create "when relevant" guidelines so your agent automatically applies company-specific knowledge when it matters.
What You'll Use
| Feature | Purpose |
|---|---|
| Context Files | Background knowledge the agent can reference |
| Guidelines | Rules that shape agent behavior |
| Activation Modes | Control when context and rules apply (always vs. when relevant) |
Step 1: Add an Always-Active Context File
Context files give your agent domain knowledge it would not otherwise have.
- Go to Context in the sidebar.
- Click New Context File.
- Enter a title like "Product Overview" and paste your company's core information:
Acme Analytics is a B2B SaaS platform for real-time business intelligence. Our product tiers are Starter ($29/mo), Professional ($99/mo), and Enterprise (custom pricing). We serve 2,400 customers across 18 countries. Our primary differentiator is sub-second query performance on datasets up to 10TB.
- Set Activation to Always.
Always-active context files are included in every conversation and run. Use this for foundational knowledge the agent should always have.
Step 2: Add a When-Relevant Context File
Not everything needs to be loaded every time.
- Create another context file titled "Engineering Escalation Process".
- Add department-specific content:
When a P1 engineering incident is reported: (1) Page the on-call engineer via PagerDuty, (2) Open a Jira ticket in the INCIDENT project, (3) Post to #incidents in Slack within 15 minutes, (4) Schedule a post-mortem within 48 hours of resolution.
- Set Activation to When Relevant.
This file is only included when the agent detects the conversation is about engineering incidents or escalations. It saves context window space for unrelated tasks.
INFO
"When relevant" uses semantic matching — the agent does not need to see the exact words "engineering escalation" in your message. A question like "what do we do when the system goes down?" will still trigger it.
Step 3: Add a When-Relevant Guideline
Guidelines shape behavior. Combined with "when relevant" activation, they apply only in the right situations.
- Go to Guidelines in the sidebar.
- Click New Guideline and fill in:
| Field | Value |
|---|---|
| Name | Use official product name and pricing |
| Content | When writing customer-facing content, always use the exact product name "Acme Analytics" (not abbreviations). Reference pricing tiers exactly as defined in the product overview. Never round or estimate pricing. |
| Activation | When Relevant |
This guideline only fires when the agent is writing something customer-facing that mentions pricing or the product name.
Step 4: Test It
- Open the Chat panel and select an agent.
- Ask: "Write a short email introducing our product to a prospect."
The agent uses the always-active product overview for facts and applies the when-relevant guideline for exact naming and pricing.
- Now ask something unrelated: "What's a good agenda for a team retrospective?"
The product overview is still available (always active), but the pricing guideline does not activate because the topic is unrelated.
TIP
Keep always-active files small (under 500 words). Put detailed reference material in when-relevant files so the agent only loads what it needs.
What to Try Next
- Context Files — Static vs. dynamic context, URL syncing
- Writing Guidelines — Categories, scoping, and best practices
- Effective Guidelines — Specific, actionable rules that work