Objective: Three kinds of refusal, all honest: a claim that changed under you, a claim with missing fields, and an action the state machine forbids. Persona: E2E Employee (claimant Asha). Duration: ~1.5 min.
Suggested narration (one segment per on-screen caption, in order):
Good software is honest about problems. Let's look at three. First: what
happens when a claim changed since you last saw it?
The system refuses to act on a version of the claim you never looked at —
and it tells you exactly what to do next: refresh, then decide.
Second: an incomplete claim. Instead of a vague rejection, you get the
blockers by name.
Merchant, category, amount, date — each missing piece called out, so you fix
it in one pass instead of guessing.
And third: some things are simply impossible in a claim's current state.
An approved claim can't be recalled — that's the state machine enforcing the
rule in the backend, not a guideline hoping for good behaviour.