Get the details to someone who can answer.
A dealer with a PO needs someone who can check the order. A driver needs the yard. An invoice question belongs with someone who can see the account.
Whoever answers first doesn’t need those answers. They need enough to reach the right desk: the company, the reference, the reason, and a callback number.
Map one common call.
- Reason
- What is the caller trying to sort out?
- Details
- Which reference or location will help the next person?
- Who to try first
- Who can check and give the answer?
- Backup
- Who should be tried next?
- Fallback
- Who calls back if nobody answers?
Repeat that exercise for the common call types. Keep the names and department vocabulary familiar to both the caller and your staff.
Tell staff who’s calling before they take the transfer.
When the person being rung hears who is calling and why before they take the transfer, they can decide whether to stop what they are doing. A call they pass on then follows a path you planned.
Keep the list short. A short list of who’s next is easier to test and keep current than a long tour of extensions.
An alert arriving is not proof the work got done.
Plan for when nobody can answer.
Keep the call details, who’s calling back, the callback number and how it ended together. An alert arriving is not proof the work got done.
Run test calls from both sides: caller and the person being rung. Try an accepted transfer, a decline, no answer, an unfamiliar company name, and a reference that needs repeating. Then check the message your team sees afterward.
See how it works for suppliers