parley
DocsPlatform
Resources
JournalIdeas on running AI supportCustomer storiesHow teams use ParleyGuidesStep-by-step playbooksChangelogWhat shipped, by versionHelp centerAnswers and support
CustomersPricing
LoginGet started
DocsPlatformCustomersPricingJournalCustomer storiesGuidesChangelogHelp center
Get startedLogin

Take charge of your AI customer experience

Get startedTalk to sales

Platform

Platform overviewChannelsPlaybooksIntegrationsAnalyticsPricing

Resources

DocumentationGuidesCustomer storiesJournalChangelogHelp center

Company

AboutCareersContact salesContact supportTerms of servicePrivacy

Security

Trust centerSOC 2ISO 27001GDPRHIPAAData processing
parley

© Parley. All rights reserved.

Journal · Operations

One agent, every language: localising support without a second build

Translating an agent market by market creates drift. Here is how teams run one agent in many languages and keep every answer consistent.

RARuth AdeyemiSolutions Lead · 5 min read

The usual path to a multilingual agent is to build it in one language and copy it for the others. It works for a quarter. Then a policy changes, three of eleven copies get updated, and customers in smaller markets start getting different answers.

One source of truth, many languages

Write playbooks and policies once, in the language your team works in. Let the agent answer in the customer's language from that single source. A policy change is then one edit, and it holds everywhere at the same moment.

Localise what is actually local

  • Legal wording that must appear verbatim in a market
  • Payment methods, carriers and opening hours
  • Tone: some markets expect more formal address than others

Keep these as small market-specific knowledge entries rather than separate agents, so the shared logic never forks.

Check quality per market

Average resolution can hide a market that is struggling. Break the scorecard down by language and review a sample of conversations in each with a native speaker every month.

A policy change should be one edit, and hold everywhere at the same moment.

Hand over in the customer's language

When the agent hands over, route to a person who speaks the language, or pass the conversation with a translation alongside the original so nothing is lost. The customer should never have to switch languages to reach a person.

RARuth AdeyemiSolutions Lead, ParleyAll posts

Keep reading from the journal

All posts
Conversation design6 min read

What a good handoff from AI to a person actually looks like

Read
Measurement7 min read

Measure resolution, not deflection: a CX scorecard your finance team will trust

Read
Knowledge6 min read

Writing support policies an AI agent can follow word for word

Read

Try it on your own conversations

Start building an agent in minutes, or talk to us about your support volume.

Get startedTalk to sales