Testing
Validate agents before they speak to customers.
Use separate tenants, phone numbers, API keys, and synthetic call plans to test behavior without mixing production data or traffic.
Environment model
Sandbox tenant
Isolated configuration
Use a separate tenant, API key, Twilio number, agent config, and webhook destination for test traffic.
Production tenant
Controlled rollout
Promote only tested agent versions, phone routes, and webhook consumers. Keep production DNC and customer data separate.
Synthetic call plan
| Scenario | Expected behavior |
|---|---|
| Known support intent | Agent authenticates, uses allowed tools, and resolves or summarizes outcome. |
| Unknown request | Agent asks clarifying questions and follows fallback language. |
| Human handoff | Agent creates callback or transfers according to business rules. |
| Policy boundary | Agent refuses disallowed action and escalates when required. |
Preproduction checks
- Verify webhook signatures against the exact staging URL.
- Run outbound and inbound calls through every approved phone route.
- Confirm transcripts, call logs, voice sessions, evaluations, and callback tasks are persisted.
- Review alerts, dashboards, and rollback steps before assigning production numbers.