Blog

qAI agent for customer order entry

AI agent for customer order entry: what a person decides

An AI agent for customer order entry keys the order email into your ERP. Which lines it enters alone, which wait for a person, and which it is refused.

4 min readRunning it, Orchestration

by Grisha Pertaia

illustration
  1. session
  2. credential
  3. lookup
  4. score
  5. intake
  6. route
  7. file
  8. sign
  9. intake

An order email arrives at the sales inbox. Someone reads it, finds the customer in the ERP, matches each line to a part and a price, checks stock and the promised date, and keys the sales order. An AI agent for customer order entry can do that reading and keying. The useful question for an operations lead is narrower: which of those lines may it enter on its own, and which must wait for one of your people?

The answer below comes from the order-entry workflow on our operations page. That workflow is designed. It has not run in the sandbox yet, and the steps are how we would build it with you in a pilot.

Most order lines are routine, and a few are not

On a normal day, most lines on most orders match. The part number is on the customer's price list, the price agrees, the stock is there and the date holds. Those lines are typing. An agent can enter them, and your order desk can stop retyping what a customer already wrote.

The lines that matter are the ones that do not match. They are also the ones where a wrong entry costs money:

  • A price below the list. Entered without a decision, it gives away margin on every unit shipped, and the next order quotes it back to you.
  • A date the stock cannot meet. A promise the plant cannot keep moves the cost to the planner, the warehouse and the customer's own schedule.
  • An order above the customer's credit limit. Entered as normal, the goods ship before anyone looks at the account.
  • A part number that is close to a real one. A near match ships the wrong part, and the return costs freight in both directions.

The workflow treats the first three as decisions and the fourth as a line it does not enter. None of them is left to the agent's judgement.

What the agent enters, and what waits

The agent enters
  • permission

    Receives a credential for this one order, and nothing wider

  • allowed

    Reads the order email and finds the customer

  • allowed

    Checks stock and the promised date for each line

  • allowed

    Enters each line that matches the price list

A person decides
  • human review

    A price below the list: your sales lead

  • human review

    A date that slips: your planner, before the customer hears it

  • human review

    An order above a credit limit: the person who holds the account

  • session

    A line with no match: sent to the order desk, not into the ERP

The waiting step is a pause, not a message in a chat tool. The agent drafts the line with the facts beside it: the requested price and the list price, or the promised date and the date the stock allows. The person approves or rejects it. Both answers go on the record with a name.

You choose which steps wait. We start supervised, so every exception above waits for a person in a pilot. You decide later which ones stop needing approval. Changing the workflow is a separate right from running it, so the agent cannot remove its own approval step.

What the agent is refused

Two kinds of step are refused outright, because the permission for one order never includes them.

Stock reserved for another customer. A short line tempts a quick fix: take the parts already allocated to a different order. The agent's credential covers this order only. The move is outside it, so the step is refused, and the reason is written down. Your planner sees the short line and decides.

A change to the customer record. An order email can ask for delivery to a new address. The agent does not change addresses, prices or credit limits on the customer record; those stay with your people. The order to shipment workflow carries the same rule further down the line: goods go only to the address on file.

A refusal here does not depend on how the email is worded. The step is outside the job either way.

What you can check afterwards

Every step leaves a line on the record: the credential for the order, each line read, each stock check, each entry, each approval with the approver's name, and each refusal with its reason. When a customer disputes an order, you start from that record, not from someone's memory of an email.

You can export the record and check it on your own machine with the open verifier, without us. The guarantees page says how an approval step works and where it stops: Ares does not decide which steps are sensitive. You do.

The closest run you can watch today is the requisition scenario. An order is drafted, a supplier change is refused, and an order above the threshold waits for the budget holder. It is the purchasing side, not order entry, but the approval and the refusal work the same way.

What it does not do

  • It does not set your price rules, credit limits or promise dates. Your people do, and the agent follows them.
  • It does not replace your ERP or your warehouse tool. It works between the inbox and those systems.
  • It reads the order as written. A line it cannot match goes to a person; it does not guess.
  • Order entry is designed, not yet run in the sandbox. The other operations workflows and their states are on the workflows page.
Keep reading