Health checks
Confirm your setup is genuinely ready before real customers ring it, rather than finding out on a live call.
What readiness covers
| Area | What is confirmed |
|---|---|
| Phone number | A number is held, active and not pending compliance |
| Voice | A voice is selected and usable; random selection has enough active voices |
| AI models | A model is configured and reachable |
| Business information | Opening hours, services and the answers the AI needs |
| Billing | An active plan, and add-ons showing as active where relied upon |
| Workflows | Refunds, bookings and escalations configured with somewhere to go |
Before you go live
- Run the readiness checksThey tell you what is missing rather than failing silently later.
- Fix anything flaggedA warning here is a call that goes wrong later.
- Run a live test callReadiness checks configuration; only a real call tests the conversation.
- Ring your transfer numberThe most commonly broken part of a setup is the number nobody answers.
- Test out of hours tooSee after hours.
Expected result
Every check green and a real test call that behaved the way you would want a customer to experience.
Not just a launch task
Configuration drifts. Numbers get released, staff leave and transfer numbers stop being answered, seasonal hours change.
Re-run readiness after any change to numbers, hours, plan or transfer destinations - and before any period you expect to be busy.
Platform status versus your setup
Readiness checks your account. For the platform itself, see the status page - it is the first place a genuine incident appears.
A controlled production launch
Treat launch as a sequence with a named owner and a rollback point, not a single switch.
- Freeze configurationRecord the approved greeting, hours, routing, knowledge revision and escalation contacts. Avoid unrelated edits during the launch window.
- Run a test matrixCover open and closed hours, a normal enquiry, interruption, an unknown answer, a human request and every business-critical workflow.
- Release one entry pointStart with one number or channel. Keep the previous route available until the new route has passed real traffic checks.
- Observe and sampleReview the first completed conversations, not only totals. Check outcome, transcript, routing, latency and the work record left for your team.
- Expand or roll backExpand only when the acceptance checks pass. If they do not, restore the previous route, preserve the affected identifiers and investigate without customers waiting.