Chat widget
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 Crisp.
Free · No account · Result in ~30s
Crisp is popular with smaller European teams and has one property that works out well for Article 50: the welcome message also appears in the teaser next to the launcher, so before anyone opens the chat. That makes Crisp one of the few widgets where a single field covers both the moment before and after opening.
We have not yet scanned enough sites where Crisp 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.
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.
client.crisp.chatclient.relay.crisp.chatwindow.$crispwindow.CRISP_WEBSITE_ID#crisp-chatbox.crisp-clientSettings, Website settings, Chatbox, Welcome message. Crisp supports per-language text, so fill in every language you serve.
Open Crisp and go to Settings, Website settings.
Pick your website and open the Chatbox tab.
Find the welcome message and enter the AI notice.
Repeat for every language in the list you serve.
Running your own bot via the API or Crisp Bot? Edit the first scenario message too.
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 Crisp: Crisp also shows the welcome message in the teaser next to the launcher, exactly where the notice does the most work.
Crisp documentation: help.crisp.chat
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.
Crisp picks the text from the visitor's browser language. Fill in English only and a Dutch visitor sees an empty or default message. On Crisp this is the most common cause of a low score on an otherwise tidy site.
Anyone wiring Crisp to their own model sends messages through the API. Those messages ignore the chatbox settings entirely, so the notice belongs in the first message your integration sends as well.
The teaser is the strongest part of Crisp for this purpose, but it is often disabled for feeling pushy. With it off, only the post-open message remains and you need a second signal, such as the banner.
Switch your browser language to each language you filled in on Crisp and reload your site in an incognito window. Crisp picks its text from the browser language, so this is the only way to see what a German or English visitor actually reads. First check whether the teaser appears next to the launcher and carries the notice, then open the chatbox for the full welcome message. If a custom integration sends the first reply, test a real conversation too.
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.
Put the sentence in the first message your bot sends, not just in the chatbox settings. API messages bypass those settings and are what the visitor actually reads.
The notice has to be understandable to the visitor. If you serve NL and EN, set it in both. Crisp makes that easy: every language field has its own welcome text.
The teaser sits visibly on the page before the first message, which is stronger than text that only appears after opening. Our scanner weighs a notice beside the launcher higher than one on a linked page.
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.