Home / Guides / Escalations and support operations

A support shift handover template that stops promises getting dropped

By Draft First. Updated October 2026

Most dropped tickets aren't dropped by the person who had them. They're dropped at the handover, when "I'll get back to you by 9" leaves with the outgoing shift. A good handover note is short, lists only what needs action and puts the promises first.

What goes in it

1. Promises due next shift. Anything a customer was told, with the time and time zone. This is the part most often missed.
2. Open cases that need action. Ticket ID, one line of status, the next step and who's waiting on whom.
3. Live escalations. Where each one stands and when the next update is due.
4. Things to watch. A deployment tonight, a known bug bringing in tickets, a customer who's close to escalating.
5. Who to call. The on-call engineer or backup lead for the next shift, if it's changed.

Leave out tickets that are just waiting on the customer, and anything the next shift doesn't need to act on.

The template

HANDOVER [outgoing shift] to [incoming shift] | [date, time, zone]
From: [name]

PROMISES DUE
- #[ID] [account]: told them [what] by [time, zone]

NEEDS ACTION
- #[ID] [one line of status] | Next: [step] | Waiting on: [who]

LIVE ESCALATIONS
- #[ID] [status] | Next update due [time, zone] | Owner: [name]

WATCH
- [deployment, known issue, unusual volume, upset customer]

ON CALL / BACKUP: [names]
Reply with a thumbs up when you've read this.

A filled-in example

Made-up names and tickets.

HANDOVER US to EMEA | Tue Oct 13, 6:00 PM ET
From: Dana

PROMISES DUE
- #4843 Oakhollow Retail: told them we'd confirm the printer
  driver fix by 9:00 AM ET Wed.

NEEDS ACTION
- #4858 Halden Freight: reports not loading. Workaround (CSV by
  email) in place. Next: confirm workaround still running |
  Waiting on: engineering

LIVE ESCALATIONS
- #4858 as above | Next update due 4:00 AM ET | Owner: Leo

WATCH
- Release at 2:00 AM ET. Watch for login errors after it.

ON CALL / BACKUP: Priya (support), Leo (engineering)

Let an AI agent draft it from the queue

The slow part is going back through every open ticket to find what you promised. An agent that can read your ticket system can do that in a minute. Use read-only access, and check the draft before you post it.

From [ticket system], list the open tickets owned by [my name or
my team], not counting status [statuses to ignore].
For each one, find any reply where we told the customer we'd do
something by a time or date, and quote it with the ticket ID.
Draft a handover note with these headings: Promises due in the next
[12] hours, Needs action, Live escalations, Watch.
Put any time without a time zone as [CONFIRM].
Use only what's in the tickets. Leave Watch empty for me to fill in.
Under 25 lines. This is a draft for me. Don't post or change anything.

Then add the part only you know: what's unusual about today. The agent can't see the tense phone call or the release everyone's nervous about.

Make it a habit

• Same template, every shift, even quiet ones. "Nothing due" is useful information.
• The incoming shift confirms they've read it.
• Once a week, look at the handovers next to the queue. If one person always hands over twice as much, that's a workload problem, not a handover problem. The weekly workload check shows it.

For handing over a single complex case rather than a whole shift, the ticket summary prompts include a handoff note.

Questions

How long should a handover note be?

Short enough to read in two minutes. List only cases that need action next shift. Everything else is already in the ticket system.

Where should the handover live?

Somewhere the next shift will definitely look, like a pinned post in the team channel, with the detail on each ticket as an internal note.

Should the incoming shift confirm they got it?

Yes. A one-word reply or a reaction is enough. A handover nobody read is the same as no handover.

Can AI write the handover?

It can draft it from the queue and your notes, and it's good at finding promises in ticket replies. The outgoing person should check it, because only they know what's unusual about today.