A WhatsApp message in English, Chinese, or any language your team doesn’t read tests more than reading comprehension. Inside the first 24 hours, 1CS’s Translate button gets a reply out the door. Once that window closes, Meta’s own documentation is blunt about what happens next: only an approved template reaches the customer, and a template approved in Thai doesn’t become one in Chinese just because you need it to.
When the message comes in a language nobody reads
A tourist asking about a pickup time, a cross-border buyer confirming a size, a regular customer’s relative messaging on their behalf — all of it lands in the same WhatsApp inbox, in whatever language they typed it in. Your team can still act on it fast, but reading it is only the first problem. The reply plan changes depending on how long the conversation has been quiet, not just on what the message says.
Set up in 1CS
On the web (chat.1cs.ai), open the conversation and right-click the message — or hover and use the ⋮ button next to it — then choose Translate. It shows “Translating…” for a moment, then the translation with a “Translated to [language]” label and a “View original” link to switch back. The destination language is whatever your account language is set to under Settings › Account settings, not something you pick per message, and the AI uses up to the previous three messages as context so it doesn’t mistranslate a sentence with no subject. Emoji, links, phone numbers, order or tracking numbers, prices, and product names are left exactly as written. It runs on 1CS’s own AI with nothing to configure, doesn’t currently cost credits, and is web-only — not yet on the mobile app.
Treat the result as a reading aid, not a certified translation: 1CS’s own guidance is explicit that this helps understanding quickly rather than guaranteeing accuracy, so reconfirm the price, date, or address with the customer again before you act on any of it. The click-by-click walkthrough is in Thai: แปลข้อความลูกค้าในแชต; the inbox it sits inside is covered in English on the unified inbox feature page.
The reply after the window needs its own approved language
Inside the 24-hour customer service window — the period that opens when the customer messages you and keeps resetting with each new message from them — your team can type a free-form reply in any language, translate button or not. We’ve covered that window in detail before; the part that matters here is what happens once it closes. Meta’s own WhatsApp Business Platform documentation states that “template messages are the only message type that can be sent outside of a customer service window” — so once 24 hours pass since the customer’s last message, a free-form reply in any language simply won’t send.
That’s where the language gap resurfaces. Meta’s template documentation requires every template to carry its own language code at creation, and says plainly that “template strings and variables are not translated by Meta.” A template named order_confirmed approved in Thai and the same name approved in English are two separate templates, each submitted and reviewed on its own. If the only order_confirmed template your account has ever gotten approved is the Thai one, a non-Thai-reading customer whose chat has gone quiet for a day has nothing you can actually send them until an English — or Chinese, or whichever — version clears Meta’s own review, on Meta’s own schedule, not yours.
As a recommended default rather than a platform rule, get the second-language version of your three or four most-used templates approved before a customer who needs them actually shows up — the same order-confirmation, shipping-update, and payment-reminder set already worth having ready for a restock ping is the one to duplicate into the other language first.
A holding line to save in two languages
While that second-language template is still waiting on approval, this fits inside the 24-hour window and buys time honestly, in English and in Chinese:
Thanks for your message! We’re checking this with our team and will reply here shortly. For anything about price, delivery date, or address, we’ll confirm it again before you pay — just so nothing gets lost in translation.
谢谢您的留言!我们正在核实,稍后会在此回复您。关于价格、到货日期或地址,我们会在您付款前再次确认,以免翻译出错。
Save both as 1CS quick replies under whatever label your team already uses for canned responses, so the same wording goes out every time rather than whatever the agent on shift types from memory.
