On this page
A voice-agent script needs to explain the task, the facts it may use, and what the system can actually do. It should not promise a booking, transfer, message, or emergency response because those words sound helpful. Start from the implemented workflow and write the conversation around its real states.
The pattern below is an original drafting worksheet for an administrative callback-request pilot. It is not a ready-to-launch script or a guarantee of conversion performance.
Write the task contract first
Define the allowed request, minimum fields, receiving system, and success condition. For example: collect a business caller's preferred callback topic and contact details, then deliver a request to an approved staff queue. Exclude account changes, payment collection, and other tasks the pilot cannot perform.
Use a small approved fact sheet with a source and owner for each answer. Include opening hours, service boundaries, and where current pricing is confirmed. Mark unknown information explicitly. The model should not turn an example warranty, fee, or response time into a real business promise.
Use short turns without arbitrary timing rules
A proposed opening is: “You’ve reached [business]. I’m its automated assistant. What would you like help with?” Replace the placeholder with an approved identity and review any required disclosures for the actual channel and jurisdiction.
Ask one clear question, then allow a response. Read back ambiguous identifiers and preserve caller corrections. Test pacing with intended users and the actual voice; a universal seconds-per-sentence rule cannot establish that every message is understandable.
| Conversation state | Instruction to draft |
|---|---|
| Request unclear | Ask which task the caller wants before collecting details |
| Required detail missing | Ask for that detail, explaining its purpose if useful |
| Caller corrects a detail | Replace the previous value and confirm the correction |
| Delivery pending | Describe the pending action without claiming completion |
| Delivery confirmed | State the specific result the receiving system confirmed |
| Delivery failed | Explain the limitation and offer the approved alternative |
Separate language from enforcement
An instruction such as “only make authorized changes” is not authorization code. The integration must validate input, account access, permitted fields, and action eligibility. It must also handle timeouts and duplicate events.
QuickVoice's live MCP handler restricts tools marked for writes, side effects, or confirmation. A script must match an allowed implementation. Do not add an instruction to bypass that restriction or describe a calendar write that is not available in the selected path.
Make alternatives truthful
If a caller requests a person, provide the configured option promptly. A live transfer requires tested telephony routing; a callback request requires a delivered staff task. Neither establishes that someone will answer within an invented interval.
For clinical, safety, legal, or financial matters outside scope, use the responsible organization's approved routing policy. Do not improvise urgent advice, tell a caller to wait on a generic queue for emergency help, or promise dispatch that has not happened.
Test the script as a versioned change
Use synthetic conversations for the normal request, a correction, refusal, silence, unknown question, unavailable receiver, repeated event, and human request. Inspect both the words and the final system record. A polite conversation with a missing request is a failure of the workflow.
Record the instruction version and the approved fact-sheet version. When an answer changes, re-run the affected cases and a few adjacent tasks to catch unintended effects. Assign an owner to failed cases rather than assuming the agent will learn the correction by itself.
QuickVoice's repository supplies infrastructure to inspect and extend, with provider configuration required. Use the implementation guide to establish the workflow before refining its wording.
Rahul Agarwal
More implementation guides