I implemented a Follow the Sun model at Tyco\/JCI across four regional centres — Shanghai, Echt, Heathrow, and North America — achieving genuine 24\/7 coverage without adding a single headcount. The coverage design took a week. The implementation took months. Most accounts of Follow the Sun focus on the design. This one focuses on what actually breaks during implementation and how to not let it.<\/p>\n
Follow the Sun is not a scheduling model. It’s a handoff model. The scheduling is the easy part — map your existing centres to GMT, design shift overlaps that eliminate gaps, write it in a spreadsheet. Done in a week. The hard part is making the handoffs work: ensuring that when Centre A’s shift ends and Centre B’s begins, Centre B has everything they need to continue active work without a transition delay that costs customers thirty minutes of context reconstruction.<\/p>\n
\nThe handoff protocol is everything. A Follow the Sun model is only as good as its handoffs. If the incoming centre doesn’t have full context on active cases, they spend the first hour of their shift reconstructing what the previous centre already knew. Standardise the handoff document before go-live — not after.<\/p>\n<\/blockquote>\n
The Three Systems That Have to Work<\/h2>\n
Telephony routing.<\/strong> Your phone system needs to route incoming calls to the active regional centre based on time of day — automatically, reliably, with fallback logic for centre unavailability. At Tyco\/JCI, rebuilding the telephony routing rules took weeks of vendor engagement. Know this is a project, not a setting, before you commit to a go-live date.<\/p>\n
Case management visibility.<\/strong> Every agent in every centre needs to see every active case, regardless of which centre opened it. This sounds obvious and is frequently not configured. Centre-siloed case views mean the incoming centre starts their shift blind to what’s in flight.<\/p>\n
Cross-regional reporting.<\/strong> You cannot manage a Follow the Sun model with centre-by-centre reporting. You need volume by time of day across the full 24-hour cycle, handoff success rates, and escalation patterns that span multiple centres. If your reporting infrastructure doesn’t produce this, you’ll be managing the model on instinct rather than data.<\/p>\n
Designing the Handoff Protocol<\/h2>\n
The handoff document is the operating unit of a Follow the Sun model. Every agent at Centre A, before their shift ends, completes a handoff summary for every active case. The incoming team should be able to continue any active case without contacting the customer to re-explain their issue. Each handoff entry should contain:<\/p>\n
\n\n✓<\/div>\nCase summary in plain language<\/strong> — what is the customer’s issue, in one paragraph, written for someone who has never seen the case before<\/p>\n<\/div>\n
\n✓<\/div>\nCurrent status<\/strong> — what has been tried, what worked, what didn’t, where the case is right now<\/p>\n<\/div>\n
\n✓<\/div>\nNext action<\/strong> — the specific next step the incoming centre should take, not “continue investigation”<\/p>\n<\/div>\n
\n✓<\/div>\nCustomer context<\/strong> — sensitivity level, previous interactions, relationship notes<\/p>\n<\/div>\n
\n✓<\/div>\nEscalation status<\/strong> — if internal teams are involved, who, what was asked, expected response time<\/p>\n<\/div>\n
\n✓<\/div>\nPriority flag<\/strong> — is this case time-sensitive in the next shift window?<\/p>\n<\/div>\n<\/div>\n
The temptation is to make the handoff document comprehensive. Resist it. A document that takes 20 minutes to complete per case will not be completed consistently. Six fields, five minutes per case, done consistently — that’s the target.<\/p>\n
The Culture Problem<\/h2>\n
The hardest part of Follow the Sun isn’t the technology or the protocol design. It’s getting teams in four countries to think of themselves as one continuous operation rather than four separate centres that pass work to each other. At Tyco\/JCI, the cultural shift happened over roughly six months. The mechanisms that accelerated it: cross-regional performance reporting (so every centre saw how the full 24-hour operation was performing), shared escalation protocols, and regular cross-regional conversations between regional managers that included sharing what each region was learning.<\/p>\n
Three Metrics That Tell You If It’s Working<\/h2>\n
Handoff completion rate:<\/strong> What percentage of active cases at shift end have a completed handoff document? Below 95% means the protocol is being skipped.<\/p>\n
Repeat contact rate at handoff:<\/strong> What percentage of cases required the incoming agent to contact the customer within the first hour? Above 10% means handoff documents aren’t transferring enough information.<\/p>\n
Time-of-day volume distribution:<\/strong> Is inbound volume actually distributed across the 24-hour window? This tells you whether your customers are benefiting from the coverage change — and whether off-peak centres have enough volume to justify their role.<\/p>\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
I implemented a Follow the Sun model at Tyco\/JCI across four regional centres \u2014 achieving genuine 24\/7 coverage without adding a single headcount. The coverage design took a week. The implementation took months.<\/p>\n","protected":false},"author":1,"featured_media":49,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[43],"tags":[45,48,44,46,49,50,47],"class_list":["post-48","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-global-ops","tag-24-7-coverage","tag-contact-centre","tag-follow-the-sun","tag-global-operations","tag-handoff-protocol","tag-shift-management","tag-telephony"],"_links":{"self":[{"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/comments?post=48"}],"version-history":[{"count":2,"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions"}],"predecessor-version":[{"id":55,"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions\/55"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/media\/49"}],"wp:attachment":[{"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/media?parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/categories?post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/datadrivenops.co\/blog\/wp-json\/wp\/v2\/tags?post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}