Workflow software has moved cases between people for decades. A ticket arrives, a rule assigns it to a queue, a person reads it and decides what happens. Intelligent workflow automation puts a model at some of those decision points. The workflow reads the ticket, decides what it is and what should happen, and either does it or hands it to a person with a recommendation.
What makes a workflow intelligent?
The test is whether the workflow makes a decision that depends on the content of the case. Three kinds of decision come up again and again:
- Classification. What is this request? A refund, a dispute, a change of plan, a complaint that needs a supervisor.
- Next step. Given the account, the policy and the history, which action applies? Approve, ask for a document, escalate.
- Generation. Draft the reply, the case note or the adjustment memo for a person to send or for the workflow to send itself.
Routing by a fixed field ("all invoices over a threshold go to finance") is ordinary workflow automation, however modern the tool.
How does it run in an operation?
Consider a parcel carrier whose drivers report failed deliveries in free-text notes and photos. An intelligent workflow reads each report, matches it to the shipment and the customer's delivery terms, and classifies the problem: a redelivery the terms allow, a return to the depot, a damage claim. The clear cases are resolved by rule. The ones where the model is unsure, or where the parcel's value crosses a limit, go to a customer service specialist with the shipment record, the driver's note and the photo side by side and a suggested resolution.
The specialist spends the day on the cases that need a specialist. The workflow keeps a record of every decision, so a manager can check a sample each week and tune the thresholds.
What guardrails make a deciding workflow safe?
A workflow that decides needs more control than one that routes. The working set:
- Confidence thresholds that send low-confidence decisions to a person.
- Action limits on what the workflow may change on its own, by type and by value.
- Approvals for actions that are hard to undo.
- An audit trail of the input, the decision, the action and the outcome.
- A stop switch that returns all cases to people.
- Sampling of automated decisions, reviewed by someone who knows the work.
The NIST AI Risk Management Framework (NIST AI 100-1, January 2023), which NIST intends for voluntary use, organizes AI risk management into four functions: Govern, Map, Measure and Manage. It is a reasonable checklist to hold an intelligent workflow against. The AI guardrails entry goes further into limits and approvals.
How does it relate to intelligent automation and process redesign?
An intelligent workflow is usually the orchestration layer inside intelligent automation, the part that carries a case from step to step. It works best after a process redesign: decide which decisions the model should own and which stay with people, then build the workflow around that split. Teams that want one engineered and operated for a specific process can look at AI workflow automation.
Should every step get a model?
Only the steps where the decision depends on reading unstructured content. A tool that makes it easy to add a model everywhere invites overuse, and each model decision adds a failure mode and a monitoring burden. Keep plain rules wherever a rule will do.
