Skip to content

Translate a customer email between Greek and English with cultural notes

← Use cases Operations

Translate a customer email between Greek and English with cultural notes

A complaint arrives in Greek and the case needs to escalate to a non-Greek-speaking senior in Frankfurt. Or the reverse — a London supplier sends an English contract that needs to land in front of Athens legal. Claude translates both ways and flags the phrases that don't carry across. Audience: beginner · ~15 min · 6 steps

You'll end up with

A markdown file with the original on the left and the translation on the right, plus a "notes" section flagging phrases where Claude is uncertain or where literal translation would mislead.

Before you start, you need
  • Nothing — Claude will invent a realistic Greek customer complaint email to practise on. (Once you trust the loop, swap in real anonymised correspondence — names, IBANs, account numbers stripped first.)
  • Claude Code installed and a terminal open (see Day 1)

Imagine NBG wildly operates across borders. Most of the time, a written translation isn’t a hard linguistic problem — it’s a context problem. Google Translate gives you a word-for-word version that’s grammatically fine and tonally wrong. The Athens-Frankfurt case escalation reads as flat or rude in the target language; the London supplier’s “by EOB Friday” lands in Greek inboxes as ambiguous.

This use case treats translation as a structured task: original on the left, target on the right, notes on what didn’t carry across on the bottom. The notes are where the value lives.

Compliance check before you start. Customer correspondence is internal-confidential. If you’re translating a complaint, strip the customer’s name, IBAN, and any account numbers before pasting into Claude — same posture as the “empathic reply” use case. Translating a contract is different: confirm with your line manager whether the document classification permits AI-assisted handling. When in doubt, ask before you paste.

Step 01

Build the workspace

Open the .

Press ⌘+Space, type “Terminal”, and press Enter.

Open the Start menu (press the Windows key), type “Ubuntu”, and press Enter. If you don’t see Ubuntu listed, install WSL first.

In Ubuntu, ~/Desktop is a folder inside ’s Linux home (/home/<your-Linux-username>/Desktop) — not the Windows desktop you see in File Explorer at C:\Users\...\Desktop. That’s fine: the files are real and Claude can read and write them. Anywhere this use case says “open in Finder / File Explorer”, run explorer.exe . from your Ubuntu terminal — Windows opens that exact WSL folder in Explorer.

Type each line:

mkdir -p ~/Desktop/claude-lab/translate-complaint
cd ~/Desktop/claude-lab/translate-complaint
claude --dangerously-skip-permissions
  • mkdir -p ~/Desktop/claude-lab/translate-complaint — make a folder inside claude-lab on your Desktop (-p creates claude-lab too if it’s not there yet — it’s the one home for all hub use cases).
  • cd ~/Desktop/claude-lab/translate-complaint — move into it.
  • claude --dangerously-skip-permissions — start here. The flag stops Claude you for permission on every file write — safe in a fresh, dedicated folder like this one. (If you’d rather see every prompt for your first run, just type claude — same thing, more interruptions.)

The cursor is now Claude’s.

Step 02

Ask Claude to invent a realistic Greek complaint

You don’t have a real Greek email to hand and you don’t need one. Tell Claude:

Create a file called source.md in this folder. Write a realistic synthetic complaint email in Greek (~180 words) that a long-standing NBG retail customer might send. The complaint: their mortgage statement for May arrived showing a higher monthly payment than agreed, the contact-centre couldn’t explain it on the phone, and they’re now worried it’s a covert rate change.

Tone in Greek: formal-but-frustrated. Use phrases a real customer would use — including at least two formal Greek constructions that don’t translate cleanly to English (the kind of thing where the literal translation loses tone). Use placeholders [CUSTOMER NAME] and [ACCOUNT] instead of inventing personal data.

Sign off with the formal Greek closing convention (Με εκτίμηση,).

No real names, no real IBANs.

Claude writes the file straight away. The Greek text now lives in source.md.

That’s the small surprise: Claude can generate the input document, not just process it. When you do this on real customer correspondence, the only thing that changes is what’s in source.md.

Step 03

Brief Claude with the *purpose* of the translation

A literal translation is rarely what you want. Tell Claude who reads this, why they’re reading it, and what they need to do with it.

Create a file called context.md. Put these 5 lines inside it:

Source language: Greek
Target language: English (UK)
Reader: a non-Greek-speaking senior risk officer in Frankfurt
Reader's purpose: decide whether to escalate this complaint to legal in the next 24 hours
Tone needed: formal but warm — must convey the customer's emotional state accurately without sounding sensationalist

Claude writes the file straight away.

The “tone needed” line is the one that separates good translation from mechanical translation. Spend a minute on it.

Step 04

Ask for the structured translation

Send this to Claude:

Read source.md and context.md.

Produce translation.md with three sections, exactly in this order:

Section 1 — Side by side. A two-column table. Left column: the original Greek paragraph. Right column: the English translation. One row per paragraph in the original.

