Production checklist

Check the journey a real caller will experience. Simulated calls, browser previews, and saved configuration are useful evidence for their own boundaries; they do not establish that a carrier route or external provider action works.

Company and service

• Confirm the intended company, eligible paid service, accepted offer, and usage funding.
• Inspect the actual BYO phone connection or acquisition result rather than a saved selection.
• Make subscription, AI-minute, capacity, and carrier costs clear to the account owner.
• Keep each company’s records, numbers, credentials, and allowance separate.

Published agent

• Review business facts, hours, pronunciation, escalation instructions, and knowledge boundaries.
• Enable the required actions and complete their current prerequisites.
• Wait for required evaluations of the exact draft. A queued check is not a pass.
• Publish the tested configuration, and review it again after changing destinations or integration policies.

See agents and templates and action readiness for the corresponding API contracts.

Incoming calls

Call the actual configured number. Verify the greeting, a business question, a message, a requested transfer, and hangup. Call back immediately. Test no-answer, closed-hours, and AI-capacity fallback. Inspect the resulting call, request, and provider receipts.

A caller requesting a person should get the configured supported transfer or a clear alternative. The agent should not say it opened a ticket or completed a handoff without the corresponding saved result.

Outbound calls

Check the outbound plan, eligible list and calling policy, suppression handling, calling window, caller ID, and working verified BYO telephony connection. An incoming number working correctly does not establish outbound readiness.

Follow campaigns and scrub, including the actual launch operation’s idempotency requirements. A purchased list or provider connection alone does not establish permission to call.

Result delivery

Confirm that the receiver verifies signatures, rejects invalid signatures, durably accepts events, and deduplicates repeated event IDs. A signed test sample must not create real customer work.

Verify a supported real workflow from its saved Vocapable receipt to the correct external record. Inspect delivery failures and recovery behavior. See webhooks and receiving results.

Team operations

Give the right people company access. Confirm they can find missed calls, messages, and callbacks from their supported phone or browser experience. Check availability, permissions, and the selected company caller ID on the actual device. See mobile and team access.

For investigation, retain company, call, request, provider, and event references without logging API keys or unrelated sensitive data. Use the error guide and service status.