Start with a routing table
Write one row for each meaningful call reason: existing customer, new enquiry, supplier, complaint and named staff request. Give each row a primary role, a backup role, the hours those people accept calls and the permitted fallback. Use roles in the policy and maintain the actual numbers separately. That lets a staffing change update one controlled list. Avoid routing every difficult question to the owner. Ask the people receiving calls which interruptions they can reasonably accept, then agree those boundaries before testing begins.
Separate a request from permission to transfer
A caller asking for a person does not tell the receptionist whether that person is working, whether they accept direct transfers, or whether the caller has reached the correct department. Ask only the missing question needed to route the call. For example: "Is this about an existing booking or a new enquiry?" A person who declines to explain should still have a clear message option. Do not force an extended qualification script on someone who has already supplied enough information or explicitly wants a human.
Define what the receiving person hears
For a warm transfer, propose a brief private introduction containing the caller name, reason and any action already attempted. Confirm whether the receiving person must actively accept before the caller is connected. Voicemail answering is not the same as a staff member accepting. Test that distinction on the actual destination handset. If the platform cannot reliably distinguish the two, use a documented alternative rather than describing the transfer as guaranteed. Never read unnecessary account or personal details into a generic voicemail greeting.
Give every failed attempt an ending
Specify a maximum wait and a maximum number of destinations for your business. Choose these with staff and validate them by listening to test calls. The caller should hear a plain explanation before waiting and a clear result afterwards. A useful fallback is: "I could not reach the team. I can take your details for a callback." The receptionist must not say that somebody will call within a specific time unless that commitment is backed by a staffed process. Preserve the original reason so the caller does not have to start again.
Test the whole telephone path
Run test calls with the destination available, already on a call, powered off and configured to send unknown callers to voicemail. Test a staff member rejecting the call and a caller hanging up during the introduction. Include the destination number that forwards back to the main line: that can create a routing loop. Record the actual path, the words heard by both parties and the message produced. A provider dashboard showing a transfer event is useful evidence, but it does not prove that a conversation with a staff member occurred.
Keep the policy usable after launch
Assign one person to maintain destination numbers and cover arrangements. Review failed transfers alongside staffing schedules rather than treating every unanswered call as a technology fault. Track attempted, accepted, unanswered and failed transfers separately. If staff repeatedly decline a category, change the routing policy or staffing arrangement instead of adding more retries. Keep a short change record with the date, owner and test performed. Re-test after changing a phone carrier, handset setting, voicemail service or forwarding rule, because any of these can alter the caller experience without changing the receptionist script.