In SAGARIS, the AI agent cannot send an email: it can only propose one for a person to confirm. A reply the AI drafts waits in your inbox until someone sends it, unless an admin has armed Auto-Mode, which is off by default. What does send without a click per message is a running sequence, including the steps SAGARIS personalized for each contact, and a few confirmations and reminders listed below.
Checked against the SAGARIS product code on 25 September 2026.
Approval means different things on different paths, so here is each path on its own. The first two never send without a person. The rest can send without a click per message, and they are listed because leaving them out is how a page like this misleads.
The agent's tools that would email a contact, enroll one in a sequence or book a meeting are proposal-only. There is no send path behind them. The outbound switch and the suppression list are checked, then the tool returns a proposal marked as not sent, and a person has to act on it where sending actually happens. No autonomy level changes this.
When a contact replies, SAGARIS can draft the answer. The draft goes nowhere until a rep sends or schedules it, and the record keeps which person did.
Auto-Mode lets low-risk replies go out by themselves. It is off by default, only a workspace admin can arm it, and arming asks for confirmation. Even armed, a reply only sends by email or text, and only when the classifier is at least 80 percent confident and at or above the workspace's own threshold, the draft passes the quality check and makes no claim that cannot be verified, and the incoming message shows no sign of an attempt to hijack the model. LinkedIn replies never send themselves.
A contact enrolled in a running sequence gets its email and SMS steps on schedule without a click per message, including the steps SAGARIS personalized for that contact. LinkedIn, call, manual and task steps send nothing themselves: they put the work in front of a rep, and the sequence moves on if it is not done. An AI call step, which is off by default, is worked by the AI calling agent instead. Contacts reach a sequence in several ways, among them a person enrolling them, your own integration through the API, an enrollment rule someone created for buying signals, an inbound lead routed to a fast-track sequence, a won deal starting customer onboarding, and the Re-Engagement sequence SAGARIS manages for a contact who went quiet at the end of a sequence and later showed interest.
If a contact in a running sequence answers with an out-of-office that names a return date, the AI writes a follow-up and SAGARIS sends it on that date, sends a second a week later if there is still no reply, and then returns the contact to the sequence.
Someone who books through a SAGARIS booking link gets a confirmation, invitees can get reminders 48 hours, 24 hours and 1 hour before a meeting, and marking a meeting as a no-show queues a rescheduling email to the prospect. These are templates rather than AI-written text. When the AI receptionist books a meeting for a caller it recognizes, the confirmation goes out without a rep; for a caller it cannot identify, a rep approves the request before the caller is emailed.
A send that needs no click still has to get past these. Each one says what it covers, because a check described as broader than it is gives you nothing to rely on.
An opt-out is keyed on the email address and the phone number rather than on the contact record, so it survives an edit, a delete or a re-import, and a STOP by text also stops email. If the suppression list cannot be read, the contact counts as suppressed.
One switch holds a workspace's sequence email, SMS, LinkedIn steps and scheduled calls for twenty-four hours, then lifts on its own. An unreadable pause state counts as paused. Replies from contacts keep arriving while it is on.
In the code the switch is closed unless it is explicitly opened, and a committed contract test fails if the deployment config stops defaulting it to closed. It is open on the SAGARIS production service, because the product sends real email, so it is not what stands between your contacts and a send. The paths and checks on this page are.
Email from a SAGARIS-managed mailbox claims that mailbox's daily capacity in one atomic step before it goes, and if the claim cannot be granted, including on an error, the email waits. Sequence texts rotate across the workspace's approved numbers and skip one that has reached its daily cap.
An answer to this question is only useful if its edges are stated, so here are ours.
Launching a sequence is the approval for its schedule. After that, SAGARIS does not ask again before each email, including the ones it personalized for a contact. If you want a person to write or check every message, use manual or task steps instead of email steps: they give a rep the task and send nothing themselves.
Only an admin can switch it on, and the setting is stored, but the change is not written to the configuration audit trail, so the trail will not tell you who armed it or when.
No. The agent's tools that would email a contact, enroll one in a sequence or book a meeting are proposal-only, with no send path behind them. It returns a proposal marked as not sent, and a person acts on it where sending actually happens. No autonomy level changes that.
Not unless an admin has armed Auto-Mode. By default a drafted reply waits in the inbox until a rep sends or schedules it. Auto-Mode is off by default, only an admin can arm it, and even then it only sends low-risk replies by email or text that clear an 80 percent confidence floor, the workspace's own threshold and the quality and claim checks. LinkedIn replies never send themselves.
No. Launching the sequence is the approval for its schedule, and its email and SMS steps go out on time without a click per message, including the steps SAGARIS personalized for each contact. LinkedIn, call and task steps send nothing themselves; they give a rep the work.
Yes. A manual or task step creates a task for a rep and sends nothing itself, and a LinkedIn step puts the message on the rep's list rather than sending it. The sequence does not wait forever: if the task is still open a day after it is due, the step closes as not done and the sequence moves on.
The workspace emergency pause holds sequence email, SMS, LinkedIn steps and scheduled calls for twenty-four hours and then lifts on its own. If the pause state cannot be read, SAGARIS treats the workspace as paused rather than sending.
Partly. A sent draft records the rep who sent it, and an approved or rejected agent action records who decided and what happened. Arming Auto-Mode is not recorded in the audit trail today. The audit trail page lists what is recorded, who can read it, and what it does not cover.
Next door