SMS and app notification translation within character and template limits
Translates order, payment and offer messages for SMS and app notifications into regional languages within character limits, keeps the variables in registered templates untouched, and flags where a Unicode script shortens the allowed length. Use it when a business sends transactional or promotional messages to customers in several languages.
The output this prompt produced, unedited.
The prompt
Fill in these first
Messages to translate: [paste rows: message type, English text, variables such as {#var#} or {{order_id}}]
Target languages: [e.g. Hindi, Bengali, Telugu]
Limits: [e.g. SMS 160 characters in English and 70 per part in Unicode; notification title 40, body 120]
Registered template rules: [e.g. fixed text must match the approved template exactly; variables only where marked]
Sender name and links: [keep as they are]
Rules for every message
Variables, links, codes and sender names stay unchanged and in a sensible position for the target grammar.
Count characters for the script used and keep within the stated limit.
Transactional messages stay neutral and clear; promotional ones may be warmer but never longer.
Numbers, amounts and times keep the same digits as the English.
If a natural translation is over the limit, give a shorter version and say what was cut.
Output format
| Message type | Language | Translation | Character count | Within limit |
Shortened fallbacks for any message over the limit.
Notes for template registration: which translations are new fixed text that needs approval.
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.