Support macro library translation that keeps tone and policy exact
Translates a support team's saved replies into new languages so the policy terms, numbers, placeholders and links stay exact while the tone sounds like a real local agent, and flags any line that reads harsher or softer than the original. Use it when a support team starts answering customers in Hindi, Tamil, Arabic, Spanish or another language.
The output this prompt produced, unedited.
The prompt
Constraints first
Placeholders such as {{customer_name}}, {{order_id}} and [Link] are copied exactly and never translated.
Numbers, dates, amounts, time limits and policy terms keep the same meaning and value.
The reply sounds like a polite local agent, not a word-for-word copy.
If a sentence could read as rude or as a promise in the target language, flag it.
Inputs
Target languages and the script for each: [e.g. Hindi in Devanagari, Tamil in Tamil script]
Macros: [paste rows: macro name, English text]
Policy terms with approved translations, if any: [paste, or none]
Formality level: [e.g. formal "you" forms, never casual]
Channel and length limits: [e.g. WhatsApp, under 500 characters]
Output format
| Macro name | English | Translation | Characters | Tone note |, for each language.
A glossary: | English term | Translation used | Notes |
A two-line check list for a native speaker reviewer before the macros go live.
support macro translationcustomer service translationcanned responses translationmultilingual supporthelpdesk localisationsaved replies
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.