# Order-exception agents for plants and distributors

The exception floor. An agent sits on the exception loop: late orders, short ships, expedites, and status asks. It packs ERP and email facts, drafts customer and vendor updates, and opens asks when a promise would be invented. A named ops lead accepts anything outbound. That is a production install, not a dashboard.

Owner: A named operations lead
First buy: Field Survey $9,500, then a $24,000 Single Agent Install

On a $15–80 million plant or warehouse, happy-path orders are not the first install. The expensive loop is the exception: late trucks, short ships, and “where is my order.” One person lives in that inbox. An exception floor gives the company its afternoon back without inventing a Friday.

On a $15–80 million plant or warehouse floor, the expensive work is not the happy path. It is the exception: a late truck, a short ship, a customer who wants a date, a vendor who went quiet. One person lives in that inbox. Everyone else waits on that person.

Mid-market operators do not need an enterprise control tower. They need a bot that can read the thread, pack the last accepted promise, and draft the next move without inventing a ship date.

This is exciting because it gives the company its afternoon back. Status work becomes a pack. Escalations stay human. The graph remembers which customers were promised what — so two agents cannot contradict each other next week.

## Who this is for

- Manufacturers and distributors whose status work sits in one inbox.
- A named ops lead who can accept a date or a concession.
- Companies that already have an ERP and do not need another dashboard.

## How you know it is working

- Exceptions closed the same day with an accepted outbound note.
- Customer updates that cite the last accepted promise, not a new invented ETA.
- Repeat contradictions — two Fridays promised to one account — dropping to zero.

## Triage

Inbound status mail, portal tickets, and internal pings become exception records with a customer, an order, and a clock.

## Pack

The bot pulls accepted facts: last ship date, open lines, who owns the account, what was already promised. Proposed inventory numbers stay labeled.

## Draft

Customer and vendor messages are drafted in the company’s voice. Missing facts become questions to ops, not guesses to the customer.

## Ingest

Once a human sends, the promise, the date, and the owner write back into the graph. The next pack is smarter.

## Questions

### What is an exception-floor agent?

It is a production agent on late orders, short ships, expedites, and status asks. It packs accepted facts, drafts updates, and waits for a named ops lead before anything is sent.

### Do we need to replace our ERP?

No. Helixfield wires the tools you already pay for. The install is a loop and a graph, not a new system of record.

### Can the bot tell a customer a new delivery date?

Only after a human accepts that date as a fact. The bot may propose. It may not invent.

### How much does an exception-floor install cost?

A Field Survey is $9,500. One production agent is $24,000. A shared graph across status and expediting is $36,000. Vendor seats are extra and client-paid.

### Will this work if our data is messy?

Messy data is why the survey exists. If the first loop cannot be named, Helixfield will not start an install.