Chat widget

Is your Freshchat chatbot EU AI Act ready?

Article 50 asks that visitors know they are talking to an AI. Scan your site free, and read below exactly where that notice goes in Freshchat.

Free · No account · Result in ~30s

Freshchat and Article 50, briefly

Freshchat is part of the Freshworks suite and, with Freddy, carries an AI layer that generates answers from your knowledge base. In practice Freshchat often runs on the website and inside a mobile app with the same bot behind it. A banner on your site then covers only half your users.

What our scans found on Freshchat sites

We have not yet scanned enough sites where Freshchat was the first widget we detected to say anything meaningful here. As soon as the sample is large enough it will appear, counts included. We would rather publish nothing than a percentage based on two sites.

How we detect Freshchat

Our scanner looks for these signals on your public page. Two independent signals are required for a match, so a blog post that merely names the vendor does not count.

Script hosts
wchat.freshchat.comwchat.eu.freshchat.com
JS globals
window.fcWidget
DOM selectors
#fc_frame#freshworks-container

Where the AI notice goes in Freshchat

Admin, Chat or Widget, Welcome message, or the first step of your Freddy bot. With an active bot that first step wins over the widget setting.

  1. 1

    Open Freshchat and go to Admin, Widget.

  2. 2

    Find the widget welcome message setting.

  3. 3

    Then go to Bots and open the bot that replies first.

  4. 4

    Edit the first step or the Freddy opening message.

  5. 5

    Publish the bot and test on web and in the app.

The sentence you paste

You are chatting with an AI assistant, not a person.

The welcome message only appears after opening. The banner snippet from the Compliance Kit covers the moment before that with a single script tag, and your AI transparency statement covers the question that comes after.

Watch out with Freshchat: Freddy AI generates answers. Beyond the interaction notice, that is a reason to start thinking about marking AI output.

Freshchat documentation: support.freshchat.com

What goes wrong most often with Freshchat

Three mistakes we run into on sites that did set the notice. Each one costs points in the scan, and each one takes minutes to fix.

Checking that it works in Freshchat

First find in your page source which widget id actually loads and compare it with the id you edited in Freshchat; with several brands or regions those are often not the same. Then open your site in an incognito window and start a conversation. If the bot also runs in your mobile app, run the same test on a fresh install of that app, because the banner on your website is invisible there and the notice has to come from the bot message.

After that you can scan again. Our scan looks at the same public page a visitor does, so what you see in an incognito window is roughly what we see.

Two dates

  • 2 August 2026: the transparency duty on interaction (Article 50) applies.
  • 2 December 2026: marking AI-generated content becomes relevant.

Frequently asked questions

Freddy or a regular bot?

Both fall under the same requirement. With Freddy the notice matters most, because the answers are generated and the wording differs per conversation.

We run Freshchat in an app.

The same applies in the app. The banner is web only; in-app you set the notice in the first message of the bot.

Can you see whether Freddy is enabled?

No. From the outside we see the Freshchat widget and the text on your page, not which AI features are active in your account. That is why we report detection, not a verdict.

Running another widget as well?

Fix this for Freshchat in about 15 minutes

The Compliance Kit contains a copy-paste disclosure banner (NL/EN/DE), an AI transparency statement, an AI system inventory and a step-by-step guide per widget.

See the Compliance Kit (€149)

Technical compliance tooling and templates. Not legal advice.