Voice assistant
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 Vapi (voice).
Free · No account · Result in ~30s
Vapi is used to automate phone calls, inbound and outbound. That makes it the deployment with the widest gap between what you arrange on your website and what the other person actually experiences. A caller does not see your site, your banner or your transparency statement. Everything hangs on the first spoken line.
We have not yet scanned enough sites where Vapi (voice) 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.
api.vapi.aicdn.jsdelivr.netwindow.vapiSDKwindow.Vapi.vapi-btn#vapi-support-btnYour assistant's firstMessage field: the line spoken before the caller says anything.
Open your assistant in the Vapi dashboard or your own config.
Find the firstMessage field.
Put the spoken AI notice there, as the first line of the call.
Does the assistant sit behind an IVR menu? Put the notice in that menu too.
Call the number yourself and listen for the line coming first, including after a transfer.
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 Vapi (voice): If the bot sits behind an IVR menu, put the notice in that menu too. Otherwise the caller only hears it after three choices.
Vapi (voice) documentation: docs.vapi.ai
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.
On an inbound call the caller has context: they rang you. On outbound they do not. That is where the notice matters most and where it is most often forgotten, because the campaign flow sits apart from the assistant config.
A system prompt shapes how the assistant answers, not what is heard first. Without firstMessage the call opens with silence or a generated line that differs every time. Set the notice as fixed text.
If a call transfers to a second assistant, the caller hears a new voice. Put a short notice there too, or it will sound as though a person has taken over.
Call your own number from a device that is not in your system and listen for the notice before you say anything. If an IVR menu sits in front, walk every route to the assistant, because the notice belongs in the menu itself and not only after it. If you also run outbound, put a test number in the campaign and record the call. Record your numbers and assistants in your system inventory, because that is where someone will look later.
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.
Both. On outbound it matters more, because the recipient has no context and did not start the call.
Put it in your AI transparency statement and your system inventory. That is where someone will look when a question comes in.
No. A phone number does not appear in your HTML as an AI system. Our scan only sees what runs on your public page. For telephony this is a manual check.
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.