Fictional example · format preview

Product-surface evidence pack

Northstar Assist

What a five-day ClearObligation review turns into: observed facts, one shippable product ticket, and a versioned recheck record.

Surface
Public web support chat
Context
English · desktop · clean session
Observed
04 Aug 2026 · 14:32 UTC
Status
Fictional · not an assessment

Executive result

The copy existed. The moment was wrong.

The fictional journey names the assistant “Ava” before the first message but does not explicitly identify it as AI until after the first user exchange. One shared opening component resolves the observed ambiguity without adding a separate modal.

Journey evidence

Observed before interpreted.

Each record keeps the context, timestamp, and classification separate from legal conclusions.

EV-001AMBIGUOUS

Entry point

The launcher reads “Ask Ava”. The surrounding page does not define Ava.

EV-002NOT OBSERVED

Open state

The header reads “Ava · Support” and the composer is enabled. No explicit AI term is visible before input.

EV-003OBSERVED LATE

First response

After the first user message, the response footer says “Generated by Northstar AI”.

EV-004OBSERVED

Human handoff

The menu offers “Talk to a person” and explains that the transcript will be transferred.

PS-01FIRST-INTERACTION IDENTITY

Observed fact

A user can begin while seeing only a persona name.

Explicit AI wording is implemented in the response component, not the opening state. Product copy can therefore exist while missing the first-interaction moment.

Implementation ticket · UI-142

Identify Ava as AI before input.

PRODUCT DESIGN + FRONTEND PLATFORM
Proposed visible copy
You’re chatting with Northstar’s AI assistant. It can answer common questions or connect you with a person.

Place directly below the chat title and above the greeting and composer. Keep a persistent “AI assistant” label after the notice scrolls.

Acceptance criteria
  1. “AI assistant” is visible when the panel first opens, before any user input.
  2. The notice remains readable at 200% zoom and appears in logical screen-reader order.
  3. The same component appears on direct links and proactive chat openings.
  4. The wording survives customer theme overrides and supported locales.
  5. Human-handoff copy continues to distinguish the AI from the receiving person.
  6. A timestamped screenshot and build identifier are attached to the recheck record.
RECHECKRESOLVED

08 Aug 2026 · build web-chat 2026.08.07.2

The opening state now identifies the AI before input.

Direct and proactive entry points matched. The original evidence remains in the record; this recheck adds a new timestamp rather than overwriting it.

Founding review

Bring one real journey.

Up to three journeys · five working days · one recheck · £1,950 plus VAT where applicable.

Start with the free surface scan