Flow
One Place. Every Case.Flow is where work happens. Each operator opens one screen and sees exactly what to do next, across every system the business runs on.
The cockpit, not the dashboard.
A dashboard tells you what happened. A cockpit tells you what to do.
Flow is a cockpit. Each operator who opens it sees a single ordered list of cases — the work that's currently theirs. They see the next task in the active case, the agent's instruction in plain language, and a chat where they can ask, push back, or report what they did. They do not navigate menus. They do not switch tabs. They do not log into other systems. The work comes to them.
One screen. Three regions.
The same screen for every vertical, every operator, every day.
What Flow does.
- The case list. Every operator sees only the cases assigned to them, ordered by the agent's priority. The list updates in real time as the agent processes new work, validates completed work, and routes between operators.
- The current task. Each case opens to a single active task. The agent has already prepared the inputs, computed the values, and drafted whatever needs drafting. The operator sees the instruction in plain language and the data needed to act.
- The validation handshake. When the operator marks a task done, the agent verifies — through an API, a screen check, a database query. If verification fails, the task stays open with an explanation. If it passes, the case moves forward.
- The chat. Every case has a chat. The operator can ask the agent for context, request a different action, escalate an exception, or just leave a note. The chat is part of the audit trail.
- The exception channel. When something falls outside the workflow, the operator surfaces it through the chat or a structured exception report. The exception goes to the right human, not to a queue.
Dashboard, cockpit, Flow.
Who works in Flow.
The person whose job is to execute one function — claims, scheduling, procurement, collections. They open Flow, work through the cases, close them, leave. Flow is their entire interface.
The person who oversees a function. They see the cases of everyone on their team, can reassign, can pull cases up the priority order, can view aggregate views over their team's work.
The person running the business. They see the rolled-up view across all functions — open volume, throughput, exceptions, KPIs. They drill into a single case when needed. Otherwise they watch the system run.
Flow is the runtime.
Flow is what the agent uses to communicate with the people in the building. Without Flow, the agent has no surface. Without the agent, Flow is empty. They are two halves of the same system.
Flow is where every other product in the ARM family eventually shows up — PRM cases land in Flow, Vendors approvals land in Flow, ERP exceptions land in Flow. Flow is the single screen that makes the rest of the system tolerable to use.