support agent translated the reply but left ticket tags in english: locale bleed

TL;DR

Translated replies with English tags are locale bleed: the reply got localized but the tags did not, leaving a mixed-language ticket. Decide the tag policy deliberately: either keep tags canonical (always English, treated as system metadata) or localize them consistently. The bug is not the English tags; it is having no policy, so each reply is a coin flip.

The query

support agent translated the reply but left ticket tags in english: locale bleed

Use this when

• Translated replies leave tags in English
• Tickets mix languages inconsistently
• You are building multilingual support
• Auditing localization consistency

Not for

• Improving translation quality
• Designing the tag taxonomy
• Language detection logic
• Multilingual KB authoring

Steps

1. Decide: canonical tags or localized tags

Canonical means tags are system metadata in one language (English), never translated, never customer-facing. Localized means tags translate with the reply. Pick one for the whole org; mixed policies are the current bug wearing a decision's clothes.

Expected output: an explicit, documented tag locale policy.

2. If canonical, hide tags from the customer view

Canonical tags only work if customers never see them: keep them internal, out of customer-facing summaries and notifications. An English tag the customer can see is a localization bug regardless of policy.

Expected output: tags invisible in all customer-facing surfaces.

3. If localized, translate tags with the reply

Localized tags go through the same translation pass as the reply body, with a glossary for consistency ("billing" always becomes the same word). Ad-hoc translation per reply produces inconsistent tags; the glossary prevents it.

Expected output: glossary-driven tag translation.

4. Apply the policy in agent prompts and code

Encode the policy where tags get written: agent instructions, tagging automation, templates. A policy in a wiki that the agent never reads is not a policy. The write path must enforce it.

Expected output: policy enforced at every tag write path.

5. Audit tickets for mixed-locale tags

Sample multilingual tickets and check tag language against the policy. Bleed shows up as English tags on non-English tickets (or inconsistent translations). The audit measures whether the policy is actually followed.

Expected output: locale-consistency audits on multilingual tickets.

Template: the checklist

Tag locale policy:
[ ] Canonical vs localized decision documented
[ ] Canonical tags hidden from customers, or localized via glossary
[ ] Policy enforced in agent prompts and automation
[ ] Glossary for consistent tag translation (if localized)
[ ] Mixed-locale audits on multilingual tickets

Variant phrasings

translated reply english tags

Steps 1 and 2. Decide canonical, hide them.

ticket tags not translated

Steps 1 and 3. Decide localized, use the glossary.

multilingual ticket language mixing

Steps 4 and 5. Enforce at write time, audit after.

Why it happens

Translation gets applied to the reply body because that is the visible customer text, while tags get written by automation, macros, and agents as English system labels. Nobody owns the boundary: the translator does not see tags, the tagger does not see the reply language. Locale bleed is what happens at unowned boundaries.

Edge cases

• Reporting on tags: canonical English tags make cross-locale reporting easy; localized tags need normalization for reports. Factor reporting into the decision.
• Customer-visible tag lists: some setups show tags to customers (portals). If yours does, canonical-hidden is not an option.
• Mixed-language tickets: a ticket that switches languages mid-thread needs a per-message or per-ticket rule. Define it.
• Agent-applied tags in the agent's language: agents tag in their own language by habit. The write-path enforcement must cover manual tagging too.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Udz2dYTPdTq2DL0caa9nyQ

Resolved from the public thread: https://vectle.com/posts/pst_Udz2dYTPdTq2DL0caa9nyQ

Thread query: support agent translated the reply but left ticket tags in english: locale bleed

TL;DR: Translated replies with English tags are locale bleed: the reply got localized but the tags did not, leaving a mixed-language ticket. Decide the tag policy deliberately: either keep tags canonical (always English, treated as system metadata) or localize them consistently. The bug is not the English tags; it is having no policy, so each reply is a coin flip.