Fin occasionally inserts English words or foreign characters into Hebrew replies. How can this be prevented? | Community
Skip to main content
Answered

Fin occasionally inserts English words or foreign characters into Hebrew replies. How can this be prevented?

  • May 6, 2026 8:13 AM UTC
  • 12 replies
  • 753 views

Forum|alt.badge.img+2

Hi everyone,

We’re using Fin in Hebrew, but we keep seeing cases where Fin adds random English words inside Hebrew replies, even when those words do not appear in our Help Center articles or snippets.

We also had a more serious case where Fin inserted Japanese/Chinese-looking characters into a Hebrew customer-facing reply.

We already added clear Guidance telling Fin to reply fully in Hebrew and avoid English unless it is a brand name, URL, product name, or a required term. The issue still happens.

Intercom Support suggested using Guidance and mentioned the multilingual glossary, but also clarified that the glossary does not apply to AI-generated replies.

Has anyone using Fin in Hebrew or another non-English language found a reliable way to prevent this?

Is this something Guidance can actually solve, or is this a current limitation of Fin?

This is affecting customer trust, so any practical advice would be appreciated.

Best answer by Peter Nixon

I got a msg this week saying our issue of random arabic words in our english replies had been fixed. Not sure if this would have fixed the issue for all languages or just some...

View original

12 replies

Forum|alt.badge.img+2
  • Connector
  • May 7, 2026 1:03 PM UTC

We see this issue a lot with teams running Fin in non-English markets, particularly Hebrew, Arabic, and Thai. 

Some things to try:

  • If your articles were machine-translated from English they might still contain some English brand names, technical terms, or stray phrases.  The LLM can interpret that as a signal that it is ok to mix languages in its responses.
  • If you have content already in Hebrew then turning off real-time translation will help - this prevents it from attempting to do its own translation (https://www.intercom.com/help/en/articles/8322387-set-up-fin-ai-agent-s-multilingual-support)
  • Not quite applicable to the problem you are seeing but you can set a language override i.e. on the contact you can explicitly say what language to reply in and avoid it trying to detect (https://www.intercom.com/help/en/articles/9423842-enforce-the-language-of-the-messenger-fin-ai-agent-and-workflows-for-specific-users)
  • In the Guidance name the specific things you do not want it to do; explicitly forbidding things is stronger (e.g. “Do not insert English words, transliterations, or any non-Hebrew characters (including Latin or CJK characters”)

 


Forum|alt.badge.img+2

We see this issue a lot with teams running Fin in non-English markets, particularly Hebrew, Arabic, and Thai. 

Some things to try:

  • If your articles were machine-translated from English they might still contain some English brand names, technical terms, or stray phrases.  The LLM can interpret that as a signal that it is ok to mix languages in its responses.
  • If you have content already in Hebrew then turning off real-time translation will help - this prevents it from attempting to do its own translation (https://www.intercom.com/help/en/articles/8322387-set-up-fin-ai-agent-s-multilingual-support)
  • Not quite applicable to the problem you are seeing but you can set a language override i.e. on the contact you can explicitly say what language to reply in and avoid it trying to detect (https://www.intercom.com/help/en/articles/9423842-enforce-the-language-of-the-messenger-fin-ai-agent-and-workflows-for-specific-users)
  • In the Guidance name the specific things you do not want it to do; explicitly forbidding things is stronger (e.g. “Do not insert English words, transliterations, or any non-Hebrew characters (including Latin or CJK characters”)

 

 

We’ll test adding another guidance with a specific rule not to include any CJK characters. Thank you!


Forum|alt.badge.img+7

Hi ​@בן גטניו and ​@Jon Vaughan , Seán here from the Fin technical support team 👋

I see ​@בן גטניו  already has a conversation already made with our support team and a ticket is with our engineers, I will update here when there is a fix for this!


Peter Nixon
Forum|alt.badge.img+3
  • Active User
  • May 27, 2026 12:28 AM UTC

I’ve just seen this for the first time with some of our replies as well. Our replies are in English but some random arabic words have been inserted.


Forum|alt.badge.img+1
  • Connector
  • Aug 27, 2026 9:33 AM UTC

Currently experiencing the same with Swedish text where EN words are being inserted into the chat because we have RTT enabled. 1) RTT needs to respect the user’s language and stay within.  2) Fin needs to link up with the Glossary feature to align with product terminology in foreign languages. 


Peter Nixon
Forum|alt.badge.img+3
  • Active User
  • Answer
  • Aug 27, 2026 11:19 PM UTC

I got a msg this week saying our issue of random arabic words in our english replies had been fixed. Not sure if this would have fixed the issue for all languages or just some...


Forum|alt.badge.img+7

Thanks ​@Peter Nixon great to hear. ​@Saad, ​@בן גטניו , ​@Jon Vaughan if there are new examples of any language please let me know here and I can raise it with our team. Thanks for your patience on this one 🙏


Forum|alt.badge.img+1
  • Connector
  • Sep 14, 2026 9:47 AM UTC

Thanks ​@Peter Nixon great to hear. ​@Saad, ​@בן גטניו , ​@Jon Vaughan if there are new examples of any language please let me know here and I can raise it with our team. Thanks for your patience on this one 🙏

Thanks ​@Sean Meade Forum Support Lead this still continues to happen to us for SV language where RTT picks up from the EN HC some bolded words in English and inserts them into a Swedish translated chat. I had to resort to a workaround by adding a disclaimer into fin’s intro that some words may appear in English. Happy to explain more in a DM if needed.

 


Forum|alt.badge.img+3

Hey ​@Saad i’ve created a conversation for our Support team to investigate this in more detail. Thanks for flagging. 


Forum|alt.badge.img+3
  • Active User
  • Oct 27, 2026 2:53 PM UTC

It's concerning that clear language guidance didn't reliably prevent the issue. How does your team now identify incorrect or unexpected responses across live conversations, rather than relying only on customers to report them?


Forum|alt.badge.img+2

​@Parvesh 

Honestly, we don’t currently have a reliable way to proactively detect these issues across live conversations. We still occasionally come across replies from Fin containing unexpected English words or Chinese/Japanese-looking characters.

That said, we’ve noticed this happening much less often with the latest version of Fin. It seems to have improved, though the issue hasn’t disappeared entirely.


Forum|alt.badge.img+3
  • Active User
  • Nov 3, 2026 5:41 PM UTC

​@בן גטניו 

Thanks for being candid about this. I think the gap between noticing that an issue has become less frequent and actually having visibility into individual conversations is important.

 

This is one of the problems I've been working on with ChatShield. It helps teams review conversations across their Intercom workspace, including both Fin and human support agents, and flags potentially risky responses for human review.

 

It doesn't replace Fin's safeguards or fix the underlying generation issue, but it can provide an additional layer of conversation monitoring.

 

ChatShield is available on the Intercom App Store, and there's a 7-day free trial if your team would find it useful to test.