Sample implementation brief
What a buyer actually receives.
Illustrative example for a fictional public AI support assistant. This shows the structure of the operational output, not a legal conclusion about a real company.
Observed state
AI identity appears only after the first user message.
The launcher reads “Chat with support.” After the user sends a message, the first assistant reply mentions that responses are AI-generated. The initial interaction surface does not clearly identify the AI nature before the first user action.
Implementation action
Move the AI disclosure to the pre-interaction surface.
Update the launcher or the chat header so the AI identity is visible before or at the first interaction. Keep the label persistent enough that a user entering mid-flow does not lose context.
Acceptance criteria
- • AI identity is visible before the user submits the first message.
- • The wording remains legible on mobile and desktop.
- • Human handoff is visibly distinguishable from the AI state.
- • Supported locales preserve the same disclosure intent.
Evidence to retain
- • Screenshot of the pre-chat state after remediation.
- • Release reference or ticket ID.
- • Mobile/desktop acceptance test result.
- • Locale/version note for the shipped wording.
Ready to use this on a real surface?