Keep names and reference codes intact across languages
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Hypothetical scenario: a customer sends a name in Arabic, a product label in French and a reference code containing a leading zero. The reply reads naturally in English, but the name has been romanised, the label has been translated and the zero has disappeared. The message is understandable; it is no longer easy to reconcile with the original.
To preserve names and reference numbers in translated messages, separate text that carries meaning from text that carries identity. Translate the surrounding explanation. Copy identity-bearing values exactly, and place any translation or transliteration beside them as a labelled explanation—not as a replacement.
The practical control is a protected-text checklist: a short record of the original value, its source, permitted explanations and unresolved questions. Use it during preparation and review, regardless of which translation tool supports the conversation.
1. Decide which text must survive unchanged
Protect a value when someone will need to match it against the original conversation, a label, a document or an existing record. The test is not whether the text can be translated. It is whether changing it would make that match less reliable.
- Customer names: preserve the supplied spelling, script, accents, spacing and order. Do not infer which part is a family name.
- Product labels: preserve the name or variant used to identify a specific item. A descriptive explanation can sit alongside it.
- Address fragments: preserve the supplied building, street or unit text when referring back to it. This does not establish that the address is valid or complete.
- Reference codes: preserve every letter, digit, separator and leading zero. Treat the code as text, not as a quantity.
Not every noun needs protection. A sentence explaining that a parcel is delayed can usually be translated normally. A product name embedded in that sentence may need to remain exact. Mark the smallest complete span needed for identification, including punctuation that belongs to it.
Record where each value came from. A customer-typed message, a reading of a photograph and a staff member’s earlier transcription carry different uncertainty. Copying an uncertain transcription accurately does not resolve its uncertainty.
2. Separate an exact value from a reading aid
A transliteration represents text in another script. A translation explains meaning. Neither should silently become the authoritative value used for reconciliation.
Hypothetical example: a customer supplies the name ليلى منصور. A team member adds Layla Mansour to help an English-speaking colleague read it. That spelling may be useful, but it is not necessarily the customer’s preferred Latin-script spelling.
A clear internal note would say: “Customer-supplied name: ليلى منصور. Provisional Latin-script reading: Layla Mansour; customer preference not confirmed.” Ask for a preferred spelling only if the task needs one. Otherwise, the original may be sufficient.
For a product, “Product label: Crème Nuit — Éclat. English explanation: night cream” distinguishes the exact label from its general description. Sending only “night cream” loses the distinction between that item and other night creams.
This adds some visual length, but keeps an explanation from looking like an official replacement. Avoid presenting several competing spellings without labels. If the source itself is unclear, ask the customer rather than silently repairing it.
3. Use this filled protected-text checklist
Fictional worked example: all names, labels, address details and references below are hypothetical. A customer has asked an English-speaking support team about an item in a multilingual message. The team needs to acknowledge the request without changing its identifying details.
Reuse these fields for each protected value: original, source and status, permitted explanation, prohibited alterations, and confirmation message. Keep the checklist with the working conversation material available to authorised reviewers.
Customer name
- Original:
ليلى منصور. - Source and status: customer’s typed message; preferred Latin-script spelling unknown.
- Permitted explanation:
Layla Mansouras a provisional reading aid, labelled unconfirmed. - Prohibited alterations: replacing the original with the reading aid, reversing name order, or marking the provisional spelling as customer-confirmed.
- Confirmation message, if needed: “You wrote your name as ليلى منصور. If you would like us to use a Latin-script version, please type your preferred spelling.”
Product label
- Original:
Crème Nuit — Éclat. - Source and status: customer’s typed description; not independently checked against packaging.
- Permitted explanation: “night cream” beside the exact label.
- Prohibited alterations: removing accents, substituting an English product name, shortening it to
Éclat, or changing the dash inside the protected value. - Confirmation message if disputed: “You entered Crème Nuit — Éclat. Is that the full label on the item, or is there another variant name we should include?”
Address fragment
- Original:
عمارة النور، شقة ٠٤. - Source and status: customer’s typed message; completeness and deliverability have not been assessed.
- Permitted explanation: “building name and apartment detail” as a description of the fragment’s role.
- Prohibited alterations: replacing the original with a transliteration, changing
٠٤to4, or adding a presumed street or city. - Confirmation message: “We have this address detail as you sent it: عمارة النور، شقة ٠٤. Is this the text you want us to retain?”
Reference code
- Original:
RF-00O7-B/24. - Source and status: customer’s typed message; the letter
Oneeds clarification before a reference-dependent action because the team cannot reconcile the supplied code. - Permitted explanation: “your reference code” outside the protected value.
- Prohibited alterations: removing leading zeros, changing case, replacing the slash, or substituting
0forOwithout confirmation. - Confirmation message: “In RF-00O7-B/24, is the character immediately before 7 the letter O or the digit zero? You can also paste the full reference again.”
This checklist preserves what was supplied without declaring every value correct. The status field shows which details can be used as supplied and which need clarification before the next action.
4. Build and check the reply in two passes
First, identify and copy the protected values from their sources. Second, translate the surrounding sentences while leaving those values untouched. Before sending, compare each protected span with its source rather than relying on memory.
Using the hypothetical checklist, the acknowledgement could read:
Thank you. We have recorded the product label as Crème Nuit — Éclat and the reference as RF-00O7-B/24. Before we use the reference for the next step, could you confirm whether the character immediately before 7 is the letter O or the digit zero?
The reply includes only the details needed for this task. It does not repeat the customer’s name or address fragment merely because they appear in the checklist. A neutral greeting also avoids introducing an unnecessary alternate spelling.
Hypothetical continuation: the customer replies, “It is zero. The reference is RF-0007-B/24.” The reviewer records that new value as customer-confirmed, retains the earlier message as context, and prepares the next reply using RF-0007-B/24. The change is now traceable to confirmation rather than an editorial guess.
Keep labels close to their values. A separate line for a reference can help inspection, especially when a message combines scripts with different reading directions. Check the actual draft’s display; do not insert spaces or punctuation inside a code simply to make it look tidier.
5. Ask questions that resolve the actual uncertainty
“Please confirm your details” is too broad when only one character is unclear. It asks the customer to repeat work and may produce another version without explaining what changed.
Use a narrow question that states what you received and what you need to know. These additional messages are hypothetical examples:
- Uncertain image reading: “I read the name in the image as Maëlle Duret, but the accent is unclear. Could you type the name as you want us to use it?”
- Preferred form of address: “How would you like us to address you?” This avoids guessing which part of a name to use.
- Conflicting versions: “Your earlier message says Maëlle Duret; the later message says Maelle Duret. Which spelling should we use for this request?”
Translate the surrounding question into the customer’s language while retaining the values being compared. If an alternate spelling is genuinely needed, distinguish a preference for greetings from a requirement to match an existing record. One answer may not settle both questions.
6. Catch changes that fluent translation can hide
Review protected spans independently from grammar and tone. A natural-sounding message can still contain a reconciliation error.
- Accents disappear:
MaëllebecomesMaelle. The result looks familiar but differs from the supplied spelling. - Codes become numbers: leading zeros disappear, or separators are reformatted.
- Similar characters are substituted: the letter
Obecomes zero, or visually similar characters from different scripts are treated as interchangeable. - Labels become descriptions: a specific product variant becomes a generic category.
- Address fragments are expanded: a reviewer adds an assumed location or rewrites a building name.
- Old text overrides a correction: the next reply reuses the first spelling after the customer has confirmed another.
Copying is preferable to retyping, but check the selection boundaries: a copied span can still omit a suffix, separator or final digit. If a display prevents reliable character inspection, request a clearer typed value instead of marking the check complete.
7. Recover with an explicit correction
If an altered value has already been sent, identify the specific change. Was it copied incorrectly, presented as an authoritative translation, or taken from an outdated draft?
- Return to the source. Locate the customer-supplied value and any later confirmation.
- Resolve uncertainty. Restore a clear original; ask a focused question if the intended value remains ambiguous.
- Send an explicit correction identifying the altered value. State what changed and provide the corrected value. Do not rely on silently editing an earlier message.
- Update the working checklist. Mark the value to use next, its confirmation status and the reason for the change.
- Check the handoff. Make sure the next reviewer receives the correction, not just the faulty reply.
Hypothetical correction for a separate copying error: “Our previous reply omitted a zero from your reference. The reference you supplied is AB-0042. Please use that full value when referring to this request.”
If the intended value remains unresolved, the correction should identify the error without presenting an unconfirmed replacement as verified. Route difficult script or spelling questions to a person able to review them.
8. Review a small batch before making this routine
A hypothetical pilot could examine ten multilingual drafts that the reviewer is authorised to access. Count the protected spans, unintended changes, unresolved readings and clearly recorded confirmations. Also note whether corrections reached the next reviewer.
Separate preservation errors from source uncertainty. A code copied exactly but awaiting character clarification needs customer confirmation. A code that lost a zero during translation needs a better preparation or review step. Combining them into one error count hides which action would help.
Give the reviewer the filled checklist as a model and compare each final protected span with its source. The observable outcome is specific: identifying values either match their sources or have traceable, confirmed replacements; unresolved readings remain visibly pending. This checks the conversation’s reliability without treating fluency as proof of accuracy.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications