AgentBiz is the white-label AI ops team agencies run under their own brand. This page is the mechanics: what it reads, what it may do, what it has to prove, and where you still have to say yes.
Six stages. Each one either produces something the next stage can verify, or it stops.
Something in a merchant's order flow stops matching the promise: a carrier scan goes quiet, a fulfillment stalls, a check fails. The signal comes from the merchant's own systems, not from a guess.
The agent reads the order and its fulfillment state directly from the store. Every conclusion it reports has to point at a real order field. If it cannot reach the store, it says so — it does not fill the gap with a plausible answer.
It works out what the case actually needs: a customer update, a note for whoever picks this up next, or an escalation to you.
It does the work in the merchant's real system. Actions are scoped: today the only write it can perform on a store is appending a note to an order.
Each action has to return evidence from the system it touched. This is the part most tooling skips, so the rules are spelled out below.
What reaches the merchant goes out under your brand, after you approve it. Your logo, your color, your name.
Most AI tooling asks you to trust a “done”. We treat an unproven “done” as a bug.
When the agent appends a note to an order, the proof it records is the order id the store sent back — not the order id the agent sent in. An action cannot vouch for itself.
If a write reports success but carries no evidence field, the platform rewrites the result to failed and logs it as a silent failure. The agent then cannot tell anyone the work is done, because as far as the system is concerned, it isn't.
Before appending to an order note, the previous note is read and recorded. If that read fails, the write does not happen — nothing is blind-overwritten — and the prior value is kept so the change can be undone.
It came out of a real incident in our own system: an integration returned success with an empty id, and the agent confidently reported a publish that had never happened. The contract exists so that failure mode cannot repeat quietly.
What the AI is allowed to touch is a property of the platform, not of how carefully someone wrote the prompt.
A page like this is easy to overstate, so here is the other half of it.
The first design partners decide which exceptions get built out first, and what the merchant-facing side looks like.
Become a Design Partner →