AI SDR human in the loop, explained: what the agent should do alone, what needs approval, what an approval card should show, and which replies to escalate.
A human-in-the-loop AI SDR does the research, list building, drafting, sending and reply sorting itself, but a person approves who gets targeted, what gets claimed and when a campaign launches. Anything outside those approved limits, such as a pricing question, a legal mention, an interested buyer or a deliverability spike, stops and comes back to a person instead of going out.
Human in the loop for an AI SDR means the agent does the volume work on its own, but a person approves the decisions that can hurt you: who gets emailed, what gets promised, and when a campaign goes live. Everything else about the setup follows from where you draw those lines.
The question matters more every quarter. In July 2026 Gartner repeated its prediction that AI agents will outnumber human sellers 10 to 1 by 2028, while fewer than 40% of sellers will say those agents improved their productivity (Gartner, July 28, 2026). More agents with no clear approval rules is how you get what Gartner's analyst calls agent sprawl: lots of activity, not much impact.
An AI SDR is human in the loop when a person has the final say before anything risky reaches a buyer. In practice vendors offer two modes. Approval or copilot mode holds drafts in a queue until someone approves them. Autopilot mode sends without waiting. Reply.io documents both for its Jason AI agent, which is a fair picture of how the market splits (Reply.io).
We think both extremes are wrong for most teams. Approving every single email doesn't survive real volume, and pure autopilot hands your domain and your brand to software that can't tell when it's wrong. The middle position is the one we'd defend: approve each campaign once, with enough detail to judge it, and make the agent stop and ask whenever it steps outside what you approved.
An AI SDR should handle any task where a mistake is cheap, easy to spot and reversible. That covers most of an SDR's week. A mediocre draft shows up in the sample; a few bad rows get caught by verification and bounce limits. None of it needs a person signing off one item at a time.
Anything that is a business decision rather than a task needs a person's approval: the segment you target, the claims and offers in the copy, and the launch itself. These are the choices where one wrong call repeats across hundreds of emails before anyone notices, so they get approved once, deliberately, before the first send.
Practitioners describe the same failures over and over. Write-ups of r/sales postmortems mention emails addressed to people who had left the company and copy naming product lines that had been retired two quarters earlier. Sentiment is lukewarm at best: an analysis of 18 Reddit threads on AI SDRs coded 32% of them negative and 46% mixed or conditional. Each of those mistakes is a targeting or claims problem. A person looking at the segment and the evidence before launch would have caught most of them.
An approval card should show the approver exactly what will happen, in enough detail to say no. That means the segment and its size, who is excluded, the evidence behind each personal claim, real sample emails, the sending limits and the conditions that pause the campaign. A one-line summary written by the agent is not an approval card.
The tray.ai team makes the same point about agents in general: approvers often see the model's summary of its plan rather than the action itself, and a request nobody answers should never default to proceeding (tray.ai). Here's a worked example of a card we'd be happy to approve. The company and numbers are illustrative, not a customer.
Campaign: Heads of RevOps at 50–200 person B2B SaaS companies in the UK that posted a RevOps or sales ops job in the last 30 days.
List: 412 contacts, all verified. Excluded: current customers, open opportunities, anyone emailed in the last 90 days, two competitor domains.
Angle: new hire ramp. No pricing, no discount, no customer names.
Evidence shown per email: the job post URL and date the opener refers to.
Samples: 5 full emails, picked at random, with the step 2 and step 3 follow-ups.
Limits: 3 steps over 10 days, 30 emails per inbox per day, working hours only.
Stops automatically if: bounce rate passes 2%, any spam complaint, or a reply mentions legal, security or pricing.
If nobody approves within 48 hours: the campaign stays on hold.
Notice the random samples. If the agent picks its five best drafts, you're approving its showcase, not its output.
An AI SDR should escalate any reply that shows buying interest or asks for a commitment, and any event that threatens deliverability or an existing relationship. Escalating means the agent stops that thread, holds anything queued for that account and hands a person the full context. It doesn't answer first and flag later.
| Trigger | Why a person decides | What the agent does meanwhile |
|---|---|---|
| Positive reply or meeting request | The relationship starts here; tone and timing matter | Stops the sequence for that contact and passes the thread with research notes |
| Pricing, discount or contract question | Prices and terms are commitments, not copy | Holds the reply; never quotes a number it wasn't given |
| Security, legal or data-protection mention | Wrong answers create real liability | Holds the reply and pauses other contacts at that company |
| Competitor named or comparison asked | Easy to make claims you can't support | Holds the reply |
| Existing customer, open deal or partner | Someone already owns the relationship | Removes the contact before sending; alerts the owner |
| Angry reply or "how did you get my email?" | Complaints feed spam reports | Suppresses the contact immediately and flags it |
| Spam rate heading toward 0.1% | Google asks senders to stay below 0.1% and never reach 0.3% (Gmail sender guidelines) | Pauses the campaign until someone reviews it |
| Bounce spike | Bad data hurts every inbox on the domain | Pauses sending; a person checks the list source |
For the deliverability rows, our post on deliverability guardrails for AI-sent email goes into the thresholds in more detail.
You stop rubber-stamping by keeping the approval queue small and making every item easy to check. People who approve a long stream of mostly-fine outputs stop reading them. That isn't laziness. It's one of the best-documented findings in human factors research.
Parasuraman and Manzey's review of the research found that automation bias shows up in experts as well as novices, can affect teams as well as individuals, and is not prevented by training or instructions (Human Factors, 2010). The EU AI Act writes the same concern into law for high-risk systems: Article 14 says the people overseeing a system must stay aware of the tendency to over-rely on it and be able to halt it (EU AI Act, Article 14). Sales outreach isn't on the Act's high-risk list, but the design lesson carries over.
Run the numbers on per-email approval. Five mailboxes at 40 emails a day is up to 200 emails a day. If a careful read takes about a minute (our assumption; it's longer if you check the sources), that's over three hours of reading every working day. Nobody keeps that up, so the approvals quietly become clicks. Compare that with reading one card and five random samples per campaign, plus a handful of escalated replies. That's work a sales lead can do properly, so it gets done properly.
Approving every email makes sense when the volume is small and each email is expensive to get wrong. Top-tier target accounts, a new market where you haven't seen the agent's output yet, and regulated buyers in finance or healthcare all qualify. In those cases the reading time is worth it and the queue stays short enough to read.
We'd also go back to full review for the first few days after any big change: a new segment, a new offer or a new data source. Once a week of samples looks right, drop back to campaign approval plus escalations. What we'd skip is permanent per-email review on a proven, low-risk campaign. It costs hours and, per the research above, doesn't buy as much safety as it feels like it does.
And there are campaigns we wouldn't run through an AI SDR at all: outreach to a handful of strategic accounts where a founder should write personally, or anything that relies on a sensitive trigger such as a layoff or a funding problem.
Outbound Labs is built around one rule: you approve every campaign before anything sends. Six agents split the work (Researcher, Strategist, Prospector, Writer, Sender and Closer), and the campaign they put together waits for your approval before the Sender touches an inbox.
Some guardrails are fixed. Each inbox sends up to 40 emails a day, and sending pauses automatically if the bounce rate passes 2%. Plans include 5 or 25 warmed mailboxes depending on the tier; AI SDR pricing and our comparison with 11x show how that stacks up against more autonomous tools. If you want to see the approval flow on your own list, read how the AI SDR works or start the free trial: 750 emails, no card.
SDR agency vs in house SDR compared on speed to meetings, control, management load, contracts, meeting quality and attrition, with a switch-over checklist.
Eathan Brown · 2 Nov 2026 · 8 min readA Lindy AI alternative for every job: Zapier Agents, n8n, Gumloop, Relevance AI, Apollo, Salesforge, AiSDR and Outbound Labs, with a cost for 500 prospects.
Eathan Brown · 1 Nov 2026 · 9 min readAutonomous SDR defined: what the label means, the autonomy levels from drafts to autopilot, how it differs from an AI SDR or sequencer, and a 4-question test.
Eathan Brown · 31 Oct 2026 · 5 min readA go to market strategy for startups that starts with outbound: when it fits, how to pick the first channel, the capacity maths and a 30/60/90 plan with stop rules.
Eathan Brown · 31 Oct 2026 · 9 min read