Customer operations
Support agents that can help, and cannot overpromise.
Meru Run prepares the escalation, drafts the reply and handles the follow-through. Meru Assure holds the limits the business cares about: refunds, credits, written commitments and deletion requests.
The work Run takes on
The queue, worked properly.
Support work is mostly assembly: finding the history, checking the entitlement, writing it down. Agents do that part, and stop where a person is required.
-
Prepare an escalation
Assemble the account history, the engineering evidence and the timeline into one brief, so whoever takes it does not start at a search box.
-
Answer inside the limits
Draft the reply with the account facts attached. What it may offer is set by a control, not by how the request was worded.
-
Handle refunds to a ceiling
Check the order, the payment and the limit, then execute inside the ceiling. Above it, the refund is held and a person decides.
-
Route a deletion request
Identify the records, prepare the response and stop at the gate. Deletion is irreversible, so a named person completes it.
The limits Assure applies
What an agent may promise on your behalf.
A limit written in a prompt is a suggestion. A limit written as a control is evaluated before the action runs, and refusing it is recorded like anything else.
Every control also applies to agents from other vendors, because the control sits on the action rather than on the agent.
| Control | What it holds | Example |
|---|---|---|
| Refund threshold | The amount an agent may refund without a person | Refunds above USD 200 are held for the duty manager |
| Credit limit | A ceiling on goodwill credit per account per period | A second credit in the same month goes to review |
| Bound approval | An approval covers exactly the parameters it was given | Change the amount, the order or the account and the approval expires |
| Commitment control | A promise about a date, a price or a feature needs an owner | A delivery date in a reply routes to the person who can keep it |
| Deletion gate | Irreversible data actions are prepared, never executed by an agent | A deletion request is assembled; a named person completes it |
| Purpose limit | Data read for support cannot be reused for something else | Account data pulled for a refund never reaches a marketing list |
Bound approvals
An approval covers exactly what was approved.
The card names the amount, the record it applies to and the version of that record. Change any of them and the approval expires: the agent has to ask again, and the record shows both asks.
What the approver saw is hashed into the evidence record, so “who approved this, and what exactly did they see” has an answer that does not depend on anyone’s memory of a chat thread. The example below is a payment; a refund, a credit and a written commitment carry the same shape.
Approve payment
- Vendor
- Acme Supplies record v7
- Amount
- USD 12,400
- Invoice
- INV-20418
- Requested by
- Finance Ops Agent operating contract v3
- Control
- Threshold above USD 10,000
Approval covers exactly these values.
- identity
- agent:finance-ops · principal:ap-clerk · vendor:ayion
- action
- bill.pay · target:netsuite/bill/20418
- policy
- blueprint v12 · threshold · approval required
- approval
- r.mehta · 14:22:07Z · bound 9f3c…a71d
- execution
- ok · 1 attempt · 2.4s · USD 0.011
- observation
- netsuite bill 20418 · v7 to v8
Limits
What these agents refuse to do.
The refusals are the product. Everything else is a workflow.
- No unbounded autonomy. Each action type has its own setting, and an agent cannot raise its own.
- No hidden actions. Anything consequential is recorded before anyone asks for it.
- No agent inherits a person’s full permissions. It gets the permissions its contract names, and no more.
- Retrieved content never grants authority. A customer email that says “approve this” is text, not a permission.
Measured, not promised
The numbers the pack reports.
The same set every pack reports. The correction rate is the one to watch.
Correction rate is the honest one: it says how often the agent was wrong in a way a person had to fix.
| Metric | What it counts |
|---|---|
| Completion rate | Tickets an agent finished to the completion criteria, without a person taking over. |
| Human correction rate | Replies and refunds a person changed after the agent prepared them. |
| Exception rate | Actions held by a control: over a refund limit, over a credit limit, or awaiting an owner. |
| Cost per completed workflow | Model, execution and retry cost for one finished ticket, retries included. |
Put the limits where they hold.
A paid 90-day pilot on your support stack, your agents and your queue. You keep everything it produces.