Everything in Opzaro starts from the same question: what does the person doing the work — and the person managing the queue — actually need? The platform is built outward from that, not down from a process-modelling notation.
These are the things a team leader or member of staff interacts with constantly — and they're configured by an administrator in the UI, not modelled by a developer.
Each step can carry an SLA target set by any administrator — no process model required. Tasks show green, amber or red on the row itself, so everyone sees queue health at a glance.
Team leaders see every task across the processes they oversee, reassign work when someone's out, and rebalance load — without needing admin rights to the whole platform.
When the default order isn't right — a key client, a regulatory deadline — team leaders set a work order number and move it to the top of the queue.
Normal, High or Urgent — set by the people doing the work, and reflected instantly in how every task list is sorted.
Tasks waiting on an inbound email, a WhatsApp reply, or a subprocess show exactly what they're waiting for — not just "in progress".
A deadline is a hard timeout. When it's reached, Opzaro can auto-approve, auto-escalate, or move the task on — no one has to notice it first.
Export step-by-step performance data — time in each step, who did what, SLA breaches — as CSV, whenever you need it, without a request to IT.
Every step transition, data change and automated action is logged against the task, for every process, automatically.
Processes are drawn as visual diagrams — start events, user tasks, gateways and end events — using the BPMN standard. Click any step to configure it across a small set of tabs that map to real operational decisions: how it's assigned, who can see it, what its SLA and deadline are, and what happens on entry and exit.
The form builder behind each step covers the field types operations teams actually need: text, numbers, dates, dropdowns, checklists, file uploads, tables, digital signatures, and read-only displays that can reference other fields dynamically.
Step configuration, in one place
Each tab is a business decision, not a technical one: who can act on this step, how long it should take, what happens if it runs over, and who it goes to next. An administrator makes these calls directly — without touching the diagram.
Opzaro is designed to sit inside your existing technology landscape — not to replace it.
Staff sign in with the credentials they already use. Permissions and team leader status can be driven from your existing Azure AD groups, with admin-managed group caching to keep things fast.
Templates and reference documents are available to step logic at runtime, so your existing document store stays the source of truth — not a copy living inside the workflow tool.
Every action available in the UI is available via API. Processes can also expose a public, embeddable form so external parties — clients, applicants, suppliers — can start a workflow without logging in.
Step logic is written in PHP and JavaScript — industry-standard languages your existing developers already know — and lives visibly inside the workflow, not hidden in a black box. Scripts have full access to the platform API, so anything Opzaro can do, your code can do too.
Administrators can describe what a step should do in plain English, and Opzaro generates the code — ready to review, edit and save. AI helping build the automation, not just running inside it.
We'll walk through a real process from your operation — onboarding, approvals, claims, change control — and show how it would look, step by step.