Skip to content
Lines open
Map my coverage

Call Routing

Routing a call when the primary contact is on leave

A coverage routine for routing calls when the usual contact is away, with a named backup, clear authority and a current handoff note.

A desk phone and a written coverage note in an office
Table of contents

Name the backup before the leave

A coverage plan should name a primary backup and a second backup for each contact. The backup should know the caller types, the open issues and the decisions they can make. A name in a directory is not a plan. The team should confirm that the backup accepts the role before the leave begins.

Record the dates of the leave and the exact handoff time. A backup who starts on Monday morning needs the note on Friday, not at noon on Monday. If the leave is sudden, use the second backup and update the plan as soon as possible. The goal is a route that works on the first call.

Set the authority boundary

Decide which decisions the backup can make without the primary contact. Routine scheduling, status updates and document requests usually belong to the backup. A price change, a contract term or a sensitive client decision may need the primary contact or a supervisor. Write the boundary in the coverage note.

Tell the callers what the backup can do. A caller who hears that the backup can handle the request is more likely to accept the route. A caller who hears that only the absent person can help may wait or escalate. The authority should be clear enough to avoid a second handoff.

Update the greeting and the directory

Change the phone greeting and the team directory before the leave starts. The greeting should name the backup and the expected response time. The directory should show the backup as the primary contact for the period. A caller who follows an outdated directory will reach a voicemail that nobody owns.

Check the internal directory and the website contact page as well as the phone system. A change in one place but not the other creates confusion. Ask a colleague outside the team to test the route. The test should confirm the greeting, the transfer and the voicemail owner.

Brief the backup on open work

Give the backup a short list of the open calls, the promises and the decisions that may arise. Include the caller name, the issue, the next date and the last thing the caller was told. Do not send a long archive. The backup needs the live items and a link to the full record.

Mark the items that cannot be delegated and the person who will cover them. If a decision must wait for the primary contact, say who will tell the caller and when. A clear note prevents the backup from guessing at a commitment. The caller should not hear a different story from the coverage team.

Route new calls by the issue

Use the issue type and the authority boundary to route each new call. A routine request goes to the backup, while a sensitive or high-value issue goes to the supervisor. Do not route every call to the backup just because the primary contact is away. The queue should still use the normal skills and escalation rules.

If the backup is unavailable, the second backup should take the call. The caller should not be told to try again later without a named alternative. A short script can explain the coverage without sharing the reason for the leave. The route should feel planned, not improvised.

Keep the primary contact out of the queue

Do not forward the main queue to the primary contact's voicemail during the leave. That creates a hidden backlog that the team cannot see. If the person will check messages occasionally, define what qualifies as urgent and who else can act. The default should be a covered route, not a mailbox.

Set an out-of-office reply that names the backup and the response time. Do not promise that the primary contact will reply during the leave. The reply should be consistent with the phone greeting. A caller who receives two different messages will question whether the coverage is real.

Hand back the work

Before the primary contact returns, prepare a return note with the calls handled, the promises made and the items still open. Include the decisions the backup made and the ones that were deferred. The returning owner should be able to resume without calling every caller to ask what happened. A short return note is easier to use than a long thread.

Schedule a short conversation on the first day back and review the exceptions. Ask the backup what was difficult and what the coverage note missed. Update the template with the answer. The handback is part of the coverage, not an afterthought.

Review the coverage

After the leave, check whether the greeting, the directory and the routing worked. Look for calls that were transferred twice, promises that were missed and callers who had to repeat their story. Fix the step that failed and update the plan. The next leave should start with a better route.

Do not measure the coverage only by whether the queue stayed open. A queue can stay open while the caller experience collapses. Read a sample of the calls and the notes. The review should protect the caller and the team, and it should make the next handoff calmer.

Update the plan after the return

Ask the backup and the returning contact what the coverage plan missed. A directory field, a greeting or a decision right may need to change. Update the template while the experience is fresh. The next absence should not repeat the same gap.

Record the dates of the leave and the name of the coverage owner in the team calendar. Remove the temporary greeting and directory changes on the return date. A stale greeting tells callers that the coverage is still active when it is not. The cleanup is part of the handback.

Map the first queue

GIVE MISSED CALLS A WAY BACK IN.

Share your call types, hours, tools, and escalation rules. We will turn them into a practical coverage plan with a clear first week.

Book a free consultation ↗See the call lanes