Translating into Thai at the right level of politeness

This means a translation into Thai cannot be neutral. Every rendered sentence sits at some level of formality, implies a speaker with a gender, and addresses a listener with a rank. A translation that is technically accurate and set at the wrong register reads as a bank talking like a teenager, or a game talking like a ministry. The register is a decision, and the sections below walk through each part of it.

The same action has several Thai verbs, each with its own level. To eat is กิน between friends, ทาน to a customer or a guest, and รับประทาน in an announcement or a formal notice. To die is ตาย in speech and เสียชีวิต in the news. To tell someone is บอก at home and แจ้ง in a letter from a company. A translator picks the tier for the whole document, and a reader hears the tier in the first line.

The verb tier is the least visible of the three signals because it hides inside ordinary sentences. It is also the one a non-Thai reviewer misses most often, since a bilingual dictionary lists all three verbs under the same English headword. The particles and pronouns are louder, and they are where most translation complaints begin.

A Thai sentence usually ends with a particle that has no dictionary meaning and carries most of the politeness. The particle also states the speaker's gender. ครับ marks a male speaker, ค่ะ a female speaker, and both are the default in customer-facing text. Dropping the particle turns a polite sentence into a flat one. Choosing the wrong one turns a hotel into a stranger.

Two details trip up most machine output. First, คะ with a high tone is the question form and ค่ะ with a falling tone is the statement form. Swapping them is the most common spelling error in Thai customer service text. Second, นะ softens a request, and a customer service line that omits it sounds like an order. A translation that ends กรุณารอสักครู่ค่ะ is polite. The same line ending รอสักครู่ is a command.

English has one you and one I. Thai has a ladder for each, and the rung fixes the relationship. ท่าน is reserved for officials, executives, and letters that want distance. คุณ is the safe second person for a customer. เธอ and นาย belong to friends and fiction. On the first-person side ดิฉัน is a formal woman, ผม a polite man, ฉัน a neutral woman in writing, and เรา a company speaking as a company.

Most product text does well with คุณ for the reader and เรา for the company, which avoids picking a gender for the brand in the pronoun. Interfaces often drop the pronoun altogether: บันทึกแล้ว says saved without naming who saved it. A translation that inserts คุณ into every sentence reads as padded, because Thai omits a subject whenever context supplies it.

The English line "Your order will arrive tomorrow." has no register. Each Thai rendering below is a correct translation of it, and each belongs to a different business. The particle is written for a female speaker in the first two rows, which is the convention most Thai support teams follow for a brand voice.

Read the three rows again for what changes. The formal row uses ท่าน, the full verb จัดส่ง, and the noun สินค้าที่ท่านสั่งซื้อ for order. The polite row switches to คุณ, borrows ออเดอร์ from English, and softens with นะคะ. The casual row drops the pronoun, shortens order to ของ, and keeps only นะ. Length falls from 48 characters to 16 while the meaning holds.

Because ครับ and ค่ะ name the speaker's gender, every polite sentence a company publishes makes the company male or female for that sentence. Thai brands settle this once. Most consumer brands, banks, and airlines write as a female speaker with ค่ะ, following the convention of the call center and the front desk. Some brands with a male persona, such as a sports channel, write with ครับ.

The failure mode is mixing. A help center that answers one article in ค่ะ and the next in ครับ reads as two different people, and a Thai reader notices at once. Decide the speaker before the first translation, write it into the brief, and check every batch against it. Short interface strings have a neutral option. Leave the particle off and use the plain verb, as native apps do for buttons and labels.

Formal Thai in the wrong place feels like a form letter. A push notification that says ขอเรียนให้ท่านทราบว่าคำสั่งซื้อของท่านได้รับการยืนยันแล้ว is correct and nobody wants to read it on a lock screen. The polite version ยืนยันคำสั่งซื้อแล้วค่ะ carries the same fact in a quarter of the characters, which also matters on a phone.

Casual Thai in the wrong place feels like an insult. A payment failure that says จ่ายไม่ผ่านนะ ลองใหม่ uses the friend register, and a customer who has just lost money reads it as flippant. The polite version การชำระเงินไม่สำเร็จค่ะ กรุณาลองใหม่อีกครั้ง names the problem and the next step at the register a bank would use. The rule of thumb is that money, health, legal, and error messages move one rung up, and marketing for a young audience moves one rung down.

Thai borrows English words constantly, and a translation has three ways to write each one. The established Thai spelling exists for common words: โปรโมชัน for promotion, แอปพลิเคชัน for application, อีเมล for email. A transliteration renders a newer word in Thai script even where no dictionary form exists, such as แดชบอร์ด for dashboard. Preserving keeps the Latin script, which is what Thai text does with product names, technical terms, and codes: iPhone, API, OTP.

Register decides which option a reader expects. Formal text prefers the established Thai form and keeps Latin only for proper nouns. Polite product text mixes freely, and กด Save next to บันทึก is common in Thai apps. Casual text keeps more English because young Thai speakers code-switch in speech. Product names, feature names, and error codes should stay in the source script at every register. A transliterated product name is unsearchable and reads as a typo.

Register drifts across a product because text is translated in batches over months by different people. The support macros arrive polite, the onboarding tour arrives casual, the terms arrive formal. A style sheet fixes the three decisions in writing, which are the speaker particle, the pronoun pair, and the borrowed-word policy. A glossary fixes the terms that must never vary, such as the Thai form of each feature name and the words that stay in Latin script.

Thai has one further consistency trap. The word for you inside a sentence and the word in the greeting must agree in rank. A message that opens เรียน คุณสมชาย and continues with ท่าน has shifted register mid-paragraph. Keep one pronoun per document and let the glossary carry it.

Two Thai registers sit above formal. Royal vocabulary, ราชาศัพท์, applies to the monarchy and uses separate nouns and verbs for the same actions. Monastic vocabulary applies to monks and has its own set. Both are governed by convention and by official guidance, and both need a human editor who works with them regularly. Machine translation should stop at formal, and a translation brief that involves either register should say so before any text is sent.

Each decision above maps to one field on Paxa Translate Lite. The defaults are set for a caller who sends plain text and wants a sensible result; the fields exist so the register can be fixed once and held across every request.

Reference fields bill at 8 credits per thousand characters against 25 for the text itself, which is the rate structure that makes a long style brief affordable to send on every request. The translation guide covers batching and how a glossary is matched.

• Pick the speaker particle, ค่ะ or ครับ, and write it into the brief.
• Pick the pronoun pair for the reader and the company, usually คุณ and เรา.
• Set formality once per surface: formal for money, legal, and errors, casual only for an audience that speaks that way.
• List product names, feature names, and codes in do_not_translate.
• Put every term with a fixed Thai form in the glossary, including the borrowed words you want spelled one way.
• Send the audience and channel in context so a lock-screen notification and a contract are translated differently.
• Test a batch of real strings in the playground; a new account starts with 100 free credits.

The translation page describes the model and its languages. The e-commerce and customer support pages show what a product listing and a support macro look like once the register is set.