Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

International Marketing › International Operations

Supporting Customers in Several Languages and Time Zones

How to support customers in several markets: which languages and hours to offer, stating them honestly, help content, translated replies, routing and reporting.
Guideintermediate9 min readUpdated

What changes when customers are in other markets

The guide to support channels and self-service chooses channels by the customers a business serves and the questions they ask, builds the help centre, sets chatbot handover, accessibility and service standards. All of it still applies. Several markets add four things.

Language. Every channel, article and reply has to work in each market's language, or say clearly that it does not. A customer who writes in their language and receives an English reply has been told something about the brand.

Time. The team's working day covers some markets' mornings and other markets' nights. A queue that is answered "within a day" may be answered while the customer sleeps, every time.

Questions. Customers in a new market ask different things: about delivery from abroad, local payment, returns across a border, product use under local conditions. The help content written at home does not cover them.

Reputation. In a market where the brand is unknown, a slow or wrong-language reply is one of the few experiences customers have of it, and they share it.

Map the support moments on the market's journey with the customer journey mapping framework, and mark where the customer needs help before buying, after buying and when something goes wrong. Those moments set the channels and hours each market needs.

Choosing languages and levels of support

Not every market needs every channel in its language from day one. Decide a level per market and channel, and write it down.

LevelWhat the customer getsTypical channelsFits a market that
FullLive and written support by fluent speakers of the language, during the market's working hoursChat, phone, email, socialIs established, or where the product needs spoken help
WrittenEmail or form support in the language, with replies drafted with machine assistance and reviewed by a fluent person where neededEmail, form, social messagesIs new or small, with mostly routine questions
Self-service with escalationHelp centre in the language; contacts handled in a shared language, with a clear route to a fluent person for sensitive casesHelp centre, emailIs a pilot, or shares a language with a larger market
Shared language onlySupport in English or another shared language, stated as suchEmailServes a niche audience that expects it, stated before purchase

Choose by the market's role in the roadmap, its volume of contacts, the complexity of the product and what customers there expect. The media and channels guide funds pilot, growth and established markets differently; support levels usually follow the same roles. A level can rise at the market's gate.

The level is a promise, so publish it. On each market's contact page, say which channels answer in which language, and whether a reply in another language is possible. Whether a market has rules about the language of customer service is a question for local advice; this guide gives none.

Hours, time zones and saying them plainly

Set each market's hours from its customers' day, not the head office's. Three patterns are common, and they can be mixed:

  • Market hours. Each market is covered during its own working hours by people in or aligned to its time zone.
  • Follow the sun. Teams in several time zones hand the shared queue on as their days end, so written contacts keep moving around the clock. Each handover needs a written note of open cases.
  • Core hours plus written cover. Live channels run in the market's core hours; a written channel stays open at all times with a stated reply time; urgent issues such as safety or outages have an out-of-hours route.

State the hours in the market's local time, with the time zone named, on the contact page, in the help centre and in automatic replies. Say what happens outside the hours: when a reply will come and where to go if it is urgent. The rest of that page, from answers to the top contact reasons to a short form and a route for urgent problems, is built in the tutorial on designing a customer contact page. Mark local public holidays in the support calendar, using dates the market owner supplies, and say in advance when cover is reduced. An automatic acknowledgement in the customer's language, stating when a person will reply, removes much of the frustration of a time-zone gap. It does not stop the clock on time to first reply, which runs until a person answers.

Help content in each language

The help centre answers most questions in most markets, if it exists in the language. Translate the articles that answer the most frequent and most important questions first: setting up and using the product, delivery and returns for that market, payment, and anything about safety. Use the contact log and search terms in the help centre to choose, not the order articles were written in.

Help content is informational, so it sits towards the faithful end of the translation and transcreation guide's spectrum: accurate, consistent with the termbase, reviewed by someone who knows the product. Add articles that only a market needs, such as delivery from abroad or local payment questions, written for that market rather than translated from home.

Keep each language's articles accessible. The support channels guide takes the Web Content Accessibility Guidelines (WCAG) as the reference for help articles, forms and chat widgets: headings, alternative text for images, labelled forms and more than one route to a person, including a written channel and a spoken one where that is offered. A translated article needs the same structure as the source, not a block of text pasted in.

When the source article changes, the language versions must change too. Record which version each translation was made from, so a stale article can be found.

Translated replies and their review

Where no fluent agent is available, replies can be written in a shared language and translated, or drafted in the customer's language with machine assistance. The AI in customer service guide sets the boundaries that apply: routine questions answered from approved help content can be assisted or automated; complaints, refunds and exceptions, legal and safety matters and customers in vulnerable situations stay with people, with AI at most summarising the history.

Apply the same rules across languages:

  • Routine replies drafted with a language model or a translation tool can be sent after an agent checks them against the help content; sample them weekly with a fluent reviewer, using the scorecard from the tutorial on reviewing support conversations for quality.
  • Sensitive replies (complaints, refunds, safety, legal, anything where tone matters) are reviewed by a fluent person before sending, or handled by one.
  • Product and brand terms follow the termbase, so a reply does not call the product something the site does not.
  • Saved replies in each language need the owner and review date the tutorial on building a library of saved replies gives every reply, so a policy change reaches every language at once.

Customer messages contain Personal Data. Translation tools and suppliers receive only what a reply needs, under the business's own data policy, which whoever owns data protection sets.

Routing, escalation and social replies

Route by language and market from the first contact. Tag every contact with both, from the edition the customer used, the address on the order or the language detected, which the AI guide describes as a routine triage task to assist and check. Send each to a queue that can answer it, and send sensitive topics to people at once, whatever the language.

Escalation needs a route that crosses markets. When a contact in a market with written-only support needs a fluent person, name who that is: a native-speaking colleague, a partner's support team or an on-call reviewer. When a complaint needs a decision, the service recovery and complaints guide applies, with the reply in the customer's language.

Social channels are support channels in many markets. Comments and messages on a market's social account arrive in the market's language and at its hours, and the community management guide sets the standards for replying. Write down who answers each account at which hours, and where a message goes when nobody can answer in that language.

Reporting service by market

Report service per market on the same definitions, as the measuring and reporting guide asks of marketing figures. For each market and channel: contacts, the top contact reasons, time to first reply in local hours, resolution in the first exchange, repeat contacts and satisfaction. Make each a key performance indicator (KPI) with an owner, reported weekly.

Two readings matter most across markets. A market whose contacts are dominated by a reason other markets rarely see, such as delivery or payment, has a site or offer problem that support is absorbing; send it to the market owner. The diagnosis of an international site edition that is not converting gives that owner the path to walk when such contacts coincide with a conversion gap. And a market whose satisfaction lags the others on the same reasons usually has a language or hours problem. The voice of the customer guide turns those signals into a loop that reaches the teams who can fix them.

A thermostat maker supports two new markets (illustrative)

Illustrative example — not a real result

Yorrixa Thermostats supports Market A and Market B

Yorrixa Thermostats, an invented maker of smart thermostats, opens Market A and Market B in the same quarter. Market A is a growth market with a shared time zone; Market B is a pilot 6 hours ahead of head office.

Market A gets full support: 2 native-speaking agents on chat and email during its working hours. Market B gets written support: email in its language, with replies drafted by a translation tool, checked by an agent and sampled weekly by a fluent freelance reviewer, and a reply within one Market B business day. Each market's contact page states its channels and hours in local time; Market B's automatic acknowledgement, in its language, says when a reply will come.

The 25 most-viewed help articles are translated first for both markets, plus 4 articles written for each market about delivery and installation. Safety and billing contacts route straight to people: in Market B, to a native-speaking engineer at the installation partner.

The weekly report shows Market B's satisfaction at 3.6 out of 5 against 4.4 in Market A by week 4. Contact reasons show the gap: installation questions answered by email that customers wanted to talk through. Yorrixa adds 2 hours a day of phone support in Market B's language through the partner, and satisfaction reaches 4.2 by week 10.

Common mistakes

  • Promising support in a language nobody answers. State which channels answer in which language, and keep to it.
  • Publishing hours in head office time. Customers read the hours in their own time. State them locally, with the time zone.
  • Translating help articles in the order they were written. Translate the most-asked questions first and add articles each market needs.
  • Sending machine-translated replies on sensitive topics unchecked. Complaints, refunds, safety and legal matters go to people, or to a fluent reviewer before sending.
  • Routing by channel and not by language. A contact sits in the wrong queue until someone notices. Tag language and market at the first touch.
  • Leaving the market's social account unanswered. Social messages are support. Name who answers, in which language, at which hours.
  • Reporting support as one global number. A market with a language or hours problem disappears inside the average. Report by market.
  • Pasting customer messages into any tool. Messages contain personal data; send tools only what a reply needs.

Frequently asked questions

Do we need native-speaking agents for every market?

Not always at first. A market can start with written support in its language, using machine-assisted replies that a fluent person reviews before anything sensitive is sent, and add live channels with native speakers once volume and value justify it. What a market should not get is a promise of support in its language that the business cannot keep. Say plainly which channels answer in which languages, and when.

Should we offer support around the clock to cover every time zone?

Only if the customers need it and the business can staff it. Many businesses cover each market's working hours on the main channels, leave a written channel open at all times with a stated reply time, and keep round-the-clock cover for urgent issues such as safety or service outages. Whatever the hours, publish them in each market's local time, not the head office's.

Can we use a language model to translate support replies?

For routine questions answered from approved help content, often yes, with a fluent person reviewing anything sensitive. The site's AI in customer service guide keeps complaints, refunds, safety, legal topics and customers in vulnerable situations with people. Customer messages contain personal data, so the tool receives only what a reply needs, under the business's own policy.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Web Content Accessibility Guidelines (WCAG) — W3C

Related