One queue
For review holds field updates, email drafts from sequences, automations and API clients, automation escalations and proposed ICP versions.
Field updates, email drafts and proposed changes wait in For review. You approve the exact content, or it goes nowhere.
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
For review holds field updates, email drafts from sequences, automations and API clients, automation escalations and proposed ICP versions.
Every item explains why it is waiting. A field update shows the old and new value side by side, with the sentence it was read from.
An approval is bound to the exact content. If a draft changed after you opened it, the approval is refused; in a batch, that draft is skipped.
04
After Approve & send you have 10 seconds to undo. Reject sends nothing.
A message leaves at most once, and only if a person approved that exact message. In a sequence a person approves each message; enrolling a contact approves nothing.
Enforced
The send gate is a trigger on the outbox. Nothing in the app, and no agent, can queue a message around it.
No. An agent can’t approve a draft; only a person can. The database refuses the request.
Yes. A draft that changed since you opened the list is skipped, so a batch never approves something you didn’t read.
Yes. Edit changes the text while the draft is still waiting, and your approval then covers the edited version.
Nothing is sent and nothing changes.
Owners, Admins and Members. A Viewer is read-only.
Not for every account yet. What works today says where each part of the product stands.
Create an account, import a CSV or a few emails, and read the first proposals with their quotes. An import is one change you can undo.
Early access. No payment details are asked for.