Guide

Keeping a person in the loop when an AI agent drafts

Let the agent prepare and a person send. The agent puts its draft quote or email in a review queue, and nothing reaches a customer until someone with authority approves it.

Request a free discovery session

Published 2026-11-01 by VisionzLab

The rule: the agent drafts, a person sends

The simplest safe design gives the agent permission to create drafts and nothing more. It can read the request, look up your catalogue, prices and history, and write the quote or reply. Sending, committing a price, promising a date or changing a customer record stays with your team.

Enforce this with permissions as well as instructions. If the agent's account can only save drafts, a bad prompt or an odd email can't make it send anything.

Where to put the approval step

Approve everything at first. As your team learns where the agent is reliable, keep the approval step on the work where a mistake is expensive or hard to undo:

Anything that commits a price, a discount, a delivery date or credit terms.
First contact with a new customer or supplier.
Anything outside your rules: unknown items, substitutes, unusual quantities or terms.
Complaints, cancellations and anything with legal or safety wording.

What the reviewer needs to see

An approval is only useful if the reviewer can check the draft quickly. Show these next to it:

The original request, so the draft can be compared with what the customer asked for.
What the agent matched and where it came from: the item, the price list, the past order.
What it wasn't sure about, flagged at the top rather than buried in the draft.
Anything that differs from your standard terms.
Approve, edit or reject in one step, with a short reason when they reject.

Building it with the tools you already have

You rarely need new software for the review step. Drafts can sit in a shared mailbox's drafts folder, quotes can be saved in your ERP or CRM with a draft status, and a short message in Teams or Slack can point the reviewer to each one. What matters is that every draft, approval, edit and rejection is recorded.

When it's safe to loosen it

Use the approval record to decide. For each type of work, track how often drafts are approved without edits. Where that stays high and the cost of a mistake is small, such as a repeat order of standard items at list price, you can let the agent release within limits you set. Keep checking a sample of what it releases.

Red flags

The agent sends from a mailbox with full send rights "just for now".
Reviewers approve without seeing the original request.
Nothing records who approved what.
Nobody can say which work the agent is allowed to release on its own.

Questions

Doesn't approving every draft cancel out the time saved?

Checking a prepared draft against the original request is quicker than reading the request, looking everything up and typing the reply from scratch. The agent does the reading and matching; the decision stays with your team.

Can an AI agent ever send emails or quotes on its own?

Only if you decide it should, within limits you set, for low-risk work where its approval record shows it is reliable. Keeping a person on every customer-facing message is also a sound permanent choice.

What should be logged?

The incoming request, the agent's draft, who approved or changed it, what they changed, and when it was sent. That record is how you find problems and decide when to loosen the rules.

Keep reading

Not sure where to start?

Request a free discovery session. We'll look at your work together and tell you plainly where AI would help — and where it wouldn't.