Choose a 24/7 answering service by testing what happens overnight, during exceptions and when the normal workflow fails. Coverage hours alone do not establish whether a customer receives a useful next step.
Separate answering hours from dispatch hours
A service can answer at midnight while your team starts work at eight. Write both times into your operating plan. The receptionist should know when it can offer routine availability, when to take a callback request and when a designated person is actually on duty. “Available around the clock” should never become an accidental promise that a technician is travelling now.
Prepare three example enquiries: a routine quote, an existing customer checking tomorrow’s visit and an urgent-sounding request. Ask the provider to demonstrate the different outcomes without relying on a salesperson’s explanation.
Inspect the overnight record
When you open the job record the next morning, can you act without replaying the whole conversation? Require the customer’s confirmed callback number, service address, requested work, agreed next step and any unresolved question. Keep claimed urgency separate from a confirmed attendance commitment.
Use this handover test: give a colleague only the resulting record and ask them to explain what was promised. If they have to guess, revise the intake fields. Check an address correction and a caller who is unsure of their postcode as well as an easy call.
Ask who receives exceptions
An escalation rule needs a destination, an owner and a response when that destination is unavailable. Decide which calls warrant interruption and which can wait. A request for a person, a complaint and a suspected immediate danger should not all use the same vague “we will pass that on” response.
Ask to see the fallback arrangement. Twilio’s failover documentation illustrates that backup call paths require configuration. Ask your chosen service what it has actually configured, who monitors failures and how you will learn that coverage has been interrupted.
Check the commercial boundaries
Ask for a written explanation of usage units, included tasks, holiday coverage, transfers, integrations and changes to your instructions. A plan that takes messages may serve you perfectly; it is a poor comparison with a booking plan if your buying goal is confirmed appointments. Identify any human escalation charges or separate implementation work.
Review the bill using your own call pattern: repeated callers, long conversations and quiet overnight periods. Keep this comparison separate from the coverage test. Our pricing worksheet helps organise the financial side.
Run a controlled evening rehearsal
Make agreed test calls outside your normal office hours before changing the main number’s routing. Include an unavailable slot, a request outside the service area and a caller asking for an immediate visit. Check the calendar, notification and final record after each call. A pass means the stated rule was followed, not that the voice sounded friendly.
Keep the test results and unresolved issues in one acceptance sheet. KEDO’s HVAC workflow offers a relevant recorded example; verify the exact hours, exceptions and integrations your business needs during setup.
Sources and editorial notes
Checklists, example wording and decision rules are KEDO Labs editorial recommendations, not measured results or guarantees of a provider’s features. Sources checked October 8, 2026.
See the workflow
Hear the call. See the booking.
Watch KEDO handle a service enquiry, then review the current setup fee and monthly price before you pay.
Reading in Google?
Make KEDO a preferred source
Add KEDO Labs as a preferred source in Google and our guides are more likely to appear with a 'preferred' badge in Top Stories, and can carry a badge in AI Mode and AI Overviews.