Practical operating guide
How to handle callers asking for someone who has left the company
By ByTomorrow · Published
The caller asks for a familiar employee. The phone agent still recognizes the name, but that person no longer handles calls for the business.
A working number is not proof that the right person will answer. An old extension, mailbox or personal number can keep a stale route alive long after a staffing change.
Diagnosis
Identify the failure before changing the flow
The name appears in several places
A destination can live in the greeting, routing table, reference documents and fallback instructions. Changing one field leaves the other paths capable of using the old contact.
The replacement is not assigned
Removing a name does not establish who now handles the work. Match the former role to a current owner and backup before offering a substitute.
The route can come from a variable
Retell documents static and dynamic transfer destinations. During a change review, inspect both the configured destination and any value supplied at call time. A corrected script alone does not prove the actual number changed.
Practical worksheet
A routing maintenance checklist and substitute-contact script
Retirement inventory
Copy these fields: former public name or role ___; affected request types ___; routing entries ___; greetings ___; reference documents ___; mailboxes ___; downstream task owners ___; reviewing owner ___. Inspect only systems within the authorized business scope.
Replacement decision
For each request type choose current responsible role ___; approved destination ___; effective time and time zone ___; backup ___; unavailable response ___. Some duties may move to different people. Do not redirect every request to the same person by default.
Substitute-contact script
Suggested wording: "That person is not available through this line. I can help route your business request. What do you need help with?" Use only owner-approved public information. Do not speculate about employment circumstances or disclose a personal contact number.
Caller insists on the former employee
Suggested wording: "I do not have an approved contact route for them. I can try the team that now handles this request." Use the offer only when that route exists. Preserve the caller's choice if they decline.
Retirement evidence
Record the old routes disabled or reassigned, the new owner's acknowledgment and the test-call result. Check a direct name request, a role request and an old fallback path. Keep a failed replacement visible instead of silently restoring an inappropriate destination.
Use the worksheet
Put it into practice
Approve replacement ownership
Have the business owner resolve each affected duty and the public wording before editing the call path.
Apply the change as one scoped update
Update the inventoried references and route settings. Check queued follow-up work separately; an old task does not move just because a phone destination changes.
Test old and new entry points
Use synthetic calls and approved test destinations. Confirm no path exposes a personal number or promises access to the former employee.
Questions
Straight answers.
Only repeat an explicitly approved public statement when relevant. The routing task does not need private employment details.
Use the owner-approved unresolved-request queue. Do not invent a replacement or imply the former employee remains responsible.
Sources and further reading
- Retell transfer-call documentation
Supports static and dynamic transfer destinations; staff retirement inventory and wording are editorial operating recommendations.
Checked .
Bring a concrete example
Use a synthetic call and your current business rules to discuss this workflow. Confirm the intended behavior before enabling it for customers.
Discuss your workflow