Workflow execution: agents that do the work in your systems
An agent picks up the work as it arrives, reads it, checks it against your rules and writes the result into the system that owns it: the order in the ERP, the shipment in the TMS, the quantities in your estimating file. What does not fit goes to a person. The work moves forward inside the tools your teams already use.
What an agent does in a workflow
Read, compare, validate, update, trigger, escalate: one workflow, several steps, across the systems the operation already runs.
Picks up the work
Emails, attachments and files are read as they arrive, without anyone forwarding them. Nobody has to open a new tool for the work to start.
Reads and checks
Each document is read in the format it came in, then checked against your rules and the records in your systems before anything is written.
Writes it back
The result goes into the system of record, through the interface its vendor provides: an order created in the ERP, a quote prepared in the TMS, a register updated, a document issued.
Escalates what does not fit
An item outside the rules goes to a person with its sources attached, and nothing goes missing silently: an uncertain line raises an alert instead of being dropped.
One workflow, end to end, at Biodéal
Biodéal's customers order by email in every format. One agent takes each order from the inbox to an order in SAP Business One, the way a person would, and no line is lost silently.
A median of 48 seconds from the email arriving to the order being ready in SAP Business One, and about 7% of orders flagged for a person. Everything else goes through without a person in the loop.
See the Biodéal case study- Intake
- The Outlook inbox is wired to a webhook (Microsoft Graph): every incoming email starts processing within seconds, with a queue absorbing volume spikes.
- Reading
- High-resolution OCR plus layout extraction, merged and interpreted by an agent that knows the product catalogue and the customer file.
- Business logic
- Anything that is not an order is rejected, stock-outs raised mid-thread are tracked, and an order is followed across several emails as it is created, merged or replaced.
- SAP order
- Customer matched, quantities converted into the right units, cascading discounts applied, warehouse and document series selected, order created through SAP's Service Layer.
- Control loop
- Every processed email is tagged in Outlook, and any uncertain line raises an alert to the team.
Inputs, outputs and who decides
What goes in is what the operation already receives. What comes out lands where the team already works.
- Inputs
- Emails and their text, native and scanned PDF, Word or ODT tables, scanned forms, spreadsheets, EDI and flat files; plan sets as PDF, DWG and IFC; records from the ERP, the TMS, telematics and the other connected systems.
- Outputs
- An entry in the system that owns it (an order, a shipment, a quote, a register update, quantities in Excel or in your estimating software's import format), an item in a review queue when a person must decide, and a record of every action.
- What a person decides
- What an agent may write on its own, and what waits for a named person, is set for each workflow. At Biodéal, orders that pass the rules are created without a person; on other workflows, nothing is written before an approver signs off.See approvals and audit
- Set per workflow
- Before a workflow goes live, the forward deployed engineer writes down with your team what the agent reads, what it prepares, what a person decides and where the result is written. Where a system has no API, the connector is built during the deployment.See integrations
What an agent does not do
Said plainly, so nobody buys it for something it is not.
- It does not replace your systems. They stay in place and keep running the operation: the agent reads from them and writes into them, and nothing is migrated.
- It does not settle exceptions without a person. In every workflow the exceptions go to a person, and construction document work keeps a human review step before anything is priced or acted on.
- It is not self-serve software. Mirage's engineers build the workflow into your systems, then run, monitor and improve it in production.
- It is not an instant plug-in. A proof of concept comes one week after the first meeting and the first workflow reaches production in 4 to 6 weeks; workflows that span several systems can take longer.
- Mirage publishes no accuracy percentage for its agents.
Where it runs in production
Each line restates the case study it links to.
- Biodéal
- Orders read from email and created in SAP Business One: 2,943 orders and 12,993 order lines since launch, for 113 distinct customers, with a median of 48 seconds from email to order.See the Biodéal case study
- OFRET Groupe
- Quote requests read and drafted from OFRET's rates, inside the Logitude World TMS through its API. More than 90% of standard RFQs are handled automatically; anything outside the standard pattern goes to an operator before it is sent.See the OFRET Groupe case study
- Transwin
- 70% less manual data entry on freight documents. It started with a single document workflow and grew to five systems in production across freight, fuel, mining and fleet.See the Transwin case study
- John Cockerill
- Piping, boilermaking and structural steel drawings read and taken off: 80 to 90% less time on piping takeoff, with engineers reviewing the output instead of measuring.See the John Cockerill case study
- OCBM
- Three agents in production. Every quantity is traceable to its source drawing, and OCBM's estimators review the takeoff line by line.See the OCBM case study
Frequently asked questions
It reads, compares, validates, updates systems, triggers actions and escalates what does not fit, across several steps. At Biodéal, one agent takes an order email from the inbox to an order in SAP Business One: it reads the document, rejects what is not an order, matches the customer, converts the quantities, picks the warehouse and creates the order.
It is set for each workflow with your team. At Biodéal, orders that pass the rules are created in SAP Business One and about 7% are flagged for a check; on other workflows, nothing is written before a named approver signs off.
The ones already in place, through the interface each vendor provides. Where a system has no API, Mirage builds the connector during the deployment. More than 200 systems connected so far.
The item is not guessed at. At Biodéal, an uncertain line raises an alert with a diagnosis and a suggested fix, and the rest of the order is still entered. At OFRET Groupe, a request with missing data or low extraction confidence goes to an operator before anything is sent.
A proof of concept on your own documents comes one week after the first meeting, and the first workflow reaches production in 4 to 6 weeks.
Mirage's engineers run, monitor and improve them in production. Your team reviews what is routed to it.
Bring us the operation you need to improve.
Mirage will map the workflow, identify what can be automated and define the fastest path to production.
Start with one workflow
Leave your work email, then pick a time for a 30-minute call on the workflow where your team loses the most time. You leave with a written plan to automate it. No commitment.