Download the editable call script
Decide when the script takes over
Write down the hours someone can answer live, the hours someone can take a transfer, and the hours requests will wait for the next shift. These can be three different schedules. Put holidays and the business time zone on the same sheet as the on-call contacts.
On a busy daytime call, the right opening might be “Our coordinators are helping other callers.” At night, that greeting suggests someone is still at a desk. Use a separate opening for each route. Your business phone routing plan should name the person responsible for switching the rota.
A script your dispatcher can edit
Replace the text in square brackets with information your team has approved. This example collects a request before anyone commits to a visit.
Opening
“Thanks for calling [business]. I’m the automated after-hours assistant. I can take a service request or try the on-call team for [covered situations]. What are you calling about?”
Intake
“What’s the service address, including the postcode or ZIP code? What number should the team use if we get disconnected? In your own words, what needs attention?”
Available on-call route
“That fits our on-call instructions. May I put you through with those details? If the team can’t pick up, I’ll tell you what happens next.”
Callback route
“I’ve recorded a request for [team] to review [approved callback window]. No visit has been scheduled. Let me read back the address and number.”
Give dispatch a handoff it can act on
A note that says “urgent, call back” forces dispatch to start again. A useful note distinguishes the caller’s description from the agent’s action. For example: “Caller reports water around the heater. In service area. Requested a visit tonight. Transfer attempted at 20:14, no answer. Callback requested from duty coordinator.” Keep any access details your business treats as sensitive in the approved dispatch system.
Define who owns the next step after an unanswered transfer. If the backup contact is also unavailable, the script must use the fallback your team can actually deliver. A notification being sent is different from a technician accepting a job.
Test four calls before forwarding the number
- Covered address, on-call person available. Confirm the recipient hears the reason for the transfer and can speak to the caller.
- Covered address, nobody answers. Expect one request in the queue, the correct callback wording and no promised arrival time.
- Address outside the service area. The assistant should apply the coverage rule before offering a visit.
- Caller describes immediate danger. Use the business’s approved emergency wording and escalation policy. Keep repair diagnosis out of the intake script.
Run the tests from a separate number. Check the actual dispatch queue and phone at the other end. Ask the dispatcher whether they could make the next decision from the note alone.
Review one week of callbacks
Count eligible after-hours calls, requests with a usable number, handoffs accepted by dispatch, and appointments the team actually confirmed. Keep wrong numbers and repeat calls about the same job separate. If intake looks strong but few callbacks happen, check queue ownership and staffing before rewriting the greeting.
For a team deciding who should answer the more complex calls, use the AI and human answering comparison. To scope an implementation, bring the completed script and the hours your service team can cover.