Human-in-the-loop approval
Human-in-the-loop approval is a step where a person approves, edits or rejects what an automation prepared before it acts, like sending an email or changing a record. The automation gathers the details and writes the draft. A person makes the call that is hard to take back, so nothing goes out without their say.
Why it matters
Automation is good at gathering details and writing a first draft. It's bad at noticing when a reply promises a price nobody agreed, or when a lead needs a softer tone. A careless reply can cost you the lead, and an email can't be unsent. An approval step keeps the speed and puts a person on the moment that's hard to take back.
What I keep with a person, and why:
- Anything sent to a lead or client, because it goes out in my name and can't be unsent.
- Prices, dates and scope, because a number in writing is hard to walk back.
- Changes to records other people rely on, like the deal owner, because a wrong edit spreads to every tool that copies it.
- Anything flagged as risky, so a person decides what to do with it.
An example
An illustrative case. A lead emails a small agency asking whether it can start a site rebuild next month and what it would cost. The automation checks whether this lead has written before and drafts a reply that asks two scoping questions and leaves the price out. The draft arrives as a card in the owner's team chat. She changes one line, presses approve, and the reply goes out once and gets logged.
How a system handles it
In the inquiry desk I built, every draft arrives as a card in Telegram, and nothing goes out without a press. Replying to the card revises the draft, and a risky email gets flagged for a person to decide. One approval sends one email: on 2026-09-07, with the desk running on SignalNine's own inbox, five approve presses in 2.2 seconds sent one email. A failed step sends an alert, but an email the junk screen sets aside does not send one yet.
Questions
Does human-in-the-loop mean someone has to watch the automation all day?
No. The automation does its work on its own and stops only at the step that needs a person. The card waits until someone gets to it, from a phone or a desk, and everything before and after that press runs by itself.
Doesn't an approval step slow things down?
A little, and that's the trade. The automation does the slow part, gathering details and drafting, so what's left for the person is a read and a press. From a phone, that can happen right away, wherever they are.
Related
- How do I approve email replies from Slack before they go out?Approving email replies from Slack, Telegram or Google Chat: what the built-in apps do, where an approval loop breaks, the send-once rule, and what I'd pick.
- Send-onceSend-once means one approval sends one email, however many times the button gets pressed. Why duplicates happen and how a system keeps the rule.
- Speed to leadSpeed to lead is the time between a lead reaching you and a real reply going back. Why it matters, an example, and how a system shortens it.
- A drafted reply to each lead, approved from my phone before it sendsAI drafts replies to lead emails that pass a junk screen, from my business facts. Risky asks get flagged, and nothing sends until I approve it on my phone.