Is your Voiceflow chatbot EU AI Act ready?

Voiceflow and Article 50, briefly

Voiceflow gets used for two very different channels: a chat widget on your site and a spoken assistant on the phone. Same flow, two completely different notices. A text banner never reaches a caller, and a spoken line does nothing for a chat visitor. Run both channels and you have to handle it twice.

What our scans found on Voiceflow sites

We have not yet scanned enough sites where Voiceflow 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 Voiceflow

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

cdn.voiceflow.comgeneral-runtime.voiceflow.com

JS globals

window.voiceflow

DOM selectors

#voiceflow-chat

Where the AI notice goes in Voiceflow

A speak or text step as the very first step of your flow, plus the assistant description in the webchat embed config.

1. 1

   Open your project in Voiceflow and go to the start of your main flow.

2. 2

   Add a speak or text step as the very first step.

3. 3

   Put the AI notice in it, matched to the channel.

4. 4

   Open the webchat embed settings and fill in the assistant description.

5. 5

   Publish and test both channels separately.

Voiceflow documentation: docs.voiceflow.com

What goes wrong most often with Voiceflow

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.

• One notice for two channels

  Text that works fine in chat gets read out on the phone as a long sentence nobody waits for. Write a short spoken variant and a readable text variant in the same flow, behind a channel condition.

• The notice sits after intent recognition

  Flows often start with a step that classifies the user's question. Put the notice before it, or the visitor hears or reads it only after they have already asked.

• The typing indicator treated as a notice

  Three animated dots say nothing about AI. Our scanner only counts text that states in words that this is an AI system. That is also exactly what a visitor needs in order to decide anything.

Checking that it works in Voiceflow

Test each channel separately, because one test says nothing about the other. For chat: open the embed in an incognito window and read the first message. For voice: call or start the assistant yourself and listen for the notice before you have said anything, and check that it stays audible if you start talking immediately. Also confirm the notice does not arrive only after intent recognition; you notice that when you have to ask a question before anything about AI is said.

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.

Frequently asked questions

Running another widget as well?

• Drift and Article 50
• LiveChat and Article 50
• Tawk.to and Article 50