Choosing a Support Centre Structure

The right support centre structure depends on consumer and service needs, because centralised, virtual, local, follow-the-sun, specialist and outsourced models each trade off consistency, proximity, resilience, cost and knowledge differently. The support centre is both a point of contact and a source of service intelligence, so its design should reduce consumer effort and feed improvement across the enterprise.

• Begin by defining consumer and service needs, then compare the structural trade-offs of each model against them.
• Design common standards and handoffs, and pilot critical interfaces before committing. Capture the current baseline first so any benefit can be demonstrated. In the article's example, a global service uses common tooling and standards but keeps local-language teams for high-context support.
• Measure handoff success, coverage and consumer satisfaction by segment as a set, with an agreed baseline, data source and owner for each. Read them together: a stronger headline is not enough if quality or consumer effort deteriorates elsewhere.
• Avoid choosing on cost alone, calling dispersed teams virtual without common practice, and ignoring language and local context.
• Where ownership crosses boundaries, keep shared standards and handoffs on the joint agenda, and review results with delivery teams and consumers, because operational success and experienced value can diverge.