Getting a Follow the Sun model live is genuinely hard work \u2014 the coverage design, the telephony reprogramming, the handoff protocol, the cultural shift across multiple time zones. I\u2019ve written about what that implementation looks like in practice. But go-live isn\u2019t the end. It\u2019s when a different set of problems begins.<\/p>\n\n\n\n
At Tyco\/JCI, we implemented Follow the Sun across four regional centres<\/a> \u2014 Toronto, Montreal, Heathrow, and Echt \u2014 achieving genuine 24\/7 coverage without adding headcount. The first few weeks after launch were instructive in ways the planning phase hadn\u2019t been. Here\u2019s what we learned about keeping the model healthy once it\u2019s running.<\/p>\n\n\n\n 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\u2019t sound under load.<\/p>\n\n\n\n When call volumes hit normal operating levels across all centres simultaneously<\/a>, the networking infrastructure showed cracks that hadn\u2019t 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\u2019t want.<\/p>\n\n\n\n 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\u2019s 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.<\/p>\n\n\n\n Your first notice of a telephony problem should never come from a customer. By then, you\u2019ve already failed the experience. Monitor and test proactively \u2014 don\u2019t wait to be told.<\/p>\n<\/blockquote>\n\n\n\n We had enough headcount across the four centres to cover the designed shift pattern. What we hadn\u2019t built in adequately was buffer capacity for the realities of running a human operation \u2014 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n The Echt centre was our most experienced team \u2014 senior, technically strong, and accustomed to being the fallback for North America before the Indian team came on board. They\u2019d 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.<\/p>\n\n\n\n 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\u2019t to diminish the Echt team \u2014 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\u2019t 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\u2019s position more secure.<\/p>\n\n\n\n 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 \u2014 cultural alignment across a global operation always does \u2014 but the consistent approach worked.<\/p>\n\n\n\nThe First Thing That Breaks: Telephony at Load<\/h2>\n\n\n\n
\n
The Second Thing That Breaks: Staffing Buffers<\/h2>\n\n\n\n
The Third Thing That Breaks: Cultural Holdouts<\/h2>\n\n\n\n
What Good Looks Like: The Metrics Worth Watching<\/h2>\n\n\n\n