Module: Work with multilingual

14 of 18 Pages

Translation prompt anatomy and templates

✖
Copy to clipboard

A great prompt reads like a compact brief and is easy for AIRA to navigate. Another benefit of keeping your prompts scannable and specific is that your editors and marketing colleagues can easily understand it, and reuse it for their projects, too.

Include the following elements in short sentences or bullet points, for clarity:

  • Audience and intent. Who will read the translated text, and why.
  • Tone of voice (ToV). If you have a strong brand tone of voice, use it. If not, define a tone that is most suitable to the business vertical your company operates in. For example, clear, compliant, reassuring ToV for banking, empathetic, evidence-based for health and life sciences, precise and technical for manufacturing and so on.
  • Formality and address. Specify formal or informal address and neutral wording based on your vertical, or where regional variants may differ.
  • Terminology. Provide a mini-glossary with preferred translations for the individual target languages.
  • Do-not-translate (DNT). Add brand names, product names, acronyms, model numbers.
  • Style and formatting rules. Specify headline case, sentence length, forbidden phrases, CTA patterns.
  • SEO constraints (if relevant). Set title length, meta description limits, keyword intent, and Open Graph copy expectations.
  • Quality bar. Ask for clarity, cultural appropriateness, and consistency across the whole page or item.

Keep prompts under ~200–300 words. Use bullet lists. Put the most critical constraints first and make them stand out with an exclamation mark.

Quick-start translation prompt templates by vertical

The following examples show how a few lines of targeted guidance can dramatically improve translation quality. We include four often-occurring verticals because they cover distinct tones and limitations. Banking is especially useful for hands-on practice in our Kbank demo website, while the others help you model scenarios you may meet later.

For users new to AIRA translations, we recommend using these prompts as demo material. You can either use them when translating already existing pages and content items in Kbank, or you can create new content items in the demo environment and translate those, building on what you already learned and practicing multiple skills at once.

As you gain more confidence in your ability to prompt AIRA to give you the results you want, you can adapt these demo prompts to your own use case, and use them on real projects.

Banking/Financial

Since our Kbank demo website is modeled as a fictitious banking institution, you can easily test out the demo scenario. Feel free to experiment with your prompt, and work iteratively to translate your way to best outcomes.

  • Use cases: Translating product pages, rate explanations, or campaign copy.
  • Protected terms (examples): Kbank, TravelGuard, SmartSave Junior, K-ID.
  • Avoid: Promising guaranteed outcomes.
  • Risky: Informal slang that undermines trust.

Example ad-hoc prompt:

  • Audience: Parents considering a child savings product.
  • Tone: Clear, compliant, reassuring. Avoid hype.
  • Formality: Neutral to formal.
  • Terminology: “savings account” → [TL term]; “interest rate” → [TL term].
  • DNT: Kbank, SmartSave Junior, K-ID.
  • Style: Short sentences, no exclamation marks, no guarantees. Align with regulatory-safe wording.
  • SEO: Title ≤ 60 chars; meta ≤ 155; include the concept of “child savings” in natural phrasing.
  • Quality: Ensure cultural appropriateness, consistent terms across page, and correct local date and number formats.

Healthcare

Experiment with this sample prompt in the demo environment or use it as inspiration to ideate translation prompts tailored to your specific projects.

Use cases: Service pages, patient guidance, educational content.
Protected terms: Khealth, CarePath, names of devices or programs.
DNT examples: COVID-19, MRI, CT, “stat”, WHO.
Template highlights: Empathetic and precise tone, no medical diagnosis or advice, plain-language explanations, consistent use of medical acronyms.

Example prompt:

  • Audience: Prospective patients and caregivers.
  • Tone: Empathetic, evidence-based, plain language.
  • Formality: Neutral.
  • DNT: Khealth, CarePath, COVID-19, MRI, CT, WHO.
  • Terminology: Use standard clinical terms accepted in the target language; avoid colloquialisms.
  • Style: Short paragraphs, active voice, no medical advice; encourage seeking professional guidance.
  • Quality: Ensure sensitivity, remove idioms, and keep reading level accessible to a general audience.

Coffee/hospitality

Use cases: Menu items, product cards, campaign banners, blog posts.
Protected terms: Dancing Goat, GoatRewards, specific blend names.
Template highlights: Friendly and upbeat, foodie vocabulary, maintain product names, adapt idioms, keep CTA playful but clear.

Example prompt:

  • Audience: Coffee lovers and café visitors.
  • Tone: Friendly, upbeat, sensory.
  • Formality: Informal but respectful.
  • DNT: Dancing Goat, GoatRewards, [blend names].
  • Style: Keep product names as-is; adapt idioms to natural local expressions; limit to one CTA per section.
  • SEO: Include coffee style or origin naturally in meta text when relevant.

Manufacturing

Use cases: Product specs, safety instructions, installation guides.
Protected terms: Product codes, model numbers.
Template highlights: Precise, technical tone; unit consistency; keep model numbers and tolerances exact; avoid marketing fluff.

Example prompt:

  • Audience: Engineers and procurement.
  • Tone: Precise, technical, concise.
  • Formality: Formal.
  • DNT: All model numbers and codes.
  • Terminology: Use industry-standard terms in the target language; avoid synonyms once chosen.
  • Style: Numbered steps, consistent units, no adjectives implying performance beyond specs.
  • Quality: Check all measurements, units, and safety statements for clarity and consistency.

14 of 18