Launch governance
Ship voice agents with enterprise controls.
Use this checklist before moving a tenant, phone number, or agent version to production traffic.
Launch checklist
Access and data boundaries
Separate admin keys from tenant bearer tokens, verify Twilio signatures, and review PII handling.
Agent behavior
Approve system prompts, model, voice, allowed tools, phone routes, and fallback behavior.
Monitoring and response
Track readiness, live sessions, call completion, transfer rate, error rate, and provider failures.
Launch ownership
Identify the business owner, escalation owner, engineering owner, rollout limits, and stop conditions.
Production gates
| Gate | Required evidence | Owner |
|---|---|---|
| Security review | Credential scopes, Twilio signature verification, PII handling, and stream-token rotation are reviewed. | Security and engineering |
| Agent behavior | Approved system prompt, model, voice, allowed tools, escalation language, and refusal policy are recorded. | Business and CX |
| Operational readiness | Dashboards, alerts, callback queues, runbooks, and support ownership are live. | Operations |
| Rollout approval | Traffic limits, rollback plan, success metrics, and stop conditions are agreed before launch. | Launch owner |
Minimum telemetry
/health/readyKubernetes and external readiness gate for production traffic.
/api/v1/call-logsCall status, direction, duration, escalation state, and outcome tracking.
/api/v1/voice-sessionsTranscripts, function calls, summaries, and conversation state.
/api/v1/admin/rollout-governanceAgent quality, evaluation thresholds, and rollout policy checks.
Final release gate
Production traffic should not start until security, runtime, operations, and business approval are complete for the tenant and agent version being launched.