Regisseur · Product Walkthrough
A claims back office that runs itself
Three real, end-to-end claims: one where everything arrives on time, one where a document is missing and the beneficiary replies, and one where the beneficiary never replies at all — and the platform hands it to a person instead of guessing or giving up silently.
3
Real claim scenarios shown
2
Human decisions in the flagship case
1
Real, automatic handoff to a person when nobody replies
0
Fabricated screens
46
Screens captured live
About this walkthrough
Every screen below is a real screenshot from three automated, end-to-end runs of Regisseur against a real, working deployment — not a mock-up, not staged data. The company, people, and policy numbers shown (Woodgrove Life, Priya Kavanagh, Corinne Ellery, Nolan Voss) are fictional demo identities. All real outbound messages in this walkthrough were routed to a single test inbox standing in for the fictional beneficiaries, so the recordings could be captured safely.
Two honest notes: first, adding the beneficiary to the case record (shown in Parts 2 and 3) is currently a manual setup step rather than fully automatic — closing that gap is on the roadmap. Second, in Part 3's automated follow-up sequence, the reminder attempts were correctly counted and the case was correctly escalated to a person once they ran out — but the reminder messages themselves were not actually re-sent during those attempts, due to the same beneficiary-linking gap. The single message shown going out in Chapter 22, and the handoff to a person in Chapter 25, both happened for real. A few other real integration issues were found and fixed during these very runs — that is exactly what running the real product, instead of a rehearsed demo, is meant to catch.
Part 1 — When Nothing Is Missing
Everything the platform needs arrives up front. It checks, finds nothing missing, and moves straight through with a single required review — no one has to chase anything down.
Getting a Claim Started
A claim is filed and the case goes live
A new claim case begins from a pre-built process template — the same starting point every case in this walkthrough uses.
Before anything happens, the platform shows exactly who is responsible for the one step that needs a person — no surprises about who owns what.
The moment the case activates, the platform's own visual map of every step lights up, ready to track the claim end to end.
Everything Needed, From the Start
Both required documents on hand before the first step is even done
The initial claim notice is uploaded and attached to the case.
The supporting document is attached at the same time, before the first step is even marked done. Because nothing is missing, this claim will move straight through to a decision.
Once the first, human step is marked complete, everything downstream picks up on its own — no one has to kick off the next step by hand.
Verified, and Routed Straight Through
Nothing is missing, so nothing needs to be asked for
The platform checks the claim against the company's own policy records and confirms who the beneficiary is — pulled from the company's own system of record, never from documents the claimant submitted.
Because both documents were already there, the platform's own process map shows the case routing straight past the follow-up step entirely.
The One Person Involved
A single, required human review before a decision is finalized
The claim is parked for a single, required human review before anything is decided — the one point in this case where a person weighs in.
The reviewer approves, and the claim proceeds automatically from here, with no further review required.
No Second Reviewer Needed
Within the company's own approval authority — no escalation required
Because the payable amount is within the company's own approval authority, the platform carries the claim straight through — a second, more senior reviewer is never brought in.
The Settlement Letter, Generated
A real, formal document, filled in automatically
A real, formal settlement letter is generated automatically, filled in from the claim's own figures.
The Settlement, Delivered
A real email to the beneficiary of record
The platform attempts a text notification (honestly recorded as not sent — no text-messaging service configured for this demo) and then delivers a real settlement email to the beneficiary.
The Company's Own Records, Updated
A real update to the policy system, not a summary
The claim's outcome is written back to the company's own policy system automatically — a real update, not a summary.
Every Step, Marked Complete
The floor: minimal human involvement, start to finish
The process map shows each step so far marked complete, from the initial filing through settlement and the company's own record update — this is the floor: a claim resolved with minimal human involvement.
Part 2 — When Something's Missing, and the Beneficiary Replies
One document is missing at the start. The platform drafts a considerate, complete request, a person reviews and approves it, a real email goes out, the beneficiary opens it and uploads what was asked for through a secure link — and the case continues on its own, no one has to notice the reply and restart anything. From there it carries straight through a final review, settlement, and a system update, to a clean close. Two decisions from a person, start to finish.
A New Claim, Started the Same Way
The same process, a different starting point ahead
The same starting point as before — the one human-owned step is assigned before the case goes live.
One Document Is Missing
The claim notice arrives; its supporting document does not — yet
The claim notice is attached — but the supporting document isn't there yet. That gap is the whole story of this case.
The Platform Notices, and Prepares to Ask
An automatic check catches the gap and adds the beneficiary to the case
The platform's own completeness check finds the missing document and routes the case toward asking the beneficiary for it.
Nobody outside the company is on the case record yet.
The beneficiary is added to the case as a named party, so the platform knows exactly who it's corresponding with.
A Person Reviews Before Anything Goes Out
A considerate, complete request, approved by a real person before it's sent
The platform drafts the exact message it wants to send — leading with condolences, explaining clearly what's needed and why — and holds it for a person to review before anything goes out. Nothing is ever sent without that review.
No request has gone out yet — the outstanding-items list is still empty.
The reviewer reads the drafted message and chooses to send it exactly as written.
The moment approval is submitted, the real email goes out.
The case's own communications record shows the request going out — a genuine, timestamped event.
Now We're Waiting — and It Shows
The outstanding request is visible the moment it goes out
The moment the request goes out, it appears as an open item on the case, along with the built-in follow-up schedule if nothing comes back.
The case is now waiting on the beneficiary to act — a real person has to open a real email and respond.
The Reply Arrives, and the Case Picks Itself Back Up
A real reply, a real upload, and the case continues on its own
The beneficiary opens the email and uploads the missing document through a secure link made just for them. The moment it lands, the case's own process map shows it move on to the next step — nobody had to notice the reply and restart anything.
The outstanding request updates itself the instant the document arrives — not because someone remembered to check and close it out by hand.
A Second, Final Decision
The only other point where a person is required to weigh in
The claim is parked for its second and final required human review.
Everything After That Ran on Its Own
Settlement, delivery, and the company's own record update — untouched by a person
With the payable amount inside the company's own approval authority, the platform carries the claim forward automatically — no further review needed.
A real, formal settlement letter is generated automatically.
The platform attempts a text notification (honestly recorded as not sent — no service configured for this demo) and then delivers the real settlement email.
The claim's outcome is written back to the company's own policy system.
Every Step, Marked Complete
Two decisions, start to finish
The process map shows each step so far marked complete — from the initial filing, through the missing-document request, the beneficiary's reply, and the final review, to settlement. This case needed exactly two decisions from a person the whole way through; everything else — including noticing the missing document, asking for it, and resuming when it arrived — ran on its own.
Part 3 — When Nobody Replies
The identical process, except this time the beneficiary never responds. The platform follows up automatically on a fixed schedule, and once those attempts are used up, it doesn't keep trying on its own — it hands the situation to a person, clearly and on the record.
The Same Process Begins
Same steps, same checks — this time, the beneficiary won't reply
The same setup as before — the one human-owned step is assigned before the case goes live.
The Same Missing Document — This Time, Permanently
Nobody ever supplies it
The claim notice arrives without its supporting document, exactly like the previous case — except this time, nobody ever supplies it.
The Same Setup
The beneficiary is added to the case record, the same way as before
The beneficiary is added to the case as a named party, the same way as before.
The One Decision This Case Requires
The identical, considerate request, reviewed and sent
The platform drafts the identical kind of considerate, complete request as before, and holds it for review — the process treats every case the same way, whether or not the beneficiary is about to reply.
The reviewer approves, and the message goes out. This is the only outbound message this case will ever need to send.
The request goes out, recorded on the case exactly the same way as before.
Waiting Begins
The outstanding request is on the record, the same as before
The outstanding request appears immediately, with its built-in follow-up schedule — the same starting point as the previous case. This time, no reply ever comes.
Following Up, On Its Own Schedule
No reply ever comes, but the platform keeps checking, on its own
The platform checks in on its own schedule, without anyone needing to remember. After the built-in attempts are used up with no response, the request is marked overdue on the case record.
When Follow-Ups Run Out, a Person Takes Over
Handed to a person — not sent again automatically
Once the built-in follow-up attempts are exhausted, the platform stops trying on its own and hands the situation to a person, with a clear, plain-language explanation of exactly what happened and what's needed.
The same situation shows up directly in a workspace-wide worklist too — not buried on a single case page, but somewhere a person checking their own queue will actually see it.
Left Honestly Open
No invented resolution — the case stays exactly where the facts leave it
The process map shows exactly where things stand: everything up to this point is done, and the step waiting on the beneficiary is still open. Nothing is invented or force-completed — if the beneficiary responds later, the case can still pick up from exactly here.
