The Ticket That Travelled the World

Picture this. It is 16:47 in London. A regional operations lead is mid-incident — a line-of-business tool has gone quiet for a cluster of colleagues in the Middle East. She has already spoken to the Service Desk twice. The analyst has the logs, the timeline, the workaround that almost worked. Shift change is in thirteen minutes.

The ticket is assigned to the overnight queue. The notes say “escalated — see comments.” The comments say “user will test in the morning.”

Morning arrives in Singapore. A different analyst opens the ticket. The context is a trail of fragments. They call her. She explains it again. They ask for the same screenshots. By the time EMEA is back at the desk, the issue has travelled the globe and aged twelve hours — and nobody can quite say who owns it.

The dashboard still looks fine. The ticket moved. Coverage was “24/7.”

The human experience was not.

This is the dropped baton.

The Problem Is Human, Not Geographical

I have spent a lot of time leading distributed support — UK, EMEA, APAC — in a genuine follow-the-sun model. On paper it is elegant Cloud Magic. Work follows daylight. Major incidents keep moving while you sleep. The Modern Workplace, we tell ourselves, never closes.

The machine metrics will often agree. Tickets change assignee. Volume is covered. First-contact resolution looks healthy if you count the first queue that touched it.

The colleague on the other end does not experience a globe. They experience one conversation that keeps starting over. That is DEX for global operations. Not “did the ticket move.” Did the person feel held?

I have coached analysts who inherited a zombie at 02:00 with nothing but a priority field and “chasing vendor.” I have sat on the incident bridge at shift change and watched context leak as one timezone signs off and another signs on.

Follow-the-sun that only moves tickets is logistics. Follow-the-sun that moves understanding is service.

What a Clean Handoff Actually Looks Like

A healthy follow-the-sun operation is not a twenty-four-hour conveyor belt. It is a relay. You should be able to answer, without a forensic read of forty comments:

  • What do we actually know — and what have we already ruled out?
  • What did the last human try, and what happened?
  • Who is the colleague, in their timezone, and when did we last speak to them?
  • What is the next concrete action — not “investigate,” a real next step?
  • Who owns the baton right now, even if the working analyst is about to change?

Tickets can have an assignee. Incidents need an owner.

What good looks like is unglamorous: a handoff checklist (symptoms, evidence, attempts, next action, user context), a warm transfer written for the incoming human — voice on the major-incident bridge, not a comment at 16:59 — and a living timeline so EMEA-to-APAC does not reset the story. Analysts can change. The owner does not evaporate at sunset.

I review handoff quality the way I review tone, FCR, and CSAT. The same “how do I…?” should not become three tickets in three regions. When we got serious about knowledge, self-service, and RCA, we drove recurring incidents down materially — on the order of a third. Fewer people explaining the same failure to a new face every morning.

The Trap Teams Fall Into

Here is the practical nuance most teams miss.

Most organisations staff the clock, publish the rota, and celebrate 24/7 coverage. You will recognise the pattern. SLAs stay green. Overnight tickets become zombies — updated enough to keep the clock honest, not enough to move the problem. Users learn that “follow-the-sun” means “tell the story three times.” Analysts park the messy inheritances. CSAT quietly sags, because the ticket did move.

That is 24/7 coverage that is actually 24/7 confusion. Green on the outside — a close cousin of the watermelon problem — and a colleague who has lost an afternoon on the inside.

The other trap is treating handoff as a tooling problem. Jira Service Management will dutifully change the assignee. None of that writes the story. If your process rewards closing the loop in your shift more than setting up the next one, you will get heroic local metrics and a global mess.

Zero Trust is useful here as a metaphor. Trust nothing that is not verified — including the assumption that “someone has it.” Then get out of the way: Zero Friction for the person who just wants their tool back.

This Week’s Challenge: Hold the Baton

My challenge to you this week is simple. Do not start with a new tool. Start with one relay.

Pick one ticket that crossed a timezone in the last seventy-two hours. Read it as if you were the incoming analyst at 02:00.

Ask:

  1. Can I take the next action without calling the colleague back to re-explain?
  2. Is there a named owner, or only a last assignee?
  3. Would I be proud to put my name on this note?

If any answer is no, that is the dropped baton.

Then write a one-page handoff checklist with your team — five to seven fields — and use it for the next five cross-region handoffs. Coach the first one live.

When follow-the-sun carries the story as well as the ticket, coverage stops being a scheduling trick — and DEX stops being undermined by the clock.

That is when the Cloud Magic feels intentional again. And work starts to feel a little more human.

Thanks for reading. See you next week.