Write down the jobs and areas you serve
List accepted work, excluded work and the towns or ZIP codes you cover. Decide how to handle an out-of-area caller without promising service you cannot provide.
Define urgent routing in plain language
Have your team approve the words that trigger the on-call path. The assistant should capture the issue and route the request, not diagnose hazards or promise an arrival time.
Name a primary and a backup
Use approved destinations, reasonable ring times and an explicit no-answer action. Test the backup when the primary phone is busy, switched off and forwarded to voicemail.
Keep booking separate from dispatch
Routine scheduling needs a tested calendar and agreed service durations. An urgent job request does not mean a technician has been dispatched. Make the status clear in the caller’s response and the team summary.
Review missed handoffs
During the pilot, check whether the right person received each urgent request. Update the rota when staff change, and retest after every routing change.