Skip to content

How agents work for your team

Agents start by working for the people who do the work today. This page covers what that looks like in practice: the kinds of help an agent gives, where it works, who is in charge of it and what someone on the order desk sees on a normal day.

An agent is software that uses an AI model to do a step of digital work: read a purchase order, build a sales order, compare an invoice with a receipt. Our forward-deployed engineers build each agent for one workflow, on your data, your rules and your exceptions. It is not a general chat window that your team has to adapt to.

A workflow’s first two levels with an agent are Level 1 (Assisted) and Level 2 (Prepared). At both, the agent works for the person at the desk, in three ways.

Kind of help What the agent does Examples
Drafting Writes a first version for a person to finish Reads an emailed purchase order and drafts the sales order. Drafts the follow-up to a supplier who has not confirmed a date.
Preparing Builds the whole transaction, ready for a decision Builds the complete sales order with every line, price and date. Lines up a supplier invoice with its purchase order and receipt.
Checking Compares one thing with another and flags the difference The price on a purchase order against your price list. A supplier’s confirmed date against the date you asked for.

An agent also summarizes and answers questions about the work on the screen. It can cut a long email thread with a supplier down to the points that matter, or say what this customer paid for this part last time. When it answers from your ERP data, it shows where the answer came from.

At these two levels an agent writes nothing to your ERP on its own. At Level 1 a person keys the transaction. At Level 2 nothing is written until a person approves it.

Agents work the queues in the operations layer, the same queues your people work. A purchase order that arrives in the customer service inbox goes into the order queue. The agent takes it, does its step and puts the result back for a person, with the original document attached.

That has three consequences.

  • Your people do not go somewhere else to use the agent. Its work shows up in the screen they already use for that workflow.
  • The agent has only the access its workflow needs. An agent that drafts sales orders can read customers, items and prices. It cannot see payroll or change a price list.
  • Everything the agent does is recorded in the audit trail, with its inputs, its decision and its result.

The queue, the approval screen and the audit trail come from our reusable tooling. What they show for your workflow is written for you: the checks, the fields the agent marks and the reasons an order stops.

The workflow owner is one of your employees: the customer service manager for order entry, the purchasing manager for supplier follow-up, the controller for AP invoice matching. They decide how the workflow should work and sign off changes to it. For the agent in that workflow, the workflow owner:

  • decides what the agent may do and sets its limits
  • agrees the threshold the agent has to meet at each level, before that level starts
  • signs off every move up the autonomy ladder
  • can move the workflow down a level without a review, for example back to approving every order.

If the agent keeps getting the same thing wrong, the workflow owner is the person to tell. During the Embedded Build, our engineers are on site to hear it too.

  1. Someone on the order desk opens the order queue. Each purchase order that came in by email overnight is a line in the queue, with the customer, the purchase order number and whether the agent has prepared it.
  2. They open the first one. The customer’s purchase order is on one side of the screen and the prepared sales order is on the other.
  3. The agent has marked what it wants checked: a part number it translated from the customer’s own number, a price that differs from your price list, a requested date inside your normal lead time.
  4. They fix what is wrong. Each correction is recorded, field by field.
  5. They approve the order. The operations layer writes it to the ERP and shows the ERP’s order number.
  6. A purchase order the agent could not read, such as a blurred scan, is in the queue too, marked to be entered by hand.

At Level 1 the morning is the same up to step 3. The agent’s work is a draft beside the purchase order, and the person keys the order.

What changes for the people who do the work

Section titled “What changes for the people who do the work”
  • The keying shrinks. Checking, deciding and handling exceptions stay with your people and become most of the job. The hours that keying took are measured and shown to you, and what your team does with them is your decision.
  • Their corrections are the measurement. Our engineers count each correction, and those counts are what a promotion review looks at when it decides whether the workflow is ready to move up.
  • What they know becomes the rules. Which customer always writes the wrong unit of measure. Which ship-to address needs a liftgate. Our engineers build that knowledge into the rules with the people who hold it.
  • The work does change. As a workflow moves up the ladder, agents take over more of the digital work, one step at a time. The people who do that work today decide how it should work, approve what agents prepare, handle the exceptions and audit the results.