Approval that binds
Letting software draft email is easy. Three things have to be true before you let anything send.
Updated · 2 min read · Fonsent
In early access today. The AI model isn’t switched on yet. Field updates come from built-in rules, which pick up only sentences that state a value outright. An approved email is held in an outbox and isn’t delivered yet. What works today
Letting software draft email is easy, and useful. Letting it send is where teams get hurt: a wrong price to the wrong contact can’t be recalled. “A person approves it first” sounds like the answer, and it is, as long as the approval means what people think it means.
Three ways approval fails
- The approval covers a template, not a message. You sign off a sequence, and every contact then receives text that nobody read.
- The content changes after the approval. You approve a draft, something regenerates it, and the new version goes out under your name.
- The message goes twice. A retry, a race or a second click sends the same email again.
None of these is exotic. Each is what happens by default when approval is a flag on a record rather than a decision about a specific piece of text.
Bind the approval to the content
In Fonsent an approval covers exactly what you read. If the draft changed after you opened it, the approval is refused. Approve several at once and any draft that changed since you opened the list is skipped, so a batch can never approve something you didn’t see.
You can still edit. A draft can be changed while it is waiting, and the approval then covers the edited text.
Send once, per message
Nothing customer-facing leaves unless a person approved that exact message, and it leaves at most once. The rule is enforced where messages are queued, in the database, so no part of the app can go around it.
It also applies inside automation. In a sequence a person approves each message. Enrolling a contact approves nothing.
Leave a short way back
After you approve an email you have 10 seconds to undo it, which is long enough to catch the wrong recipient. Rejecting sends nothing. Once an email has gone, the history says so: a sent email is never shown as undone.
Decide who may approve
- People, by role: Owners, Admins and Members can approve. A Viewer can’t.
- Not the agent. An agent can’t approve a draft; only a person can.
- Not your integrations either. A request made with an API key or through the MCP server is treated as an agent’s request.
Email delivery isn’t switched on in production yet. The approval rules are in place; what works today has the current state.
Approval is a small ceremony. It is worth making it mean something. See the queue in the product.