The Human Clause A support experience, redesigned

Wrong UX Human UX

Screen 4 of 6

Platform Support Automated assistance, always on Automation where it helps · humans where it counts

Case status

Checking…

Closed · final

Status is unavailable for this case

Case TOS-2025-7741 is closed. Status pages exist for open cases only. Last updated: never.

Messages sent 14

Humans reached 0

Appeals read by a person 0

Days stuck in the loop 7

You are here because nowhere else answered.

This page is what a support system looks like from the outside when it has no inside.

Scene 04 · Oct 8, 09:45 UTC — four minutes after you filed

Live status

This page updates while you watch. On purpose.

Live

Received09:40
Brief attached09:41
Specialist matchingnow
Decision—

Your place in the review stack 14 cases ahead of you in the review stack · moving, not stuck

Reply target · a named specialist

5:58:12

A written decision from a named human, or an honest delay note — never silence.

Reviewer

Matching a specialist — usually within the hour of filing. The name appears here the moment it happens.

What happens next

Your specialist reads the brief, your statement, and the evidence — every word
She files a written decision — reinstatement or refusal, with reasons either way
You can reply to her decision, and a human reads that too

Case study · 04 of 06

Time, made visible

Between “appeal sent” and “decision made” lies the cruelest gap in automated support: the waiting, with no clock, no queue, no name. The redesign treats silence as a defect — it publishes the pipeline, the position, the countdown, and eventually, the person.

The problem

“Closed” cases have no status page. Open ones barely do. The user refreshes an inbox that never changes, because the platform considers the inside of a queue private — private from the person inside it.

The redesign

Four states, honestly labeled — received, brief attached, specialist matching, decision — with the stack position counting down, an SLA ring running on real seconds, and the matcher’s promise printed: a name within the hour. Here it took 11 minutes.

Details to notice

This demo queue advances while you watch — deliberately compressed from hours to seconds so the feeling is visible.
The clock reads 23 h 55 m and falls: the 24 h target started at 09:40, when the appeal was filed. The math is meant to check out.
The assignment lands mid-scene — watch the pipeline step flip to “Human review” when Maya’s name appears.
“Matching” states are shown, not hidden — an in-progress case is information too.
In Wrong UX, the same URL is a dead end. There is no clock to obey.

Each screen is one moment of the same story, in two systems — switch worlds above to compare that moment, then walk on; time moves forward with you.

Portfolio website