Inbox handoffs across time zones without dropped threads

Handoff: Ana → Chen, [date] 15:30 UTC

Needs action from you:
- [Customer A] billing error – refund approved by Dee, please process
  and reply. Thread: [link]
- [Prospect B] demo request – replied with times, watch for their
  answer, book it if they pick one

In progress, I'll continue tomorrow:
- [Customer C] data import issue – I'm mid-investigation, don't reply
  unless they escalate

Waiting on customer (no action unless they reply):
- [Customer D] asked for logs, follow up [date]

Heads-up:
- Payment provider status page shows delays; expect billing questions

Play 4: Decide which threads to pass and which to finish#

Not every thread should be handed off. Passing a thread means the next person has to read it, understand it and possibly re-ask questions. That has a cost.

Finish it yourself (keep ownership across days) when:

• You've built context with the customer over several messages
• It's a complex investigation where switching people means starting over
• The customer is upset and a new voice would feel like being passed around
• It can wait until your next shift without harm

Pass it on when:

• The customer is waiting on something time-sensitive that will happen during the next person's hours
• It's a quick action that's fully defined ("process this refund")
• The customer is in the next person's time zone and will reply during their day

When you keep a thread overnight, tell the customer: "I'll pick this up first thing tomorrow, my time." When you pass it, tell them too: "My colleague Chen will follow up this afternoon."

Play 5: Make ownership visible#

The biggest risk in follow-the-sun is the assumption gap: "I thought you had it." Every thread that's open should show, in the tool, who owns it right now. Whether that's done with a label, a status, or a note at the top of the thread, it should be obvious to someone who opens the thread without reading the handoff.

When ownership transfers, update it at the moment of handoff, not later.

Play 6: Set time-zone-aware expectations for customers#

Customers don't care how your team is distributed; they care when they'll hear back. Make that predictable.

• Publish your support hours in a time zone customers understand, or in several. "We reply between 04:30 and 00:00 UTC on weekdays" is clearer than "24/5-ish."
• Base SLA targets on business hours you actually cover. If nobody works 00:00–04:30 UTC, a message sent at 00:30 shouldn't count against a two-hour target until 04:30.
• Use an auto-acknowledgment that mentions timing for messages arriving during the gap: "We've got your message. Our team is offline right now and will reply within a few hours of [time]."

Play 7: Watch for the classic failure points#

• Daylight saving changes. Coverage shifts by an hour twice a year, and not on the same dates in every country. Review the coverage map when clocks change.
• Public holidays. A holiday in one country can quietly remove a whole block of coverage. Keep a shared calendar of everyone's holidays.
• Friday-to-Monday. The last person on Friday hands off to the first person on Monday, often two days later. Make Friday's handoff note especially thorough.
• Silent handoffs. Someone logs off without posting a note because "nothing happened." Post a note anyway: "Nothing to hand off" is useful information.

Handoff checklist#

• Coverage map in UTC, including the gap and overlap windows
• Handoff note posted at every shift end, in the fixed format
• Ownership updated in the tool at the moment of handoff
• Customers told when a thread changes hands or waits overnight
• Support hours published; SLAs based on covered hours
• Coverage reviewed at daylight saving changes and around holidays

Key takeaways#

• Map coverage in one reference time zone to find overlaps and gaps.
• Hand off in overlap windows, with a fixed four-part note.
• Keep complex or emotional threads with one owner; pass quick, time-sensitive ones.
• Make current ownership visible in every open thread.
• Base customer expectations on the hours you actually cover.