Philippines staffing blog ·

Plan a help desk handover when an agent leaves the program

How to move a departing agent's caseload, knowledge, and access without dropping tickets or surprising the client.

Plan a help desk handover when an agent leaves the program help desk operations illustration

Direct answer

Operational guidance

Why departures need a plan

An agent leaving the program takes more than a seat out of the roster. They carry context about recurring customers, unfinished approvals, and shortcuts that never reached the knowledge base. If the desk waits until the last week, the handover becomes a rushed scan of an inbox. A short written plan protects the customer experience and the team that remains.

Departures are predictable enough to plan for even when the exact date is not known. Build a checklist that starts when a resignation is confirmed and ends with an access review after the last shift. The checklist should name who owns each step and where the evidence is stored. A routine plan removes the improvisation that causes missed tickets.

Map the departing caseload

List every open ticket assigned to the agent, including items in a waiting state and items that belong to another owner but depend on their input. Sort the list by customer promise date and by risk, not by ticket age alone. Add the recurring customers the agent handles informally, because those relationships often sit outside the queue. The map should show what would break if the agent disappeared tomorrow.

Include the work that does not look like a ticket, such as saved replies in draft, client requests sent by chat, and side agreements about how a report is produced. Ask the agent to walk a supervisor through their week and note every recurring task. The exercise usually reveals two or three duties that never appeared in a job description. Those duties need an owner before the last day.

Capture knowledge before the last day

Ask the departing agent to write short notes for the cases that took them the longest to learn. A note should explain the decision, the person who approved it, and the trap that a new agent would fall into. Keep the note close to the ticket or article it supports rather than in a personal document. Knowledge that lives only in a farewell email will be lost within a month.

Record a walkthrough for the two or three workflows that are hardest to describe in writing. Screen recordings are useful when a tool has several hidden steps, but they need a written summary and a date. Review the recording with the receiving agent and correct anything that sounds out of date. The goal is a durable instruction, not a tribute to the person leaving.

Transfer open tickets

Reassign tickets in batches by work type so the receiving agents can build context instead of switching between unrelated cases. Send a handover note with each batch that names the customer promise, the next action, and any sensitive history. Do not reassign a ticket that is waiting on a client decision without telling the client who now owns it. A silent reassignment makes the customer repeat themselves.

Set a short overlap period when the departing agent can answer questions from the new owner. Use that time for the cases with the highest risk, not for a general tour of the queue. Record the answers in the ticket so the next reader benefits. The overlap should end with a named owner for every item on the map.

Remove access on time

Plan the access removal before the last shift so it happens on a known date and time. List every tool, client portal, shared mailbox, and distribution list the agent can reach, then confirm each one with the client owner. Removal should include sessions, saved passwords in shared browsers, and forwarding rules. A forgotten forwarding rule can keep sending customer data after the account closes.

Keep a record of what was removed and who confirmed it. If a client delays a removal, record the date of the request and the escalation. The desk should not describe an account as closed while a client-controlled access path remains open. Access evidence belongs with the handover record, not only in an email thread.

Brief the client

Tell the client about the change before the customer notices a new name on replies. Name the replacement owner, the overlap dates, and the channel for questions. Keep the message factual and short, and avoid promising that nothing will change. A client who knows about the transition is less likely to read a routine handover as a service problem.

Ask the client whether any of their internal contacts need to update a distribution list or an approval route. A departing agent may be the named approver in a client workflow that the desk cannot see. Confirm the change in writing and keep the reply with the handover record. The client should leave the conversation knowing exactly who acts next.

Support the receiving agents

Give the receiving agents time to read the handover notes before the tickets arrive. A transfer that lands at the start of a busy shift will be skimmed rather than understood. Pair each new owner with a supervisor for the first week and review the riskiest cases together. Support during the transfer is cheaper than repairing a missed promise later.

Watch the receiving agents for overload, because a departing caseload often lands on the most experienced people. Rebalance the queue if one agent receives several complex cases at once. Ask what is missing from the notes and fix the template for the next departure. The handover is working when the new owners can explain their cases without calling the person who left.

Review after thirty days

Thirty days after the last shift, check the transferred tickets for missed promises, reopened cases, and notes that nobody could follow. Ask the client whether the transition created any confusion and record the answer. Review the access list one more time to confirm that every removal held. The follow-up turns a one-time handover into a repeatable process.

Update the checklist with the gaps the review exposed, especially any task that had no owner until someone noticed. Keep the completed checklist as an example for the next departure. Write the change into the plan while the details are still fresh. A good handover is not a heroic effort by one supervisor; it is a routine that the desk can run while the queue stays open.

Authoritative sources

Related planning pages