What Goes In Knowledge
- Facts the agent can safely repeat to customers
- Policies and exceptions
- Product, listing, or service details
- Public help content
- Internal reference details the agent may need to reason over
- Scoped facts for a specific listing, entity, customer group, or category
What Does Not Belong In Knowledge
- Tone and writing style
- Conditional process instructions
- Tool invocation rules
- Automation timing
- Escalation thresholds
- Hard prohibitions
Writing Principles
- Focused: One page or section should cover one topic.
- Complete: Include edge cases, exceptions, and related details the agent needs.
- Scoped: Put facts at the level where they apply. Do not make a listing-specific rule global.
- Composable: Reference related Knowledge pages instead of duplicating the same fact in multiple places.
- Customer-safe: Do not include internal-only instructions unless the agent is allowed to use that information.
- Current: Update or remove stale source-backed content when policies change.
Good Knowledge Examples
Cancellation Policy
Good: “Customers can cancel up to 24 hours before the appointment for a full refund. If they cancel within 24 hours, the fee is non-refundable unless the team approves an exception.” Bad: “If the customer asks to cancel, check the calendar and notify ops.” This is process and tool guidance, so it belongs in a Skill or Tool description.Wi-Fi Details
Good: “The North Beach listing uses networkNorthBeachGuest and password oceanview2026. The router is in the hallway closet.”
Bad: “Be friendly when giving Wi-Fi details.” This belongs in Persona or a tone Skill.