The order arrives forty different ways. The line needs it one way.
The documented process says an order arrives. The real one is forty customers, no two formatted alike, half the payload in PDFs, and a routing rule that lives in one sales administrator’s head. Downstream, quality alerts are triaged by whoever is free, supplier certificates expire unnoticed until the audit, and the ISO evidence is rebuilt every year from scratch. These are queues, and the people who own them are the ones who know the product. The queue is where an agent belongs.
- Built on top of your ERP and MES. Nothing gets replaced.
- In one European manufacturer’s order handling, three of eleven steps needed a model (SUPALABS engagement data)
- Quality and compliance steps stay with a named person; the chase work does not
Put an agent on the queue, not on the org chart.
Each role owns one recurring queue. It drafts, it shows its evidence, and a named person signs before anything consequential moves. The last column is the sector’s AI Boundary Map: whether the step is mostly a rule, mostly a model, or stays with a person.
| Role | What it drafts | Who signs | What it reads | Mostly |
|---|---|---|---|---|
| Order intake | The order in the ERP from whatever arrived, email body, PDF, portal export or spreadsheet, with every line matched to a catalogue code and every unmatched line flagged. | Sales administration, on the flagged lines only once the pass rate has earned it. | The shared inbox, the catalogue, customer price lists. | a model |
| Goods receipt and invoice matching | The three-way match between order, receipt and invoice, with exceptions grouped by cause: price, quantity, missing receipt. | Accounts payable, on the exceptions. | ERP purchase orders, receipts, SDI invoices. | code and rules |
| Quality exception triage | Each SPC alert or non-conformity report drafted with the batch, the machine, the last three occurrences and the supplier lot, ready for a decision. | The quality manager. | MES, the quality system, supplier records. | code and rules |
| Supplier qualification | The certificate set per supplier, ISO, REACH and RoHS declarations, conflict-minerals statements, with expiries sixty days out and a request drafted for each. | Purchasing, before a supplier is approved or renewed. | PEC and email attachments, the supplier register. | a model |
| Quote from product rules | A quote from a request, applying the configuration rules and the customer’s conditions, with any request that falls outside the rules routed to a person. | Sales, above the threshold you set. | The configurator rules, price lists, the CRM. | code and rules |
| ISO 9001 evidence | The evidence pack for each clause from records the company already keeps, with gaps listed as questions rather than filled in. | The quality manager, before the certification visit. | The quality system, training records, the document store. | a model |
How much of this is actually AI.
Three of these six queues are deterministic, matching, triage and configured quotes, and a rules engine does them more cheaply than a model ever will. The other three read documents that were written by someone else: customer orders, supplier certificates, the company’s own records. That is where a model earns its place, and it is where the evaluation suite matters most, because the cost of a wrong catalogue code is a wrong shipment. The order-handling workflow SUPALABS mapped in one European manufacturer came out at three of eleven steps needing a model; this page is the same shape.
3 / 6 queues mostly rules · 3 / 6 with a model
No client names. Real patterns.
Every engagement produces the same five documents, whatever the sector. What we can show is anonymised: the pattern, the number, and where it applies.
Three of eleven steps genuinely needed a model in one European manufacturer’s order-handling workflow. The other eight were parsing, lookups, validation and routing (SUPALABS engagement data, 2024–2026).
The order-handling engagement behind these numbers, as redacted documents →Related case studies
Three tiers, set per task type, and you set the thresholds.
Every automated task runs at one of three levels of authority. The tier is set per task type rather than per system, so the same workflow can draft one step, wait for approval on another, and act alone on a third. A task moves up only when the evaluation suite shows the pass rate you defined as the threshold, and it moves back down the moment the monthly report shows a regression.
Nothing is promoted on our say-so. The thresholds are yours, the report that tests them is a named line item, and the decision log shows every action that was taken at every tier.
The full method: five artifacts, three tiers, four rungs →Four rungs. You can stop after any of them.
The problems, one at a time.
Frequently asked questions
The same method, other queues.
Thirty minutes to find out whether there is anything worth mapping.
The call is free, and we will tell you if the answer is no. Bring one queue that costs someone an evening a week.