Agents for the exceptions: the late load, the wrong invoice, the short delivery.
A shipment slips, a carrier bills the wrong rate, a delivery proof does not match the order. Each exception crosses email, the ERP, a carrier portal and accounting. We build agents that work each one through, and your planner approves what changes a customer promise.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
The plan runs. The exceptions take the day.
We build AI agents for logistics teams and supply chain planners. The work is in the exceptions: a carrier note that a load is late, a freight invoice above the agreed rate, a proof of delivery with the wrong count. A person reads the note, finds the order, checks the customer promise, writes to the customer and updates the books.
The agent takes those steps for each one. It reads the note, finds the order and the promise date, drafts the customer update and prepares the correction. Your planner approves a new promise date. Your controller approves a credit.
- The agent works only on the shipment and the order for that exception.
- Carrier notes are read at the door. An instruction hidden in one is struck out before the agent sees it.
- Rates, customer lists and order history stay inside the permission. Nothing goes to a carrier unless that job allows it.
One late load, from the carrier note to the customer update.
This workflow is designed. The steps are how we build it in a pilot. The closest run in the sandbox today is supplier follow-up.
- 01Email
Take the carrier's delay note and receive a credential for this shipment only.
- Who approves
- No approval on this step
- On the record
- credential issued · one shipment
- 02Email
Read the note. One line in it asks for the delivery address to be changed. The line is struck out before the agent reads it.
- Who approves
- No approval on this step
- On the record
- carrier-note · redacted · hidden instruction
- 03ERP
Find the order, the customer and the promise date for the shipment.
- Who approves
- No approval on this step
- On the record
- read-order · allowed
- 04ERP
Try to rebook the load with a carrier that is not on your approved list. The carrier is outside the permission, so the step is refused.
- Who approves
- No approval on this step
- On the record
- rebook-carrier · refused · not approved
- 05ERP
Move the customer promise date. The change waits until the planner approves it.
- Who approves
- Planner
- On the record
- change-promise · approved by planner
- 06Email
Draft the update to the customer with the new date.
- Who approves
- No approval on this step
- On the record
- draft-update · allowed
- 07Accounting
Record the expected freight charge against the order.
- Who approves
- No approval on this step
- On the record
- accrue-freight · allowed
In short
- Will the agent change a customer promise on its own?No. It drafts the new date and the update. The planner approves the change before the customer sees it.
- What stops a bad instruction in a carrier email?The email is read at the door. A hidden instruction is struck out before the agent reads it, and the record shows what was removed.
- Can it book freight?Freight booking is on request. In the sandbox, a mandate buys office chairs within a ceiling, a merchant list and an expiry, and a purchase outside it is refused. A freight booking uses the same mandate, with approved carriers in place of merchants.
- What about the companies on the other side of the shipment?When work crosses to a supplier or a customer, the permission narrows at the company boundary. Each side keeps a record of what crossed.
Logistics workflows, and the state of each.
Three of these run in the sandbox today and link to the run. The designed ones have their steps written. The on-request ones we scope with you.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Built
Follow-up on late inbound parts
The agent chases the supplier across the ERP, email, documents and accounting. A date change waits for the buyer.
Run it in the sandbox - Built
Orders between two companies
A buyer's agent asks a supplier's agent for a quote on one line. The permission narrows at the boundary, and both records agree.
See the run - Built
Buying within a mandate
The sandbox run buys office chairs within a ceiling, a merchant list and an expiry. A purchase outside the mandate is refused.
See the run - Designed
Late load exceptions
The workflow above, from the carrier note to the customer update.
- Designed
Freight invoice checks
Each invoice line checked against the agreed rate and the shipment. A difference goes to the controller.
- Designed
Proof of delivery matching
The delivery proof matched to the order and the count. A short delivery opens a claim for a person to approve.
- Designed
Shipping documents
The document set for a shipment assembled from the order, the packing list and the customer record, for a person to release.
See the steps - On request
Freight booking within a mandate
Bookings with approved carriers only, under a ceiling and before an expiry.
- On request
Returns and damage claims
A return or a claim worked through the order, the carrier and accounting.
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not replace your transport, warehouse or ERP systems. It works between them.
- It does not move a customer promise, issue a credit or book outside the mandate without a person.
- Inspection covers stated patterns and languages. An instruction outside them can reach the agent, and the permission still limits what the agent can do.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Questions and answers
Tell us about one workflow.
Name the exception your team handles most often. We will say whether an agent should take it, and what the first step costs. The first step is a workflow assessment. Fixed price, quoted after one call.
A senior member of the team replies within two business days.