10
Screens shown, all captured live
1
Real e-signature collected
1
Real handoff closed from a chat message
About this walkthrough
Every screen below is a real screenshot from 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 Annuity,
Rowan Okafor, Ingrid Halvorsen, Teodoro Salazar, Desmond Ilagan, Marisol Fenwick) are fictional demo identities. All
real outbound email in this walkthrough was routed to a single test inbox standing in for the fictional recipients,
so the recordings could be captured safely; the signature step ran against a real e-signature provider (DocuSeal);
the chat exchange shown was a real person, typing a real reply, at the keyboard.
One honest note: on the case that needed a human to close it out from a chat message, that same case briefly
still showed the underlying request as open on another screen after the chat reply closed it — a real gap between
two parts of the platform noticing an update at different times, found and fixed the same day it was found.
Every case starts from the same process map — every step from receiving the paperwork to writing the outcome back to the company's own records is laid out before anything happens.
The transfer request and the replacement disclosure are uploaded and automatically confirmed against the case — no one has to separately track which documents are in hand.
The platform prepares a full, reasoned suitability recommendation. A reviewer reads it, records a decision, and puts their name to it — every recommendation ends in a real decision made by a person.
If a reviewer wants to approve something the platform recommended against, it doesn't just let that pass quietly. It stops and asks for a stated reason before it will proceed.
Above every case, the platform writes a short, plain-language summary of exactly where things stand — what's being exchanged, who it's for, what's already happened, and what it's waiting on next — along with a note of when it was generated and how much of the case record it drew on.
When something's missing or needs fixing, the platform reaches out directly to the person who can supply it, through a secure, single-use link — no account or login required on their end.
The moment a required signature is completed, the process map reflects it immediately and moves on to the next step automatically — nobody has to notice the signature landed and manually restart anything.
The platform follows up on its own schedule and keeps an exact, visible record of how many attempts have been made and how overdue a response is — nothing is ever silently forgotten.
When a wait needs a human decision, the platform can bring that decision to wherever the right person already is. Here, a real reply in Microsoft Teams closes the outstanding step directly, on the record.
Every message the platform sends is kept on the case exactly as it was written, with the recipient's address masked on screen for privacy — and the platform says plainly, right there, that only the address is masked, never the message itself.
