Fix the wrong language or incorrect terms

Correct language direction, mixed-language detection, names, brands, and specialist vocabulary without confusing configuration errors with poor audio.

6 min read Updated September 5, 2026 Accuracy

Match the problem to the correct control

Language errors do not all come from the same setting. First decide whether Connect misunderstood the spoken language, translated in the wrong direction, or handled one specific term incorrectly; each symptom has a different correction. Change only one language or context control at a time when comparing the result.

Problem Correct control Do not use first
Everything translates in the wrong direction From, To, Translation Type Pronunciation Dictionary
Mixed-language speech is detected incorrectly Language Hints and Strict Mode Voice Preference
A name or brand is consistently wrong Pronunciation Dictionary Adding many language hints
Industry phrases lose meaning Conversation Context Microphone gain
Random words are missing Audio quality first Dictionary entries for every missed word

Reset the language direction

The From and To selectors define the active translation path. Reset them before adjusting detection aids so that a basic direction error is not hidden behind more advanced settings. Test names, technical terms, and expected accents before the live call so useful context can be prepared.

  • Set From to the language spoken on the source side.
  • Set To to the language the listener should receive.
  • Select Unidirectional, Unidirectional reverse, or Bidirectional to match who needs translation.
  • Use a short sentence with a clear subject and verb; confirm transcription before judging translation.
  • If the direction is still wrong, turn CONNECT-ON off, correct the settings, and begin a fresh test.

Use Language Hints deliberately

Add only languages you genuinely expect to hear. A focused list gives detection a useful boundary; a long speculative list adds ambiguity. Enable Strict Mode when speech must stay within the selected hints, and disable it when unexpected languages may appear. Test names, technical terms, and expected accents before the live call so useful context can be prepared.

Hints are not target languages. From and To define the translation path. Language Hints help Connect identify what may be spoken.

Separate context from pronunciation

Context tells Connect what the conversation is about, while the pronunciation dictionary teaches it how a repeatable name or specialist term should be handled. Use the smallest tool that matches the error. This makes accuracy differences easier to identify and explain. Keep the source language, destination language, and speaking direction aligned with the people in the conversation.

  • Use Conversation Context for a domain, topic, setting, expected speakers, and important terminology.
  • Use a Pronunciation Dictionary for names, products, acronyms, brands, and words that should be spoken a specific way.
  • Keep one context focused on one call type and review entries that conflict.
  • Test the term in a full sentence, because isolated words provide less context.

Rule out an audio problem

If errors move around instead of repeating on the same terms, run How I Sound?, position the microphone correctly, and remove noise or clipping. Context cannot recover speech that was never transcribed clearly. Record the working device names and settings so the same result can be reproduced on the next call.

Configuration is fixed when the source transcription is stable, direction is correct, and the same specialist terms resolve consistently across repeated sentences.

Prepare an accuracy report

Include the exact spoken sentence, displayed transcription, produced translation, expected translation, From/To values, Language Hints, Strict Mode state, and active context or dictionary. Never include confidential customer information. Test names, technical terms, and expected accents before the live call so useful context can be prepared.

Frequently asked questions

These answers address repeatable language errors after microphone quality and the translation direction have been confirmed. If the result remains unclear, record the exact behavior and the conditions under which it occurs. This keeps troubleshooting focused and gives support enough context to reproduce the problem.

Should I add every supported language to Language Hints?

No. Add only the languages that may actually be spoken during the call. A focused list helps detection; a long speculative list can introduce unnecessary ambiguity.

When should Strict Mode be enabled?

Enable it when the conversation must remain within a controlled set of hinted languages. Leave it off when callers may switch unexpectedly to a language that is not in the list.

Why does the pronunciation dictionary not fix random missing words?

The dictionary is intended for repeatable names, brands, acronyms, and specialist terms. Random omissions or changing errors usually point to clipping, noise, microphone position, or an unstable source transcription.

Support

Need help? Get in touch with our Support Team for assistance. Include the calling application, operating system, selected microphone and speaker, translation direction, and the exact step that failed. A short description of the expected result and what happened instead helps the team respond more quickly.

The following articles continue this workflow with setup instructions, troubleshooting checks, and feature-specific guidance. Start with the resource that matches your next task, keep the current configuration available for comparison, and validate each change in a short test call before applying it to a live conversation.