Multilingual Support Response Adapter
Adapt customer support responses for different languages and cultural contexts — going beyond translation to adjust tone, formality, idioms, and expectations for each market.
Prompt Template
You are a multilingual customer support specialist with expertise in cultural communication differences. Adapt the following support response for multiple markets: **Original response (in English):** [paste your English support response here] **Target languages/markets:** [e.g., Spanish (Latin America), German (DACH), Japanese, French (France), Portuguese (Brazil)] **Support channel:** [email / live chat / help center article / social media reply] **Brand tone:** [e.g., casual and friendly, formal and professional, warm and empathetic] **Product/service context:** [brief description of what your company does] **Customer issue type:** [complaint, question, bug report, feature request, billing] For each target market, provide: 1. **Translated and culturally adapted response** — not a literal translation, but a response that feels native 2. **Cultural notes** — key adjustments made and why (formality level, directional phrases, apology style) 3. **Tone calibration** — how the brand tone translates for this culture (e.g., casual in English may need to be semi-formal in Japanese) 4. **Common pitfalls** — phrases or approaches that would feel wrong or offensive in this market 5. **Greeting and sign-off conventions** — appropriate opening and closing for this market and channel Also provide: 6. **Universal template** — a culture-proof template structure that works across all markets with minimal adaptation 7. **Escalation phrases** — how to say "let me escalate this" appropriately in each language/culture
Example Output
Original English Response
"Hey Sarah! Thanks for reaching out. I'm sorry to hear the export feature isn't working for you. I've looked into it and it looks like this is a known issue we're fixing in our next update (expected this Friday). In the meantime, here's a workaround: [steps]. Let me know if you need anything else!"
🇩🇪 German (DACH) Adaptation
Response:
Guten Tag Frau Schmidt,
vielen Dank für Ihre Nachricht. Es tut mir leid, dass die Exportfunktion bei Ihnen nicht wie erwartet funktioniert. Wir haben das Problem identifiziert und arbeiten bereits an einer Lösung, die voraussichtlich am Freitag veröffentlicht wird.
In der Zwischenzeit können Sie folgenden Workaround nutzen: [Schritte].
Bitte zögern Sie nicht, sich erneut zu melden, falls Sie weitere Fragen haben.
Mit freundlichen Grüßen,
[Agent Name]
Cultural notes:
- Shifted from first-name casual ("Hey Sarah!") to formal address ("Frau Schmidt") — German business culture defaults to formal unless the customer uses "du" first
- Added structure and precision — German customers expect clear timelines and factual communication
- Removed exclamation marks and emoji — reads as unprofessional in German support context
**Tone calibration:** English "casual friendly" → German "warm but professional"
Common pitfalls:
- Never use "du" (informal you) unless the customer does first
- Don't over-apologize — German customers prefer solutions over excessive empathy
- Avoid vague timelines like "soon" — give specific dates
🇯🇵 Japanese Adaptation
Response:
[お客様名] 様
お問い合わせいただきありがとうございます。
エクスポート機能に不具合が発生しており、ご不便をおかけして誠に申し訳ございません。
現在、開発チームが修正に取り組んでおり、今週金曜日のアップデートで解消される予定です。
それまでの間、以下の方法で対応いただけますと幸いです：[手順]
その他ご不明点がございましたら、お気軽にお申し付けください。
Cultural notes:
- Formality level significantly higher — Japanese support defaults to keigo (honorific language)
- Apology is more prominent and comes before the explanation — taking responsibility is culturally expected
- "ご不便をおかけして誠に申し訳ございません" (deepest apologies for the inconvenience) is standard, not excessive
Universal Template Structure
1. Culturally appropriate greeting
2. Thank the customer for contacting
3. Acknowledge the issue with appropriate empathy level
4. State what's happening (cause/status)
5. Provide timeline or next step
6. Offer workaround if available
7. Invite further questions
8. Culturally appropriate sign-off
Tips for Best Results
- 💡Never just translate — localize. 'Hey!' is friendly in American English but can feel disrespectful in German or Japanese support contexts.
- 💡Default to the more formal register in each language and let the customer set the tone downward. It's easier to become casual than to recover from being too informal.
- 💡Have native speakers review your adapted templates before going live. AI translation is a great starting point but cultural nuance needs human validation.
- 💡Build a market-specific glossary of your product terms — 'dashboard', 'workspace', and 'pipeline' may not translate directly or may have established local equivalents.
Related Prompts
Customer Complaint Response Template
Write a professional, empathetic customer complaint response that resolves issues and preserves the relationship.
Help Documentation Writer
Write clear, user-friendly help articles and documentation that reduce support tickets and improve self-service.
Support Ticket Triage and Response
Triage incoming support tickets by priority and generate initial responses for common issue types.