English Leakage in Translated Sales Apps (and How We Fixed It)

What "English leakage" means

You set your app to Spanish. The home page translates. The menu translates. Then you click into a settings panel and the Save button is still in English. That random English string is English leakage — and most translated apps are full of it.

It happens because most translation systems wrap maybe 40% of UI strings and leave the rest hardcoded. Users feel it instantly. The illusion of a translated app cracks.

How we audit it

ClosersForge ships an internal Translation QA dashboard that we use ourselves and that admins on team accounts can run. It does four things:

1. Completion percentage per language across every namespace (common, navigation, auth, dashboard, gamification, sparring, pitchPractice, voicePractice, courses, scriptBuilder, followUp, closerIQ, certifications, playbooks, globalSalesMode, bilingualPractice, bossBattles, team, admin, errors, notifications).

2. English leakage scanner — scans the live page for ASCII-only strings while the app is set to a non-English language and flags them.

3. Test language mode — temporarily switches the whole app to a beta language to feel real-world usage.

4. RTL preview — flips the entire layout right-to-left for Arabic and Hebrew so we can catch broken alignment, mirrored icons, and misaligned chat bubbles.

How we fixed our worst leaks

When we first scanned ClosersForge with the leakage scanner, we found:

• 200+ route files with hardcoded English
• Modals (especially confirm dialogs) untranslated
• Toast notifications untranslated
• Empty states untranslated
• Form validation errors untranslated
• Chart axis labels untranslated

We expanded the dictionaries to 30+ namespaces and wired the highest-traffic surfaces first: nav, auth, profile, pitch practice, sparring, gamification, usage limits.

Missing-key registry

Every time the app tries to render a translation that doesn't exist, we log it to an in-memory registry. The QA dashboard surfaces it live. As reps use the app in beta languages, missing keys show up immediately and we fix them in the next deploy.

Safe fallback for beta languages

For our 11 beta languages we use a tiered fallback:

1. Static dictionary entry (best)

2. Cached AI translation of the English source

3. English source string (last resort, with a beta badge near it)

Users never see a broken key like `gamification.xp.gained`. They see English with a beta badge — clean, honest, useful.

What this means for you as a rep

When you switch ClosersForge to Spanish, the core flows feel native. When you switch to one of the 11 beta languages, you'll see a beta badge on the language and English will sometimes appear in less-trafficked surfaces — and we're closing those gaps weekly.

More on our localization stack

• Global Sales Mode
• Localized sales training
• Translate sales pitches without losing persuasion
• AI sales coach in your language
• Get coaching in a different language than practice

FAQ

Can I run the leakage scanner on my own pages?

If you're a team admin, yes — open Translation QA.

How fast do beta-language gaps get fixed?

Top-traffic surfaces are usually patched within a week of being logged.

Does English fallback feel jarring?

We pair it with a beta badge so users understand they're on a partially-translated language.

What about RTL languages like Arabic?

Full layout flip. The QA dashboard previews it before we ship.

→ Open Translation QA (admin)

→ Set your language preferences

→ Read about Global Sales Mode