Official-source-backed technical resource

Review white-label chatbot identity settings

Separate customer branding from the factual identity of the AI participant. Includes a free implementation worksheet.

Short answer

Separate customer branding from the factual identity of the AI participant. Define which configuration changes need review and test the rendered customer experience.

Download the blank working record (.md)

When to use this guide

A white-label setting lets a customer replace AI assistant with account specialist without any review warning.

This is a fictional implementation scenario. The procedure below is Article 50 Hub's suggested working method, not a prescribed legal form, a customer result or a claim that every step is an additional statutory requirement.

Review procedure

  1. Inventory configurable names, avatars, identity text and visibility options.

  2. Identify changes that could make the participant appear human or conceal the notice.

  3. Define a review and support process for risky configurations.

  4. Test representative customer configurations and record the exact values used.

What the example review finds

  • A branding change removes the AI identity statement.

  • The preview differs from the customer's published configuration.

Keep these example observations separate from your own results. An unknown or untested state should stay open until the relevant evidence has been inspected.

Fields for your working record

  • Customer configuration

  • Identity field

  • Visibility setting

  • Review rule

  • Published evidence

Use the downloadable blank worksheet linked on this page to connect the observed behavior with the deployed system. Add a reviewer, date, evidence reference, unresolved questions and a next action. The worksheet is editable locally and does not upload your records to Article 50 Hub.

Completion and handoff

Close the task only for the scope actually reviewed. Preserve the result that another authorized reviewer can reproduce, identify the owner of remaining work, and record a retest when the implementation changes. A completed worksheet is not a substitute for the underlying evidence.

Decision boundary

Contractual controls and configuration checks do not settle provider or deployer roles by themselves.

The official references below provide legal or technical context. Resolve applicability and exception questions with the responsible qualified reviewer; use the product's tools to organize implementation work within that assessment.

Official sources

  1. EU AI Act — legal text and contextEUR-Lex
  2. Commission FAQ — transparency obligations and scopeEuropean Commission
  3. Article 50 Service Desk — read with its amendment notice and current Commission guidanceEuropean Commission
  4. W3C — evaluating accessibility and the limits of automated checksW3C WAI

Last reviewed: 2026-09-23. This is technical implementation information, not legal advice.

Share this source-backed guideLinkedInEmail