Writing good instructions
Keep instructions short and concrete; long prompts add latency to every reply. Say who the assistant is, what it must never do, and what to do when unsure ("offer to take a message"). Use the knowledge base for facts (prices, hours) instead of the instructions.
Still stuck?
Email [email protected] or send us a message. Team and Scale plans get priority support.