To translate a WhatsApp message into another language, first check whether your app offers Translate when you long-press the message. Where supported, choose the language and read the translated text in its conversation context. For important decisions, verify the original wording: a translation must keep who is speaking, what they agreed to, what remains uncertain and exactly when something should happen.
People searching for how to translate WhatsApp messages, WhatsApp translate on iPhone or Android, translate a WhatsApp group chat or translate WhatsApp voice notes need to separate text translation from audio transcription. WhatsApp introduced built-in text-message translation in September 2025, but feature and language availability can vary; voice notes may require an additional process. A machine-translated message can help with understanding, not automatically establish consent or certify a binding decision.
This guide shows a practical method for reading and writing multilingual WhatsApp messages, including group conversations, short replies, slang, emoji, timestamps, forwarded text, screenshots and recorded voice notes. The original conversation is the source of truth. Whenever a message affects money, safety, privacy, travel or a deadline, clarity and confirmation matter more than perfect-sounding prose.
Quick answer: use Translate, then check the message’s meaning
Open the conversation, long-press the text message and look for Translate if the feature is available on your supported device. Choose or download the appropriate language when prompted. Read the surrounding messages and confirm critical details directly with the sender if needed. Never assume a translated ‘okay’ settles an earlier question unless you can identify exactly what it answers.
Fifteen principles for translating WhatsApp conversations
How to translate WhatsApp messages on a supported phone
WhatsApp announced built-in message translation on 23 September 2025. Its published instructions describe long-pressing a supported text message, choosing Translate, selecting the source and destination language, and downloading the relevant language when prompted. The launch covered one-to-one chats, groups and Channels, with supported languages and platform availability varying during rollout. Android was also offered an automatic translation option for incoming messages in a chat. Check the current app version and language availability on your device; a person who does not see Translate may not yet have that feature or language pair.
That tool is useful for understanding ordinary incoming text, but it is not a substitute for checking important commitments. If the translated message controls payment, travel, medicine, legal rights or a private disclosure, compare the original with a competent speaker when possible. WhatsApp’s original announcement said its built-in message translation happens on-device. That does not mean a copied conversation uploaded to a different translation service receives the same privacy treatment. See the official WhatsApp message-translation announcement for the features it originally described.
Start by identifying who wrote the message
A message is part of a conversation, not a self-contained instruction manual. Before translating, find its sender, date, preceding turn, intended recipients and whether it is a quotation, reply, forwarded text or newly written instruction. The sentence ‘Yes, that is fine’ means something different when it answers a meeting time, a cancellation question or a request to share photographs. A literal target version cannot repair missing context. If the thread is unclear, translate with a visible qualifier instead of inventing what ‘that’ refers to.
In groups, attribution is even more important. A parent, teacher, organiser and group administrator may all speak about the same activity from different positions. The translator should not turn one person’s suggestion into an official group decision. Preserve the speaker’s name or stable label, the original order and the difference between a direct instruction and a participant’s opinion. Read the target thread from the perspective of someone who never saw the original.
Keep yes, no, maybe and silence separate
Brief chats often convey commitment with tiny words: ‘sure’, ‘okay’, ‘probably’, ‘not yet’, ‘let me check’ or ‘I think so’. Their force depends on tone and context. ‘I might come’ is not confirmation of attendance; ‘I saw your message’ is not agreement to a proposal. Many misunderstandings arise because a translation sounds more decisive than the source. Identify which decision the message makes before selecting a target-language expression.
Silence is not a word waiting to be translated. Missing replies, read receipts and reaction icons may describe what the app displayed, but they do not establish consent to a contract, a photograph or a change of plan. If the conversation lacks an explicit answer, the accurate summary is that an answer has not been provided. Avoid writing a reassuring ‘approved’ merely because no one objected.
Preserve times, dates and time zones
Chat messages often use relative language: ‘tomorrow’, ‘tonight’, ‘next Friday’, ‘after school’ and ‘by six’. The intended meaning depends on when the sender wrote the message and their location. Do not turn a relative date into an absolute date without checking the message timestamp and the relevant local time. A message sent just before midnight in one country may refer to a different calendar day for the reader elsewhere.
When arranging appointments or deliveries, retain the time basis and the difference between arrival, check-in, start and final deadline. A phrase such as ‘before 6 p.m.’ is not the same as ‘at 6 p.m.’ If the chat involves people in several zones, request a confirmed city and time zone rather than silently assuming the reader’s own zone. Keep appointment IDs, meeting links and phone numbers exactly as supplied.
Read emoji and reactions as context, not certainty
An emoji may soften a request, signal warmth, express irony or simply reflect a sender’s habitual style. Its meaning is not universal, and a thumbs-up reaction can be ambiguous in a conversation involving contractual changes or consent. Do not convert a reaction into a formal acceptance unless the participants explicitly treat it that way. Preserve the presence of the symbol where it affects tone, and explain its uncertainty when writing an external summary.
Similarly, laughter markers such as ‘haha’ and playful punctuation may qualify a joke or a complaint. Translate the social effect without inventing new insult, flirting or intimacy. A short message sent between friends may use wording unsuitable for a formal report. When reusing chat material for documentation, label it as a quotation and keep editorial interpretation outside the quoted text.
Understand slang, abbreviations and code-switching
People type quickly, using abbreviations such as ‘brb’, ‘imo’ or shortened local phrases. A message can switch languages midway through a sentence, especially in multilingual families and workplaces. Before replacing a term, determine whether it is a name, a culturally specific expression, a task code or casual shorthand. Expand abbreviations only when their meaning is clear from context. If two interpretations are plausible, a short translator’s note is more reliable than a confident guess.
The target should normally sound like the sender speaking naturally, not like a legal statement. At the same time, slang should not become caricature. Avoid exaggerating a person’s accent or education level. Keep meaningful changes in politeness, social distance and address forms. When a local term has no useful equivalent, retain it and give a compact explanation instead of inventing a strange literal phrase.
Treat forwarded messages and screenshots cautiously
A forwarded message can be genuine text, a partial quotation, a rumour or a copied announcement whose context is missing. Translation does not verify that the original claim is true. Preserve any forwarded-label or source limitation when it matters. A screenshot may omit earlier messages, timestamps or edits, so do not portray it as a complete conversation without evidence.
Images and screenshots may contain text that must be transcribed before it is translated. Keep visible typos or uncertain readings distinct from corrected language. For photographs containing private phone numbers, addresses or faces, use an approved privacy-conscious workflow. Do not post screenshots publicly merely to ask a translation question. If OCR or image translation makes an uncertain word look crisp, verify it against the image before acting on the result.
Voice notes require a separate transcription step
A voice note is audio, not a normal text message. The built-in text-message translation described in WhatsApp’s 2025 announcement should not be presented as a guarantee that every voice note is automatically translated. Depending on device and current features, a user may need an authorised transcription process, followed by translation. Check that the recording is intelligible, identify the speaker and preserve relevant hesitations, negation and timing.
Speech recognition can mistake names, numbers and background voices. A transcript saying ‘fifteen’ when the speaker said ‘fifty’ can change a payment or appointment instruction. Listen again to high-impact segments, request a typed clarification when possible and do not invent the missing word. The voice note may also include sensitive third-party speech; obtain appropriate permission and use a secure workflow before transferring recordings.
Translate requests, commitments and conditions exactly
A chat might ask for a document, promise a callback, reserve a slot or discuss a refund. Mark the actor, action, condition and deadline. ‘Can you send it tomorrow?’ is a request; ‘I will send it tomorrow’ is a commitment; ‘I will send it if the office approves’ is conditional. A natural target sentence must retain that difference. Distinguish advice from orders and preferences from final decisions.
For payment and logistics, keep account details, reference IDs and money amounts unchanged. Translation never authenticates a request for money or an identity claim. A suspicious message can be translated to understand its contents without clicking links or sending personal information. When financial details are critical, confirm them through a separate trusted communication channel.
Keep consent, access and privacy boundaries clear
Group messages may contain requests to share photographs, add participants, forward contact lists or record meetings. Translate the exact permission requested and who is covered. ‘You may send the summary to the team’ does not automatically allow forwarding the full chat to another organisation. ‘Please do not share’ is a prohibition, not a stylistic suggestion. A translation that widens consent can expose someone’s personal data.
Sensitive chats should be handled minimally. If all that needs translation is a delivery time, do not upload an entire unrelated conversation to an external service. Be especially careful with health information, school records, children and account recovery details. Screen captures can reveal phone numbers and group membership even when a highlighted sentence seems harmless. The safest workflow limits sharing to the authorised, necessary content.
Manage group instructions without shifting authority
A group administrator may publish a confirmed schedule while members discuss alternatives. Translate the difference between ‘proposal’, ‘please vote’, ‘confirmed by the organiser’ and ‘cancelled’. A fluent rewrite that moves a participant’s preference into the administrator’s voice can cause missed events. Use clear sender names, dates and a separate status summary when permitted.
If a group thread is long, construct a chronological table of proposals, approvals, outstanding questions and final instructions. Do not delete disagreements simply to make the summary easy to read. A final plan should be linked to the message that authorised it. If no one issued a final confirmation, report that the plan is still awaiting confirmation.
Check spelling of names, locations and addresses
Names and street labels can resemble ordinary words in one language. A venue’s official name should usually be kept in its recognised form, perhaps with a transliteration or explanatory gloss. Do not replace an official MRT station, school or hotel name with a translated description that a map app cannot find. Preserve building numbers, postal codes, room numbers and distinguishing unit identifiers.
A correct translation should let a recipient follow the original directions to the same destination. If the source says ‘Gate B’, the target should not say ‘main entrance’ unless that is verified. Address translation and address formatting are distinct tasks. Place names may have established forms in the target language, but practical navigation should remain tied to exact identifiers.
Separate translation from a diplomatic rewrite
Sometimes the sender wants their message translated for delivery; other times they ask for a more polite or professional version. These are different commissions. An accurate translation preserves directness, annoyance, hesitation and courtesy without inventing abuse or promises. A diplomatic rewrite may adjust tone, but it should be labelled as an edited version and approved by the sender.
If you need to reply in a language you do not know, start with a simple factual sentence and ask a competent reader to check it when the stakes are high. Avoid complicated humour, idioms and ambiguous negation. A message can be warm without obscuring who will do what. For sensitive topics, offer a back-translation or plain-language summary so the sender can confirm the intended commitment.
Build an audit trail for consequential conversations
For ordinary social chat, formal documentation is unnecessary. For an international business handover, a complaint, a school permission question or a delivery dispute, retain the original message, timestamp, sender and reviewed target text in a secure authorised record. Note whether translation was automatic, human reviewed or supplemented with an explanatory note. A later reader should be able to distinguish quoted evidence from the translator’s summary.
Do not treat a machine translation as a certified transcript or legal proof merely because it sounds polished. Mark uncertain names, dates, voice-note words and cultural terms. A short decision log of high-risk choices makes follow-up easier and avoids the temptation to overwrite history with a revised interpretation after the event.
Use a practical two-pass review
First review meaning: actors, tense, negation, dates, amounts, conditions, consent and the exact state of decisions. Then review naturalness: register, flow, politeness, idioms and readability on the actual phone screen. This order matters because a fluent but inaccurate sentence may be harder to spot. Reading the translated thread without the original tests whether the conversation still makes sense.
Finally, perform an action test. Ask what a recipient would do next based on the target alone. Would they turn up at the same time, share the same material, pay the same amount and understand the same permissions as the original reader? Where the answer differs, repair the translation before sending it. Not every message needs this level of review, but important ones do.
Thirty worked examples: what a real chat reader could misunderstand
The following examples are illustrative English-language source scenarios. In a real translation, the target-language choices must be tested in their specific cultural and conversational context. The purpose of each example is to identify a meaning distinction that a quick fluent rewrite can easily erase.
1. A provisional invitation
Message context: ‘I might be able to join on Friday; I’ll confirm after lunch.’
What to preserve: The translated version must not tell the group the sender will definitely attend. Preserve both uncertainty and the promised future confirmation. The correct next action is to wait for an explicit reply, not to count the person as confirmed.
2. A response that answers a different question
Message context: ‘Okay’ follows ‘Did you see the document?’ rather than ‘Will you approve it?’
What to preserve: A reader might incorrectly treat the reply as approval. Restore the surrounding question and preserve the limited acknowledgement. For an external summary, say the message confirms receipt only if that is genuinely what it does.
3. A changed meeting time
Message context: ‘Not 4:30 — the call is now 5:30.’
What to preserve: Negation and corrected time carry the main information. Do not delete the old time without indicating that a change was made when the conversation’s history matters. The final action is to join at the confirmed new time.
4. A phone number with a country code
Message context: A contact shares ‘+65 6123 4567 ext 208’ as an illustrative formatted number.
What to preserve: Do not translate plus signs, dialling codes or extension digits as words that change the number. Retain the identifier and explain the extension only if needed. Translation cannot verify that the number actually belongs to the claimed person.
5. A message about a place nickname
Message context: ‘Meet at the old library side entrance.’
What to preserve: The phrase may be familiar only to members of one group. Preserve it and request a confirmed map pin or official address before creating a clearer direction. Do not choose the nearest library or an entrance based on guesswork.
6. A repeated ‘please’ expressing urgency
Message context: ‘Please, please reply before noon.’
What to preserve: The repetition may indicate urgency rather than formal politeness. Translate the actual deadline and urgency without making it threatening. The reader should understand that a prompt response is requested, not that failure automatically produces an unstated penalty.
7. A joking insult between friends
Message context: A familiar pair exchanges a teasing term and laughing emojis.
What to preserve: A literal strong insult may sound hostile in a target culture. Preserve playful register if context supports it, or explain the uncertainty. Do not invent a closer relationship, escalate hostility or rewrite the message as a formal complaint.
8. A parent group rumour
Message context: ‘Someone said tomorrow’s lesson is cancelled, but I haven’t checked.’
What to preserve: Preserve hearsay and lack of verification. A target that states ‘Tomorrow’s lesson is cancelled’ transforms a rumour into an official notice. The practical next step is confirmation from the teacher or organiser.
9. A refund request
Message context: ‘Could you check whether a refund is possible?’
What to preserve: The customer is asking about eligibility, not accepting a refund offer. Keep the question and conditional wording. Do not translate it as ‘please process the approved refund’, which asserts a decision that does not exist.
10. A conditional work commitment
Message context: ‘I’ll deliver the draft by Tuesday if legal approves the wording.’
What to preserve: Preserve the dependency. Removing ‘if’ creates an unconditional deadline; replacing legal approval with the sender’s own preference changes authority. The recipient should know what is pending.
11. An emoji mistaken for formal consent
Message context: A person reacts with a thumbs-up after someone proposes posting group photographs.
What to preserve: A reaction is context-sensitive and may not be adequate consent for publication. Preserve the visible reaction without labelling it explicit approval. Request clear permission through the appropriate channel before sharing personal images.
12. A message received during an overnight time-zone change
Message context: ‘See you tomorrow at 9’ is sent from one country just before midnight.
What to preserve: The reader may be in another calendar day and time zone. Keep the message date visible and confirm the location-based time. Do not silently decide that ‘tomorrow’ refers to the reader’s local date.
13. A voice note with uncertain quantities
Message context: An audio message mentions ‘fifteen boxes’, but automatic transcription suggests ‘fifty boxes’.
What to preserve: Re-listen and ask the speaker to type the number before placing an order. The translator should not pick the more plausible quantity. Preserve the uncertainty in any interim summary.
14. A screenshot missing the prior line
Message context: A cropped chat image shows ‘Yes, go ahead’ but not the request it answered.
What to preserve: Do not assume which action was approved. Translate the visible phrase and mark missing context. For consequential interpretation, seek the complete thread or a clarification rather than guessing the omitted question.
15. A forwarded health claim
Message context: A forwarded message recommends an unverified treatment and attributes it to a hospital.
What to preserve: Translation does not authenticate the hospital or the claim. Preserve the fact that the content is forwarded and do not present it as medical advice. Direct users toward verified sources before acting on health information.
16. A group poll still open
Message context: The organiser says ‘Vote by Thursday; we’ll announce the final plan later.’
What to preserve: Translate the voting deadline and pending decision. Do not convert the leading option into the confirmed choice. A group participant should know they still need to vote and wait for the announcement.
17. A message stating nonpermission
Message context: ‘Please do not share my phone number outside this group.’
What to preserve: Keep the prohibition and scope. A target such as ‘prefer not to share’ may sound optional and weaken a privacy boundary. Readers should know they are not authorised to forward the contact detail.
18. A teacher’s tentative schedule
Message context: ‘We hope to finish by 6, but collection may be later.’
What to preserve: The message sets an estimate, not a guaranteed release time. Preserve the possibility of delay. Do not instruct families to assume 6 p.m. is fixed.
19. An abbreviation with two meanings
Message context: ‘I’ll send the PR shortly’ appears in a work group with both press releases and pull requests.
What to preserve: The abbreviation is ambiguous. Read the project context or ask the sender. If unresolved, retain the abbreviation with a note rather than expanding it as the wrong work item.
20. A sentence with a double negative
Message context: ‘I don’t think we shouldn’t go’ appears in a hurried message.
What to preserve: The source may be awkward or self-contradictory. Do not smooth it into a confident yes or no without clarification. A translator can flag the ambiguity and ask a simple follow-up question about the intended decision.
21. A quoted message inside a reply
Message context: A participant forwards a manager’s instruction and then writes, ‘I disagree with this.’
What to preserve: Keep the quoted instruction distinct from the participant’s response. Otherwise the target may attribute the manager’s words to the critic or mistake the disagreement for the official policy.
22. A code-switched family term
Message context: The sender uses a family-language title in an otherwise English message.
What to preserve: Translate the relational function, not a stereotyped equivalent. Preserve the original form if it carries identity or respect that a generic aunt/uncle label would distort. An explanatory gloss can help new readers.
23. A complaint softened into neutral language
Message context: ‘I am really upset that my parcel hasn’t arrived’ becomes ‘I have a delivery question’.
What to preserve: That rewrite erases the expressed dissatisfaction. Preserve the complaint and the underlying delivery issue in a respectful target register, without exaggerating blame or promising the recipient is at fault.
24. A remote work handover
Message context: ‘Please review the first page; I’ll handle the figures.’
What to preserve: Keep division of work intact. A careless translation that reverses responsibilities can cause duplicate effort or leave the figures unchecked. Write the target so each person knows the specific next action.
25. A payment message that could be fraudulent
Message context: ‘Send the deposit to this new account now; the old one is closed.’
What to preserve: Translate the instruction to understand it, but do not treat translation as authenticity verification. Confirm the account change through a previously trusted channel before transferring money or replying with account data.
26. A meeting link with punctuation
Message context: The sender pastes a URL containing symbols and says ‘Use this link at 10’.
What to preserve: Protect the literal URL and confirm what ’10’ means. Do not insert translated characters into the link or assume morning versus evening. A clickable-looking target string is not useful if the destination breaks.
27. A disappearing message quoted later
Message context: A participant summarizes something they remember from a disappearing-message conversation.
What to preserve: Do not present the recollection as a verbatim archival transcript. Label it as a participant’s recollection where necessary; a translation cannot recover unavailable original text.
28. A message marked ‘edited’
Message context: The sender changes ‘Tuesday’ to ‘Thursday’ in an edited message.
What to preserve: A target reader may rely on an earlier copied version. Retain the latest approved wording and document the correction when the schedule matters. Do not quietly mix two versions as if they were one unchanged instruction.
29. A group member leaves before a decision
Message context: A participant votes for a plan, leaves the group, and a later message changes the arrangements.
What to preserve: Do not assume they received the later update or approved the new plan. A translated summary should distinguish who was informed at each stage, without inventing receipt.
30. A friendly but noncommittal closing
Message context: ‘Sounds good, we’ll see’ closes a discussion about a possible dinner.
What to preserve: In some contexts this is encouragement, not a firm booking. Preserve its tentative status. If a restaurant reservation is needed, ask for a concrete date, party size and confirmation rather than relying on the translated closing.
Step-by-step workflow for a multilingual chat
1. Identify the source. Confirm whether the material is a typed message, screenshot, forwarded passage or voice note. Keep enough surrounding context to understand short replies. Record sender and timestamp where relevant. For sensitive material, work with permission and expose only necessary content.
2. Identify the action. Mark the question, request, promise, estimate, opinion or final decision. Underline numbers, time references, negation, conditions and personal-data boundaries. Do not begin by decorating the target sentence; begin by knowing what the reader must understand.
3. Translate naturally. Use the app’s built-in translation when available, or an approved alternative. Preserve meaning, speaker, register, code-switching where important and exact data tokens. A short explanation is acceptable when a cultural expression is impossible to convey in one phrase; an invented certainty is not.
4. Check important details. Compare messages about money, meeting times, permission, refunds, schedules and safety against the source. If a voice note or screenshot is unclear, seek a fresh typed clarification. Do not answer an ambiguous question on the sender’s behalf.
5. Send a confirmation when necessary. A reliable multilingual reply repeats the operational facts in plain language: ‘To confirm, the meeting is Thursday at 5:30 p.m. your time, and no payment is due yet—is that correct?’ Adjust the facts to the real situation. The purpose is not to sound formal; it is to prevent two people acting on different interpretations.
Practice exercises
The yes/no context challenge
Write five mini-conversations in which the answer is only ‘yes’, ‘okay’ or a thumbs-up. Change the question each time. Give the answers to a translator with and without the preceding question; compare interpretations. This shows why message translation requires a thread, not just a standalone bubble.
The voice-note number check
Record a harmless fictional voice note containing a date, two numbers and a proper name. Produce a draft transcript, translate it and ask a second listener to check the exact words. Any mismatch should be corrected in the transcript before target-language polishing. This prevents speech-recognition errors from being hidden inside fluent writing.
The group-decision ledger
Use an imaginary group discussing three possible event times. Mark each person’s proposal, vote and final administrator confirmation. Translate a summary that keeps the difference between the most popular suggestion and the approved arrangement. Ask a reader whether they would arrive at the right time and whether any participant’s consent was assumed.
The privacy-boundary test
Prepare three sample messages: permission to share a summary, prohibition on forwarding a photograph and a request to provide a private phone number. Translate them and have a reviewer underline exactly what is and is not allowed. If the reader grants broader access than the original, the translation fails.
The urgency ladder
Translate a set of messages using ‘whenever you can’, ‘by Friday’, ‘as soon as possible’, ‘before noon’ and ‘only after approval’. Ask another reader to arrange them by obligation and time certainty. The target phrases should preserve their different degrees of urgency and conditionality.
The date-across-time-zones test
Imagine two colleagues in different time zones exchanging a message at 11:45 p.m. about ‘tomorrow morning’. Identify the sender’s timestamp, location and intended appointment zone before translating a concrete date. Ask both readers to state the same meeting instant. Do not silently anchor tomorrow to the translator’s location.
Frequently asked questions
How do I translate a WhatsApp message on iPhone or Android?
In supported WhatsApp versions and language pairs, long-press a text message and select Translate. Choose the source and target language if prompted. Availability may depend on platform and rollout; verify current support in WhatsApp’s settings or help information. For important messages, review the result.
Does WhatsApp translate group chats?
WhatsApp’s 2025 announcement included translation for one-to-one chats, groups and Channel updates. The precise availability and supported languages can change. Check the feature on your device rather than assuming every group language is supported.
Does translating a WhatsApp text also translate voice notes?
Not necessarily. Voice notes are audio and may require a separate permitted transcription and translation workflow. Check current app features, verify words and numbers by listening, and respect the participants’ privacy.
Can automatic translation miss sarcasm or slang?
Yes. Slang, irony, references to earlier messages and emoji can be context dependent. Revisit the original and the surrounding thread when a phrase seems unusually strong, confusing or consequential.
Is copying chats into another translation app safe?
Not automatically. Review the receiving app’s privacy practices and your authority to share the content. Built-in on-device translation and uploading private messages to an external service are different data-handling choices.
Should a message translation keep spelling mistakes?
For informal reading, a natural correction may help, but documentary, disciplinary or legal uses may require a faithful record of source errors and ambiguity. Label editorial corrections clearly when they could affect interpretation.
Can I use a translation as evidence of consent?
Translation can help a reader understand a message, but it does not turn silence, emoji or vague phrases into valid consent. For consequential permission, seek explicit confirmation by an appropriate method.
How should names, dates and phone numbers be handled?
Keep exact identifiers stable; use an established name form where appropriate and verify ambiguous relative dates or time zones. Do not guess missing digits or locations.
What is the best way to reply in another language?
Write a short, factual message, preserve the intended action and deadline, and have it checked if the subject is important. A simple question requesting confirmation is safer than an elaborate idiomatic sentence that changes the decision.
Final translation checklist
Check the sender, original text, source version, date, time zone, reply relationship, group authority, negation, yes/no strength, promises, numbers, URLs, phone numbers, emoji context, nicknames, slang, privacy, consent, screenshots, voice-note transcription and the recipient’s next action. If any consequential point remains ambiguous, ask rather than guessing. A successful translation helps two people understand each other without adding agreement, accusation or certainty that the conversation did not contain.
Continue learning: Master Art of Translation · Customer Support Messages · Interview Transcripts · WhatsApp’s message-translation announcement.