An agent returning from a long leave steps back into a queue that kept moving without them. Cases were reassigned, policies changed, and promises were made in their name. A handback note has to return ownership without losing any of that history. It should also give the agent a realistic first week instead of a full load on day one.
Confirm the return date and scope
Start with the date the agent formally returns and the hours they will work in the first week. A part-time return is common after a long absence, and the note should reflect it. Name the queues the agent is taking back and the queues that remain with another owner. A vague handback lets two people believe they own the same inbox.
State the temporary coverage arrangement that applied during the leave. Record who held each queue, what authority they had, and when that authority ends. If the coverage owner keeps a review role for a few weeks, say so. The returning agent should know where the second signature still applies.
List the queues and saved views
Name each queue, saved view, or filter the agent will use again. A renamed queue or a new routing rule can make an old favorite view point at the wrong work. Give the exact names that appear in the tool today. Ask the agent to confirm each view opens with the expected result.
Describe any queue that was split, merged, or retired during the leave. Explain where its work moved and who owns it now. Update the agent's bookmarks and saved replies to match. A stale view is a quiet source of missed cases.
Carry forward open promises
List every open promise the agent made before the leave. Include the customer, the case identifier, the promised date, and the current state. Mark which promises were kept by the coverage owner and which are still open. A promise without a state is a future complaint.
For each open promise, name the next action and its due date. If the customer was told a specific person would reply, note whether that is still possible. Reassign the promise if the original owner cannot meet the date. The customer should not learn about the leave from a missed deadline.
Show what changed while away
Summarize policy changes, price changes, and tool changes that affect daily replies. Keep the summary short and link to the full notice for each item. Mark the changes that alter what an agent is allowed to promise. A returning agent should not learn a new rule from a customer.
List the macros, templates, and knowledge articles that were updated or retired. Point out any saved reply that now gives an outdated answer. Ask the agent to review the changed items before taking live contacts. A short quiz or read-back can confirm the review happened.
Check access and permissions
Confirm that the agent's accounts, queue membership, and system roles are active before the first shift. Long leave can trigger an automatic access review that removes permissions. Test the tools the agent needs rather than assuming they still work. Record the date each access check passed.
Name the person who can restore a missing permission on the first day. A blocked agent who waits for a ticket loses hours of coverage. Give the returning agent a direct contact for access problems. The handback should remove that friction before it appears.
Set the first review date
Set a review meeting within the first week back. Use it to check workload, open promises, and any knowledge gap the agent noticed. Do not wait for a monthly one-to-one that may be weeks away. A short early review catches problems while they are still small.
Agree on a ramp schedule for the first two weeks. Start with a share of the queue and increase it as the agent confirms confidence. Record the target date for a full load and the person who can adjust it. A ramp that is written down is easier to defend than an informal hope.
Record the handback in the log
Write the handback as a dated entry that both the returning agent and the coverage owner can see. Include the queues transferred, the open promises, and the access checks. Store it where the team keeps its coverage records, not in a private message. A later dispute about ownership should be answered by the log.
Ask both parties to acknowledge the entry. An acknowledgement is not a formality when a promise is involved. It shows that the returning agent saw the open items and accepted them. The coverage owner should confirm that nothing was left undocumented.
Brief the team
Tell the wider team that the agent is back and which queues changed hands. Name the coverage owner's new role if it continues in a review capacity. Update the roster, the escalation list, and any shared status page. Customers should see one owner, not two.
Review the handback note in the next team meeting. Ask whether any promise was hard to reconstruct from the record. Use the answer to improve the next leave plan. The note is a working document, not a closing formality.
Review after two weeks
Check the agent's queue after two weeks for reopened cases and missed promises. Compare the first week's load with the agreed ramp. Ask the agent which parts of the handback were most useful. Their answer is better evidence than a manager's guess.
If a promise slipped, trace whether the note carried the right date and owner. Fix the template before the next leave rather than blaming the individual. Record the change and the date it takes effect. Each handback should be easier than the last.
