Prepare a single approved set of business instructions, confirm the booking integration and routing plan, then rehearse normal calls and exceptions before forwarding customer calls.
Gather the operating facts
Start with a one-page business brief: trading name, pronunciation, office hours, service area, accepted job types, contact routes and approved answers to common questions. Add holiday exceptions and work you do not accept. Keep firm prices separate from estimates and from questions that require the owner’s approval.
Appoint one person to approve this brief. If two team members give conflicting instructions, resolve them before launch. Date the document and keep a change log. This is the operating specification, not marketing copy, so a precise boundary is more useful than an impressive promise.
Define required intake fields
Specify the minimum details needed for each call type. A new job might require name, callback number, service address and a plain-language description. An existing appointment query may need a booking reference instead. A supplier calling for accounts should not be forced through the new-job script.
For every field, decide what happens if the customer does not know it. Test corrected spellings and numbers. Require the final record to distinguish confirmed details from uncertain ones. Use fictional examples during configuration and avoid importing customer information that is unnecessary for the agreed workflow.
Prepare the calendar and ownership
Confirm which calendar receives bookings and which calendars affect availability. Agree appointment duration, permitted start times and the circumstances requiring manual review. A technician’s lunch break or a travel block must not be mistaken for an available service slot.
Google Calendar’s schedule settings include availability checks and buffers. Check what your actual integration supports rather than assuming settings transfer between systems. Give the connection an accountable owner, document how access is revoked and verify that booking details reach the people who need them.
Write the routing and rollback plan
Record the existing number, intended forwarding behaviour and who can reverse it. Confirm the instructions with your carrier or phone-system provider. Decide whether the agent answers all calls, only unanswered calls or an agreed after-hours window. Those choices can affect how you test and how your team recognises a failure.
Document a backup destination and an honest customer message for service interruptions. Twilio describes configurable failover paths; your supplier should explain the arrangement it uses. Keep rollback instructions accessible to someone other than the original installer.
Sign off a small launch checklist
- Normal enquiry produces the correct record and authorised next step.
- Unavailable slot does not result in a false booking.
- Address correction survives into the final notification.
- Request for a person reaches the agreed destination.
- Unsupported question is recorded without an invented answer.
Have the business owner approve the evidence before routing real calls. Review the first live records promptly and maintain a list of changes. Our call-handling playbook helps decide when automation should answer, while KEDO’s service page describes the published workflow to discuss during onboarding.
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.