Section 2 — Translation notes. Bullet list of phrases where any of the following applied:

  • The literal translation would mislead the reader about tone or intent
  • The Greek used an idiom or formal register that doesn’t have a clean English equivalent
  • A word has two plausible English translations and you picked one — say which and why
  • The customer expressed something culturally specific (e.g. addressing the bank as την Τράπεζα — capitalised, almost personified — which loses force in English)

Each note: the Greek phrase, the English you chose, one sentence on the trade-off.

Section 3 — One-line summary in the target language. Three sentences in English summarising what the customer is unhappy about, what they want, and what the bank’s stance currently is — designed to give the Frankfurt risk officer the picture in 30 seconds before they read the full translation.

Do not soften emotional language. If the customer is angry, the translation should read as angry. The Frankfurt reader needs the real signal, not a polite version of it.

Press Enter. Translation + notes for a one-page email takes 30–60 seconds.

Step 05

Cross-check the notes, then send

Ask Claude to show you what it wrote:

Show me translation.md.

Section 2 — the notes — is where the value is. Read it carefully. For each note:

  • Does the trade-off Claude flagged actually match how the Greek read to you?
  • Are there idioms or culturally specific phrases Claude didn’t flag that you would have?

If you spot a missed nuance, tell Claude:

The phrase “Δεν περιμένα κάτι τέτοιο από σας” — your literal translation “I didn’t expect this from you” loses the implication that the customer’s relationship with the bank is now damaged, not just disappointed. Flag this in the notes and adjust the English to “I didn’t expect this kind of treatment from you” or similar.

Iterate until the notes feel honest.

Make Claude prove nothing got lost

You can judge nuance; completeness is checkable. Paste:

Verify your own translation. (1) Count the paragraphs in source.md and the rows in the side-by-side table — they must match; show me both counts. (2) Translate your English version back to Greek — without looking at the original — then compare that back-translation to source.md and list every place where the meaning drifted, however slightly. (3) For each drift, either fix the English or add a translation note explaining why the drift is the right trade-off.

The back-translation test is the oldest trick in professional translation QA, and Claude can run it on itself in one . Drift it finds is drift the Frankfurt reader would have inherited silently.

In a real cross-border thread you’d paste translation.md into Teams or Outlook for the Frankfurt senior, with the Section 3 summary as the first paragraph. We’re pretending here — the file on your Desktop is the deliverable.

The pattern works in either direction (English → Greek or Greek → English) and for any document type — contracts, internal memos, technical specifications. The structure (side-by-side, notes, one-line summary) stays. Only context.md changes.

Your reputation as the person who “handles the cross-border cases well” is built on getting the notes right — not on getting the translation perfect. Most colleagues won’t notice a perfect translation; they’ll notice when a nuance got flagged that they would otherwise have missed.

Save your translation rules in CLAUDE.md

The three-section structure (side-by-side, translation notes, one-line summary) and your standards for what counts as a worth-flagging nuance don’t change between documents. Save them as CLAUDE.md:

Create a CLAUDE.md in this folder. Put in it my stable translation rules:

  • Output in three sections in this order: (1) two-column side-by-side table, one row per source paragraph; (2) translation notes — flag literal translations that would mislead, untranslatable idioms/register, words with two plausible English equivalents, and culturally specific phrases (e.g. Greek capitalised την Τράπεζα almost personifying the bank); (3) one-paragraph summary in the target language for the reader who reads first and skims the rest
  • Don’t soften emotional language — if the source is angry, the translation reads angry
  • Notes are where the value is. A translation without flagged trade-offs is suspect

CLAUDE.md is the magic filename reads automatically when you start claude in a folder containing it. Next document: copy this into a new folder, drop in the source, write a short per-document context.md (target language, reader, purpose, tone), run claude --dangerously-skip-permissions. Your structure and standards are already loaded.

Step 06

Level up — nuance notes that appear where you need them

Optional: the notes section is the value, but it lives at the bottom of the file while the reader’s eyes are on the table. One fixes the geography:

Read translation.md. Build a single self-contained file translation.html that I can open by double-clicking — no server, no internet, no external libraries. Two-column side-by-side layout, Greek left, English right, comfortable to read (generous line height — Greek text needs it). Every phrase that has a translation note gets a dotted underline — hovering over it (or tapping, on a tablet) shows the note as a small tooltip right there. The three-sentence summary pinned at the top in a highlighted box. Accent colour #007a8a.

Now the Frankfurt reader sees “I didn’t expect this kind of treatment from you”, notices the dotted underline, hovers — and learns in place that the Greek implies a damaged relationship, not mere disappointment. The nuance arrives exactly when it’s relevant instead of in a footnote they never reached.

The pattern to remember — any output Claude can produce as text, it can also produce as a small interactive page. The upgrade prompt is always the same shape: “turn this into a single self-contained interactive HTML file I can open by double-clicking.” It works on every use case in this hub.

Next use case →

Capture how a colleague does a manual process so you can hand it off

Someone on the team is the only person who knows how the month-end reconciliation actually works. They're going on holiday. Interview them on Teams (recorded transcript), then ask Claude to turn that transcript into a step-by-step runbook anyone on the team could follow.

Open it → Back to all 15 use cases