Support Shift Handover Checklist
A shift handover checklist for support teams: open escalations, promised callbacks, queue status and known issues, handed over in writing every shift.
- Typical schedule per shift
- The checklist 4 sections, 14 items
- Variables
{{shift}}{{outgoing_agent}}{{incoming_agent}}
Use this checklist at every shift change in a support team: from the morning to the evening shift, from one time zone to the next, or to the weekend on-call person. It suits teams that cover long hours or several time zones and keeps customer promises from falling through the gap between two people.
Who owns it
The outgoing agent owns the run and fills it in before their shift ends. The incoming agent confirms the last section, which makes the handover a two-way check instead of a message nobody reads. The support lead reviews handovers occasionally to spot recurring problems.
Common pitfalls
- Verbal handovers only. A quick chat at the desk or on a call is useful, but nothing survives it. Write it down, even briefly.
- Promises hidden in ticket threads. "I'll call you back at 9" in a reply is invisible to the next shift. List every promised callback and follow-up with its time.
- Handing over the whole queue. The incoming agent can read the queue. The handover is for what is not obvious from it: escalations, angry customers, odd patterns.
- Known issues not shared. If an outage or bug is affecting customers, the next shift needs the status, the workaround and the macro, not just "something with logins".
- Leaving before the handover is read. The outgoing agent should not sign off until the incoming agent has confirmed it.
Schedule the run to start shortly before each shift change. The history then shows what was handed over, which helps when a customer says they were promised something.
The checklist: Support handover {{shift}}: {{outgoing_agent}} to {{incoming_agent}}
Escalations and promises
-
Open escalations listed with owner, status and next step
-
Promised callbacks and follow-ups listed with the time and the ticket link
-
Customers who are upset or at risk flagged, with a one-line context each
-
Tickets waiting on engineering or another team listed with who to chase optional
Queue status
-
Queue size and the oldest unanswered ticket noted
-
Tickets close to missing their response target flagged
-
Unusual spikes or repeated questions noted, with example tickets
Known issues
-
Active incidents or bugs affecting customers summarised with status page link optional
-
Current workaround and the macro to use for each known issue shared
-
System or tool problems noted: helpdesk, phone, chat widget optional
Handover
-
Handover note posted in the team channel or the run, before the shift ends
-
{{incoming_agent}}read the note and asked any questions -
{{incoming_agent}}confirmed they own the escalations and promises from now on -
{{outgoing_agent}}set their status to offline and reassigned their open chats
Checklist as Markdown
Frequently asked questions
What should be included in a support shift handover?
Open escalations, promised callbacks with times, at-risk customers, the queue status, known issues with their workarounds and any tool problems. Skip what the next agent can see in the queue. Focus on what is not obvious from the helpdesk.
How long should a shift handover take?
A few minutes when the notes are written during the shift. The checklist keeps it short, because each section is a quick list rather than a report. If handovers regularly take much longer, that usually points to too many open escalations or unclear ownership.
How do follow-the-sun support teams hand over?
They hand over in writing, because the outgoing and incoming agents are often not online at the same time. A short overlap or a quick call helps for escalations. The incoming agent confirms the handover, so ownership of every open promise is clear.
Updated