Skip to main content
Most platforms make you maintain a knowledge base per language. This one does not, and the distinction between chat and templates is where the real work is.

​
Chat: nothing to do

Set the agent’s reply language to match the customer and it answers in whichever language they wrote in. Your knowledge stays in one language. The agent translates as it answers.
Write your material in whichever language you maintain best — usually English. Translating your knowledge base by hand produces drift: the Hindi version says ₹1,200 and the English one says ₹1,400, and nobody notices for months.

​
The languages

37, including all 22 of the Eighth Schedule — Assamese, Bodo, Dogri, Konkani, Maithili, Manipuri, Santali and the rest — each in its own script in the picker, in one A–Z list.

​
Templates: real work, and worth it

Chat translates on the fly. Templates cannot — every one is submitted to Meta and approved in a specific language.
1

Set your contacts' languages

Each contact carries a language. Set it on import, or from the Contacts page.
A contact with no language set receives your default. So adding languages is always an improvement, never a prerequisite — nothing breaks for contacts you have not got to yet.
2

Create the variants

One template name, several languages. The editor can draft the translations for you, and the rule it holds to is strict:
A translation that changes the placeholders is refused, never repaired.If {{1}} and {{2}} swap order in the Hindi version, your customer gets the order number where their name should be. That is not a translation problem you want discovered by a customer, so a variant whose placeholder count or order differs from the original is rejected outright.
Always read the draft before submitting. It is a starting point, not a finished translation.
3

Send normally

Nothing changes at send time. Each contact receives the variant matching their language; anyone without one gets the default.The API takes no language parameter for the same reason — a template is identified by name, and its language is whatever it was approved in.

​
A worked case

A Pune business with Marathi, Hindi and English-speaking customers: A Marathi-speaking customer asks a question in Marathi and gets a Marathi answer drawn from English material. Their shipping notification arrives as the approved Marathi template. Nobody maintained a second knowledge base.

​
Where it will not help

  • Authentication templates. Meta writes and localises one-time password wording itself; rewording gets the template rejected.
  • Scanned documents in any language. There is no OCR.