Markdown

Voice Agent Launch Checklist

Use this before routing real customer calls to a voice agent.

Flow Definition

Disclosure

Tool Access

ToolAccessAllowed actionConfirmation requiredLog fields
CalendarRead/writePropose/create appointmentCaller confirms exact date/time; downstream calendar is reconciledPseudonymous call ref, slot ref, result code
CRMRead/writePropose/add minimized structured noteConfirm source facts and policy gate before writePseudonymous contact ref, action, result code

Escalation Triggers

Immediate danger comes before the business queue: stop the business flow and direct the caller to their local emergency service, such as 112 in Estonia. Do not tell them to wait for a callback. Test the accessible emergency wording for every supported locale, and never claim an emergency transfer unless it actually occurred.

Test Scenarios

Launch Decision

Unknown booking result acceptance

Synthetic case: caller confirms an exact slot and timezone; operation B17 times out. Expected: preserve B17, reconcile before retry, disclose the unknown result, and pass it to the human route when requested. Verify the calendar independently. If transfer fails, do not claim a completed transfer or callback; use the approved fallback and verify its outcome. Booking and notification are separate effects.