Is your Botpress chatbot EU AI Act ready?

Botpress and Article 50, briefly

Botpress is a developer platform, not a ready-made widget. You build the flow yourself, attach a language model and embed the webchat with a config object in your own page. That gives you full control over the first message, and it also makes you the one accountable for that first line being there.

What our scans found on Botpress sites

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

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.botpress.cloudfiles.bpcontent.cloudmessaging.botpress.cloud

JS globals

window.botpressWebChatwindow.botpress

DOM selectors

#bp-web-widget-container.bpw-widget-btn#bp-widget

Where the AI notice goes in Botpress

The first node of your main flow, plus the webchat config, so it shows before the first message arrives.

1. 1

   Open your bot in Botpress Studio.

2. 2

   Go to the main flow and select the start node.

3. 3

   Add a text message card with the AI notice as the first card.

4. 4

   Open the webchat config and set the same sentence in the description or opening message.

5. 5

   Republish the bot; the embed loads the published version.

Botpress documentation: botpress.com

What goes wrong most often with Botpress

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.

• The notice lives in the system prompt

  Instructing the model to introduce itself as an AI is no guarantee that it will, and the visitor never reads that prompt anyway. Put the sentence in the flow as a fixed text message, not as an instruction to the model.

• Bot published, embed still on the old version

  The webchat embed points at a specific bot version. We regularly see an updated flow in Studio while the site still loads the previous build. Always verify in an incognito window after publishing.

• Only the notice, no plan for labelling

  Botpress bots generate text. From 2 December 2026 marking AI-generated content becomes relevant. Handle only the interaction notice now and you will redo this work in a year. Write the approach into your AI transparency statement.

Checking that it works in Botpress

First check in your HTML which bot id and which version the webchat embed loads, and compare that with the version you just published. Then open your site in an incognito window and start a conversation: the fixed text message from your first node should appear before the model generates anything. Next, ask whether you are talking to a person and read the answer; with a generative bot that is the only way to see what your system prompt actually does with it.

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?

• Tidio and Article 50
• Drift and Article 50
• LiveChat and Article 50