---
title: "Customer support message translator"
type: "skill"
url: "https://useaiblocks.com/skills/customer-support-message-translator"
updated: "2026-10-28"
first_published: "2026-10-25"
job: "Help your customers"
tested: true
licence: "MIT"
source: "https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/translate-ticket"
instructions: "https://useaiblocks.com/skills/customer-support-message-translator/SKILL.md"
---

# Customer support message translator

> Translate a customer message into English and get a reply draft in their language, with an English check. Works for pasted text or a Gorgias ticket.

Paste a customer message, or give a Gorgias ticket number. Your AI finds the language, translates the message and flags unclear phrases. You get an English version, a reply in the customer's language, and what that reply says in English.

Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28

## Links

- Page: https://useaiblocks.com/skills/customer-support-message-translator
- Instructions (SKILL.md): https://useaiblocks.com/skills/customer-support-message-translator/SKILL.md
- All files (zip): https://useaiblocks.com/skills/customer-support-message-translator.zip
- JSON version: https://useaiblocks.com/skills/customer-support-message-translator.json
- In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get customer-support-message-translator"

## What you give it

- The customer message, pasted as text.
- A Gorgias ticket number, if you want your AI to fetch the message (optional).
- Verified product facts to use in the reply (optional).

## What you get

- The language and formality level of the message.
- A clear English translation with notes on unclear phrases.
- A reply draft in the customer's language.
- An English version of that reply, so you can check it.

## Example: what goes in and what comes out

### What goes in

- The customer message, pasted as text
- Or a Gorgias ticket number
- Verified product facts for the reply (optional)

### Before you start

- For a Gorgias ticket number: Composio CLI with your Gorgias account connected, and an AI that can run commands
- Pasted text needs none of this

### What comes out

- **Translation header**: The language and dialect your AI detected, how sure it is, and whether the message is formal or informal.
- **Customer's Message (Original)**: The customer's text, quoted as it was written.
- **English Translation**: A clear English version that keeps the customer's tone and intent.
- **Cultural Notes**: Sayings, context or unclear phrases the support person should know, with possible meanings.
- **Draft Reply**: A reply in the customer's language, with the right formal or informal address.
- **English Back-Translation**: What the reply says in English, so you can check it before sending.

## Use it when

- A customer writes in a language you do not speak.
- A message has a saying or slang you cannot read.
- You want a reply that sounds natural and matches the customer's level of formality.
- You need to check what a reply says in English before you send it.

## Skip it when

- You need legal, refund or contract wording: have a person who knows the language and the policy write and check it.
- You need a fully translated help center or long documents: use a professional translation service or a human translator.
- You only want a reply in English: write it yourself or ask your AI for a plain reply, no translation needed.

## How to use it

1. Open Claude, ChatGPT or Gemini and paste the skill text, or add the skill folder if your AI reads files.
2. Paste the customer message. Add any product facts the reply must include.
3. To use a Gorgias ticket number instead, your AI must run commands, and Composio CLI must be linked to your Gorgias account.
4. Read the English translation and cultural notes first.
5. Check the English back-translation against the reply draft. Fix anything that does not match your facts.
6. Have a person who knows the language review any reply about refunds, legal or contract terms before you send it.

## What to do next

- [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer): Support ticket help article writer

## Sources and credits

- From Composio: https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/translate-ticket, shared under the MIT licence (original name: translate-ticket).
- [translate-ticket skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/translate-ticket), Composio: Copied under the MIT licence. We gave it a plain name. We added Before you start and After this sections that link to other AI Blocks steps.

## Instructions (SKILL.md)

## Translate Ticket

You are a multilingual support specialist. Detect the language of a customer message, translate it to English for the agent, then draft a reply in the customer's language.

The user's input is: $ARGUMENTS

<!-- needs: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. -->
### Before you start
Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait.

**What you need** (use your own material or the linked skill):
- **Customer words** (yours): reviews, testimonials, support tickets, survey answers or call transcripts. Export them or paste them in.

**Makes it better (optional):**
- **A tool connection** (yours): an AI connected to an outside tool or service, such as an MCP server.

How to start:
1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name.
2. **Check what's missing.** Look for customer words, a tool connection. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps.
3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it.

**Tools that do this best:**
- **Gorgias for ticket lookup; pasted text also works:** Live lookups need Composio CLI access and connected accounts for these services.
<!-- /needs -->

### Workflow

#### If a [Gorgias](https://composio.dev/toolkits/gorgias) ticket ID is provided:
1. Run `composio search "get ticket details from Gorgias"` in Bash
2. Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}'` in Bash. If the CLI reports the toolkit is not connected, ask the user to run `composio link gorgias` and retry.
3. Parse the JSON output and extract the customer's messages

#### If raw text is pasted:
Use it directly.

### Process

#### Step 1: Language Detection
Identify the language and dialect if possible (e.g., Brazilian Portuguese vs European Portuguese, Latin American Spanish vs Castilian).

#### Step 2: Translate to English
Provide a clear English translation that:
- Preserves the customer's tone and intent
- Notes any idioms or cultural context that doesn't translate directly
- Flags ambiguous phrases with possible interpretations

#### Step 3: Draft reply in customer's language
Write a support response in the customer's language that:
- Uses natural, native-sounding phrasing (not machine-translate-quality)
- Matches the formality level of the customer's message
- Uses the correct formal/informal address (e.g., usted vs tu, vous vs tu, Sie vs du)

### Output

```
## Translation

**Detected language:** [Language] ([confidence])
**Formality level:** [Formal/Informal/Mixed]

### Customer's Message (Original)
> [original text]

### English Translation
> [translation]

### Cultural Notes
- [Any context an English-speaking agent should know]

### Draft Reply in [Language]
---
[Reply in customer's language]
---

### English Back-Translation
> [So the agent knows exactly what the reply says]
```

<!-- next: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. -->
### After this
When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:
- The [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer). It takes the draft.
If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.
<!-- /next -->
