A useful structure
Keep frequently changing facts in
[[Section name]] blocks. Type @ to insert an attached tool’s exact name. Keep long reference documents in a knowledge base and state when to search it. Instructions support up to 28,000 characters.
Example: showroom appointments
The following fictional example assumes you have created the two named tools. Replace the business facts and insert your actual tool names.Test in stages
- Publish and run web tests with populated and missing variables. Inspect tool arguments and results in the transcript.
- Call your own phone to check recognition, pauses, interruptions, dates, and numbers under realistic audio conditions.
- Start with a small set of real calls, review analysis and tags, and expand after the outcomes are acceptable.
Frequently asked questions
Should I write in English or Spanish?
Should I write in English or Spanish?
Either can be used. Configure spoken languages in General and test the instructions in the intended language.
Can a prompt guarantee no invented answers?
Can a prompt guarantee no invented answers?
No. Give explicit sources and fallback behavior, inspect tool outcomes, and evaluate representative calls.
Why is the old flow still running?
Why is the old flow still running?
Tests use the published version. Save and publish the new prompt.
