The kind of team this fits: a brokerage claims advocacy desk, roughly 180 open claims a month across clients.
The morning before
180 open claims a month, and a client asking for a status update means the advocate has to go find it across insurer and client touchpoints before they can even reply, let alone act on it.
Image, the morning beforeA photo or illustration of what this looks like today, before any of this runs.
How this could run
Not a feature list. The actual sequence, from the moment the case lands to the moment someone signs it.
- 01
Status lives in one place
Claim status, documents and communications are pulled together across every touchpoint.
- 02
Delays get resolved, not just reported
Coordination with insurers and stakeholders happens as the delay is found, not after a client asks.
- 03
The advocacy path arrives with a plan attached
A recommended path and action plan are ready, not rebuilt from memory each time.
Image, inside Zen StudioScreenshot of a Zen Studio canvas configured for a workflow like this one.
What doesn't change
A senior advocate still handles what actually needs escalating. What changes is how much reaches them by default versus by necessity.
What this could mean
Illustrative, based on the shape of a workflow like this one. The real number depends on the case, the team, and how it's configured.
5 days → 2 hoursStatus change to client communication
70%Claims resolved without senior escalation
Image, inside Zen PilotScreenshot of the Zen Pilot dashboard or explainability panel for a run of this workflow.
Where this lives in the platform
For a claims advocate, a workflow like this starts as a conversation with Zara, describing the process in plain language and getting a first draft of the team back in the same session. Zen Studio is where engineering opens that draft, sets the guardrails node by node, and versions it before it goes live. Zen Pilot is where it actually runs, and where anyone can watch a case move through it in real time, node by node, with the reasoning attached.
