Prompts
- Lead with role → constraints → output format
- Ban inventing prices, legal advice, or competitor claims
- Force language mirroring (“reply in the user’s language”)
- Include a concrete JSON example when you need rich responses
- Inject contact fields carefully; handle empties
Knowledge and files
- Prefer focused sources over one mega-document
- Remove low-value crawled pages after indexing
- Re-train after major content changes
- Put immutable rules in the prompt, bulky facts in knowledge/files
Tools (functions & MCP)
- Name tools clearly (
get_order_status) - Describe when to call them, not only what they return
- Validate all tool arguments server-side
- Prefer idempotent writes
- Scope MCP credentials to least privilege
Routing and fallbacks
- Keywords for hard overrides; Agent for natural language — priority
- Always define human handover
- Pair Agents with Flows when steps must be exact
Cost and quality
Release checklist
- Provider connected and model selected
- Prompt constraints reviewed by a human
- Knowledge/files answer the top 20 real questions
- Tools tested for success and failure
- Handover + fallback Flow verified
- Channel-specific rich messages tested on device
Next
Limits
Token, knowledge, and platform caps.
Prompt engineering
Deeper prompt patterns and examples.