Getting a Follow the Sun model live is genuinely hard work — the coverage design, the telephony reprogramming, the handoff protocol, the cultural shift across multiple time zones. I’ve written about what that implementation looks like in practice. But go-live isn’t the end. It’s when a different set of problems begins.
At Tyco/JCI, we implemented Follow the Sun across four regional centres — Toronto, Montreal, Heathrow, and Echt — achieving genuine 24/7 coverage without adding headcount. The first few weeks after launch were instructive in ways the planning phase hadn’t been. Here’s what we learned about keeping the model healthy once it’s running.
The First Thing That Breaks: Telephony at Load
We had given customers a single number to call and were routing calls on the backend between centres based on time of day. The design was sound. What we discovered at launch was that it wasn’t sound under load.
When call volumes hit normal operating levels across all centres simultaneously, the networking infrastructure showed cracks that hadn’t appeared in testing. Calls transferring between regions experienced packet loss. Customers were hitting dead air or, worse, voicemail in the middle of what should have been a seamless handoff. The first notice we had of the problem in some cases was a frustrated customer, which is exactly the feedback loop you don’t want.
The resolution required working directly with the telco providers to redesign the routing architecture for real-world load, not testing conditions. That took time and several rounds of adjustment before it was stable. The lesson: your telephony setup needs to be stress-tested at realistic volume before go-live, not just validated in low-load conditions. And once it’s working, it needs to be monitored and tested on a regular cadence, because telco issues are endemic. Infrastructure drifts. Routing rules get touched during maintenance windows. The configuration that worked in January may not be working the same way in June.
Your first notice of a telephony problem should never come from a customer. By then, you’ve already failed the experience. Monitor and test proactively — don’t wait to be told.
The Second Thing That Breaks: Staffing Buffers
We had enough headcount across the four centres to cover the designed shift pattern. What we hadn’t built in adequately was buffer capacity for the realities of running a human operation — sick days, vacation, unexpected attrition, training pulls. When a Follow the Sun model is designed to minimum coverage, any absence creates a gap. And gaps in a 24/7 model have nowhere to hide.
The optimisation here was less dramatic than the telephony fix but just as important: revisiting the staffing model to build in realistic absence assumptions, cross-training agents across adjacent product lines so coverage could flex when individual agents were unavailable, and creating clear escalation protocols for when a centre came in under minimum numbers. The model needs headroom, not just headcount.
The Third Thing That Breaks: Cultural Holdouts
The Echt centre was our most experienced team — senior, technically strong, and accustomed to being the fallback for North America before the Indian team came on board. They’d supported all four products, and they knew it. The Follow the Sun model redistributed that responsibility, and not everyone in Echt was immediately enthusiastic about what they perceived as a reduction in their operational importance.
The optimisation approach here was sustained rather than one-time. We ran regular townhalls and leadership visits to that location. We made the case clearly and repeatedly: the goal wasn’t to diminish the Echt team — it was to stop asking customers to wait 24 hours for a response to a critical issue. We showed them, specifically, that adding the Indian centre hadn’t affected their headcount or their compensation. What it had done was make the customer experience significantly better, which made the whole business stronger, which made everyone’s position more secure.
We also showed them the data. Customer satisfaction scores improving. Critical issue response times dropping. When the business case is visible in numbers rather than just presented as a talking point, it lands differently. It took time — cultural alignment across a global operation always does — but the consistent approach worked.
What Good Looks Like: The Metrics Worth Watching
Once the model is stable, these are the four metrics that tell you it’s actually healthy — not just operational, but performing at the level it was designed for.
Handoff Completion Rate
What percentage of active cases at shift end have a completed handoff document in the CRM? Below 95% means the protocol is being skipped. Find out why before addressing it — the cause is usually either the process is too burdensome or agents don’t believe the incoming centre reads it. Fix the right problem.
Repeat Contact Rate at Handoff
What percentage of cases required the incoming agent to contact the customer in the first hour to re-establish context? Above 10% means handoffs aren’t transferring enough information. Pull a sample of those cases and read the handoff notes — the gap will be obvious.
Telephony Transfer Success Rate
What percentage of cross-centre call transfers connect cleanly — no dead air, no voicemail, no dropped call? This should be tracked weekly, not monthly. Telephony degradation is gradual, and you want to catch it before customers do.
Time-of-Day Volume Distribution
Is inbound volume actually distributed across the 24-hour window, or is it still concentrated in one or two time zones? This tells you whether customers are genuinely benefiting from the model or whether you’ve built 24/7 infrastructure for a problem that only occurs in an 8-hour window.
The Optimisation Discipline Most Teams Skip
The single biggest mistake I see organisations make after a Follow the Sun model goes live is treating it as static. The model is built, the coverage is working, and attention moves to the next initiative. The assumption is that if nothing is visibly broken, nothing needs attention.
That assumption is wrong, and it’s expensive when it fails.
Telephony infrastructure drifts. Routing configurations change during maintenance. Telco providers make backend changes that affect your setup without notifying you. The handoff protocol that 95% of agents were following at launch slips to 80% six months later as new hires join without the same training intensity as the original cohort. The staffing buffer that existed at go-live gets eroded by attrition that wasn’t backfilled fast enough.
None of these failures announce themselves loudly. They accumulate quietly until something breaks badly enough to be visible — and by then, the customer impact is already real.
Follow the Sun is infrastructure. You don’t complete infrastructure — you maintain it. The teams that treat it as a project to be finished are the ones who get surprised when it stops working.
The Ongoing Maintenance Cadence
Build these into your operating rhythm before you need them urgently:
The Payoff
When Follow the Sun is optimised rather than just operational, the customer experience change is real and measurable. Critical issues that once waited 24 hours for a response get picked up within the hour. Customer satisfaction scores reflect it. The team’s sense of operating as a single global function — rather than four separate centres passing work to each other — becomes genuine rather than aspirational.
That shift doesn’t happen at go-live. It happens through the months of sustained work after: the telephony tests nobody notices when they pass, the handoff audits that catch slippage early, the leadership visits to the centre that needs more attention. The maintenance is the model. Don’t outsource it to the assumption that things are fine because nothing is visibly broken.