The published failure mode of this category is not that the writing was bad. It is that the writing went out.
A large share of AI sales development deployments are cancelled inside the first year, and the reason given is consistently the same: messages reached customers that nobody had read. Once that has happened once at a company of six people, the tool is gone, and the argument that the next message would have been fine is not an argument anybody wants to hear.
Every serious competitor moved toward autonomous sending this year. One of them used to sell itself as artificial intelligence for sales development representatives rather than an artificial sales development representative, and has since moved to autopilot messaging. So the gate below is more differentiated than it was when we wrote it down, not less.
What the gate actually is
It is a check in the code, in a specific place, and it is worth naming the place.
The dispatcher takes an approved draft and a set of gates in a fixed order. The very first thing it does, before it looks at anything else, is refuse a draft that was not approved. The only caller anywhere in the tree that passes an approval is the authenticated endpoint behind the Dispatch Queue, reached by a signed-in person clicking on that exact draft. No cron reaches it. No agent reaches it. No scheduled path reaches it.
The second gate is a per-tenant switch that is off on a new account and stays off until somebody turns it on. A missing setting reads as off. A setting we failed to read reads as off. With it off, approving a draft records the attempt and reports it as held, so you can run the whole thing for a month and read everything it would have said before a single message leaves.
What that costs
A gate is a ceiling. An autonomous sender does not have one, and if raw volume at the top of the funnel is the only thing you are short of, that ceiling is a real cost and you should weigh it honestly. We say so on our own comparison pages.
What you get for it is that the program is auditable in the direction that matters. Every approval is recorded. The thing you show a customer is a thing you read first.
And now it actually sends
Until recently the gate had an embarrassing corollary: approving a draft did not send it either, because no verified send path sat behind the dispatcher. A seller approved a message and then pasted it into their own mail client.
That is fixed. Email now goes out through the Google account you connect, so your address is the From line, your domain carries the reputation, and the reply lands in a thread you own. The gate is unchanged. It says a person clicks. It never said the click should lead nowhere.