Built because: "Whenever a user interacts with Fin, our system needs to make a real-time, three-way decision:"
The idea, in three working flows
Three tap-through flows show the handover from its three seats: the customer who asks, the colleague who inherits, and the supervisor who corrects. Each reuses the designed content of the two replay pages, cut to four screens.
These are designed prototypes, written for this concept. The conversations are fictional, Kettle is a fictional company, and nothing on this page calls a model.
Opened from the file system: the browser refuses module scripts here, so the flows cannot run. Serve the site folder over HTTP and reload.
Fin settles Priya’s export question. Her contract question escalates, and the handover either carries what Fin knew or drops it.
Four screens, from the settled fix to a handover that repeats nothing.
The same escalation from Marta’s side: five fields arrive at the top of the thread, and she replies without scrolling back.
Four screens, from queue to sent reply.
Fin misreads Nadia’s rate card and nothing flags it. The human catch becomes a guidance entry with its cost stated.
Four screens, from wrong answer to written rule.
d-049 · A seventh page shows the idea as three tap-through flows
- Decision
- Three tap-through flows on a seventh page, notes beside the glass.
- Because
- The replay pages argue at depth; the panel needs tap speed.
- Rejected
- Autoplaying walkthrough videos or GIF captures
- Would measure
- Whether a reviewer taps a full flow before a replay.