Generative AI
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 Dialogflow Messenger.
Free · No account · Result in ~30s
Dialogflow is Google's building platform and comes in two flavours that differ in almost everything: the older ES with intents, and CX with flows and pages. On your website it usually appears as the df-messenger element. That element has its own title attribute, which is one of the few places you can put a notice before the conversation starts.
We have not yet scanned enough sites where Dialogflow Messenger 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.
www.gstatic.comdialogflow.cloud.google.comnonedf-messengerThe chat-title attribute on the df-messenger element, plus the Default Welcome Intent (ES) or the entry fulfilment of your start page (CX).
First determine whether you run CX or ES; the consoles differ completely.
On CX: open the start page of your main flow and edit the entry fulfilment.
On ES: open Intents and find the Default Welcome Intent.
Put the AI notice in the first response of that step.
Also update the chat-title attribute on the df-messenger element in your HTML.
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 Dialogflow Messenger: Dialogflow CX and ES differ. In CX you set it in the start flow, in ES in the Default Welcome Intent.
Dialogflow Messenger documentation: cloud.google.com
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.
By default it reads something like "Customer service". That is the first text a visitor sees, before any message exists. It is the cheapest possible home for the word AI, and almost nobody uses it that way.
Start the conversation with a parameter or a deeplink and Dialogflow sometimes skips the welcome step. The visitor lands mid-flow having never seen the notice. Test with the exact URL your customers use.
If the same agent sits behind a phone number, the notice has to be audible in the first spoken sentence. Text in chat-title never reaches a caller.
Read the chat-title attribute on the df-messenger element straight out of your page source; that is the first text a visitor sees and a deploy overwrites it easily. Then open your site in an incognito window and click the messenger open with no parameters in the URL. Test once more with exactly the URL you use in campaigns or emails, because a parameter or deeplink can skip the welcome step and drop you mid-flow.
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.
CX: the start page of your main flow. ES: the Default Welcome Intent. You cannot tell them apart in the page source; in the console you can, by the presence of flows and pages.
Then the notice has to be audible in the first spoken sentence. Put it in the entry fulfilment so it comes first regardless of channel.
It is a strong signal because it is visible before the first message, but it is separate from what the agent says. Set both; it costs one line of HTML and one field in the console.
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.