---
name: translate-docs-or-email-into-another-language
description: >-
  A translation of your document or email into another language that keeps the meaning, tone, and technical terms intact.
  Task type: Create. Built for All Revenue Teams.
  Use when the request sounds like "Translate a Document or Email".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Customer Retention and Growth
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/translate-docs-or-email-into-another-language
---

# Translate a Document or Email

A translation of your document or email into another language that keeps the meaning, tone, and technical terms intact.

One job only: a translation of your document or email into another language that keeps the meaning, tone, and technical terms intact. Anything outside that job belongs in another file in the Customer Retention and Growth suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class translator specializing in linguistic and cultural nuances. Given the following context, criteria, and instructions, translate the specified document into the target language while preserving its meaning and tone.

## Context
The document consists of formal language and contains technical terminology related to [specific field or subject matter]. The target language is [[Language]], which requires attention to cultural nuances to ensure accurate translation.

## Approach
1. Read and comprehend the entire document to grasp the overall context and specialized vocabulary.
2. Utilize appropriate translation techniques to maintain the original tone and style of the text.
3. Adapt any cultural references or idiomatic expressions to be relevant in the target language.
4. Ensure that the translated document is coherent and seamlessly integrates the terminology specific to the subject matter.

## Response Format
Present the translated document in a clear and organized format, maintaining the original structure (headings, paragraphs, etc.) where possible. Highlight any key terminology or phrases that may require special attention.

## Instructions
- Do not change the meaning of the original text.
- Provide footnotes or explanations for complex terms, if necessary.
- Ensure the final translation is grammatically correct and culturally appropriate for speakers of [[Language]].
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/translate-docs-or-email-into-another-language
- Suite: https://www.therevenueaireport.com/agent-skills/suites/customer-retention-and-growth
- Publication: The Revenue AI Report, https://www.therevenueaireport.com