- Call or message
- Collect the request
- Check approved details
- Route or book
- Hand off and record
Decide what the first response is for
I start with what the customer is trying to get done. Someone calls to ask about an appointment. Someone else sends a message about a quote. Another person has a problem that needs attention now. I want those requests to reach the right place, with enough information for someone to act. The voice and the wording come after that decision.
Write the handoff before choosing a voice. Who receives an unresolved request? What details do they get? How does the customer know someone is taking over? A pleasant automated conversation that leaves no usable record has only moved the waiting somewhere else.
Use the actual business channel
For calls, use a supported telephony integration that can receive the call, collect information, and route it. Twilio's voice documentation is an example of the available building blocks. The exact number, provider, and routing setup depend on your existing phone system.
For WhatsApp, plan around the Business Platform and its sender-registration and messaging requirements. A personal WhatsApp session controlled by a browser script is a different operational arrangement. Check the current provider rules before designing reminders or outbound messages, and do not assume that receiving an enquiry gives permission for unrelated marketing.
Keep business facts outside the model
Services, opening hours, coverage, prices, booking availability, and escalation contacts should come from records you control. The model may help understand a request or phrase a response. It should not invent an appointment slot or decide a discount because the conversation is going well.
Confirm consequential actions against the system that owns them. When a calendar is unavailable, collect a request for a person instead of announcing a booking. When a quote needs judgement, prepare the details and leave the commitment to the person responsible.
- Confirm what was requested before acting.
- Keep the original message with its summary.
- Make cancellation and human contact easy to find.
Test the interruptions too
Try background noise, an interrupted sentence, an unclear message, a caller changing their mind, and someone asking for a person. Check what happens when the provider times out or sends the same event again. A retry should not create another booking or another message.
Review the delivered record as well as the conversation. Did the correct person receive enough information to help? Was the customer told what happens next? Measure acknowledgement and a useful human response separately. They describe different parts of the service.
Follow a booking request through the handoff
Suppose someone messages a service business asking whether a visit is available. The message includes a preferred day and a description of the problem, but no location. A useful response asks for the missing location and explains what happens next. It does not claim that an appointment has been booked.
Once the required details arrive, the workflow checks the service area and the calendar it is permitted to read. If the request can be accommodated, it can prepare a proposed slot for confirmation. If availability is uncertain, the request goes to the named booking owner with the original message, collected details, and the reason the system stopped.
Now test a change of mind. The customer asks for another day after the draft booking was prepared. The old proposal should no longer be actionable without another check. Test the same event arriving again too. You want the current request attached to a single record, rather than separate conversations that each appear ready to confirm.
Finally, imagine the customer asks to speak with someone. The response should acknowledge the handoff and give an honest expectation. A generated assurance that somebody will call immediately is not useful unless the business can keep that promise. The person taking over should be able to read what happened without asking the customer to start again.
Keep a maintenance checklist
After launch, review changes to opening hours, service areas, escalation contacts, sender setup, and booking rules. Check a completed request all the way through, including the record the person receives. Treat a provider or prompt change as a reason to rerun the awkward examples.
Keep the route to a person available while investigating failures. Switching off a broken automation should leave customers with a working contact channel and the team with a clear list of requests that still need attention.
Sources you can check
The links support the platform details and technical distinctions. Recommendations and examples are editorial judgement.