Serving Europe After Brexit Without a European Site

A British company selling into Europe has a customer service problem that did not exist in 2015. Its customers are spread across a dozen markets, speak eight languages, expect support in their own, and are no longer served by whatever arrangement the business had before the UK left the single market.

The instinctive answer is a European site — somewhere in Ireland, Portugal or Poland with multilingual recruitment. It is a reasonable answer for large operations and an expensive one for everybody else, because multilingual European hubs carry a cost structure that only works at scale.

The alternative is less obvious and increasingly common: run English-language support and operational coordination from a single offshore site, and buy language capability as a specialist layer rather than as a whole operation.

What actually needs to be in-language

Not everything, and the distinction matters commercially.

Research into European consumer preference consistently finds that customers prefer support in their own language and will tolerate English in specific circumstances — typically for technical issues, for written channels, and where the alternative is a delay. Tolerance varies considerably by market: Dutch and Nordic consumers are generally comfortable in English; French, Italian and Spanish consumers markedly less so.

That variation allows a sensible segmentation. Markets with high English comfort can be served predominantly in English with in-language support for complaints and sensitive matters. Markets with low English comfort need in-language handling for anything beyond the simplest transaction.

Getting this wrong in either direction is costly. A business that insists on in-language coverage everywhere pays for capability it does not need in half its markets. A business that insists on English everywhere loses customers in France and Italy without ever learning why. Advisers who scope multilingual offshore operations begin with that segmentation for precisely this reason, because every subsequent decision inherits it.

“The mistake is treating Europe as one market with one language requirement,” said Ralf Ellspermann, founder and chief strategy officer at PITON-Global. “It is a dozen markets with a dozen tolerances, and the mix changes which operating model makes sense.”

Where the offshore hub fits

The Philippine advantage in this configuration is not language. It is everything around language.

English-language capability at scale handles the UK volume, the Nordic and Dutch markets, business customers across Europe who generally operate in English, and all written channels where comprehension is easier than conversation. It is the load-bearing half of the model, and the part Philippine call centre outsourcing for multilingual programmes is built to carry.

“Anyone telling you the time-zone question is trivial has not staffed a European afternoon shift from Manila for a year,” said John Maczynski, chief executive of PITON-Global. “It works. It works because somebody designed the rota around it and paid for the inconvenience, not because the problem went away.”

And the cost structure supports a specialist layer. A business paying European rates for an entire operation cannot afford much depth. A business running the volume offshore can afford genuinely good in-language handling for the interactions where it matters.

Operational coordination — case management, order investigation, back-office processing, escalation handling — sits well there regardless of the customer’s language, because much of it does not involve speaking to the customer at all. It is also the work that transfers most readily, and the work most often left behind in a language-first design.

Coverage, honestly assessed

Time zones are the real constraint in this model and the one most often glossed over.

Philippine working hours cover European mornings comfortably in the late shift and European afternoons in the overnight shift. A single-site operation serving European business hours is therefore working unsocial hours, which has consequences for recruitment, retention and the seniority of staff willing to do it.

This is manageable and it is not free. Operations that pretend otherwise end up with their least experienced staff on European afternoons, which is when their most demanding customers are calling.

The regulatory layer

Post-Brexit data arrangements add a dimension that a pre-2020 outsourcing contract will not have addressed.

A UK business serving EU customers is handling personal data subject to EU GDPR as well as UK requirements, and transferring that data to a third country. The mechanics — transfer impact assessments, the appropriate contractual safeguards, where data rests as distinct from where it is processed — need settling at contract rather than discovering at audit.

The question that catches businesses out is not storage but processing. Sending a conversation to a model that sits outside the UK moves the data, regardless of how the arrangement was labelled at procurement — and automation layers added after signature routinely do exactly that without appearing anywhere in the agreement.

Which takes longer — the service design or the data architecture? Consistently the second, and it costs a fraction as much settled before go-live as it does afterwards.

A practical sequence

Five steps, in order

Segment the markets first, on English tolerance, contact volume and commercial value. The answer is rarely uniform and everything downstream inherits it.

Put English-language and operational work offshore next, prove the model, and measure quality against the previous arrangement rather than against an aspiration.

Add in-language capability selectively, weighted toward complaints, retention conversations and the markets where English tolerance is lowest.

Settle the data architecture before go-live, including the transfer assessments and any automation layer that will process European customer data, because this is the element that cannot be retrofitted cheaply.

Revisit the segmentation annually. English tolerance shifts, market volumes move, and a model set correctly once becomes wrong quietly — usually in the markets nobody is reporting on.

See also: How Businesses Manage User Access

Why this model keeps appearing

Because it fits the shape of the problem. Most British businesses selling into Europe have volume concentrated in a few markets, a long tail of smaller ones, and insufficient scale in any single European language to justify a dedicated team.

A hub handling the bulk in English, with specialist language capability layered where it earns its cost, matches that distribution. A European site built for an idealised multilingual requirement generally does not — which is largely why a good number were quietly folded back into a hub a few years after opening.