Acme Assist

Customer-facing support chatbot · fictional example

01 · OBSERVED STATE

The AI disclosure appears only after the user has already started the interaction.

Example observation: the launcher says “Ask Acme,” the pre-chat state does not identify the experience as AI, and “AI assistant” appears only in the conversation header after the first message.

02 · EXACT CHANGE

Move the disclosure into the pre-interaction state and keep a persistent AI label in-session.

SUGGESTED PRE-INTERACTION COPY

“Chat with Acme’s AI assistant.”

SUGGESTED FIRST-OPEN SUPPORT COPY

“You’re chatting with an AI assistant. For a person, choose Human support.”

Final wording should be reviewed against the actual product context, applicable accessibility requirements and qualified legal/compliance advice.

03 · DEVELOPER TICKET

No compliance memo translation required.

ChangeExpose AI identity before the first user message and retain a persistent “AI assistant” label during the conversation.SurfaceChat launcher, pre-chat panel and conversation header.AcceptanceOn a clean session, a user can identify the system as AI before sending any message; the identity remains visible after conversation start.AccessibilityDisclosure text is available to keyboard and assistive-technology users and does not rely only on colour/iconography.RegressionVerify desktop + mobile and the human-handoff state.

04 · EVIDENCE TO RETAIN

Leave behind proof that the shipped control exists.

ScreenshotVersioned capture of launcher / pre-chat disclosure before first interaction.ScreenshotConversation header showing persistent AI identity.ReleaseTicket/PR/release reference tying the control to a deployed version.QAAcceptance-test result for first interaction, mobile and accessibility states.

Fix one live AI surface — €190 →

BOUNDARY

TraceNotice turns public product observations and official Article 50 materials into implementation support. It does not certify compliance, determine legal applicability or replace qualified counsel.