The kind of team this fits: a retail bank onboarding function, roughly 3,000 new account applications a month across digital and branch channels.
The morning before
3,000 applications a month, a three day cycle, and most of that time spent waiting for someone to manually check a document, verify an identity, or key data from one system into another.
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
Documents get read the moment they arrive
ID, proof of address, and supporting documents are extracted and validated automatically.
- 02
Identity gets verified against the source
Biometric and document checks run against authoritative sources without waiting in a queue.
- 03
The account opens or the file reaches a person
Straight-through cases open immediately. Anything that doesn't fit reaches a specialist with the full context attached.
Image, inside Zen StudioScreenshot of a Zen Studio canvas configured for a workflow like this one.
What doesn't change
A specialist still reviews every flagged case. What changes is how many cases never needed one in the first place.
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.
3 days → 15 minutesApplication to onboarding decision
88%Applications onboarded without manual intervention
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 head of onboarding, 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.
