Help topic
Sending safeguards, domain setup, pacing, and sender health.
A send plan is the pre-flight check showing who would get an email, who Deloosh is leaving out, and why, before you approve anything. It appears in the Workbench after Approve & draft , alongside the draft itself — read it as the "what will actually happen" description you are approving against.
A suppression is an address Deloosh will not mail because it bounced, complained, unsubscribed, or otherwise needs protecting from you. A send to a suppressed recipient is denied with the suppression code — and some suppressions can never be undone from inside the product, on purpose.
The pause breaker is the account-level stop switch for email activity: it holds sends until you explicitly resume. Pause all stops every send across your workspace immediately — not the current campaign, everything.
The sending-health light is the green, amber, or red dot at the top of the Vitals view that summarizes how mailbox providers are currently receiving your mail. It is the one number that can stop Deloosh from drafting: on red, the specialist refuses to draft and the assistant switches into incident mode.
Until your sending domain is verified, Deloosh blocks marketing and cold-outreach sends from it. The denial code is domain unverified, and the reason reads: "tenant {your workspace} has no verified sending domain (connected systems.email domain verified is not set)" .
Deloosh does not show an open rate as an engagement or performance metric because opens stopped being reliable evidence. It never uses opens for recommendations, decisions, triggers, segments, or sending-health assessments. When the assistant surface is available, you can still ask for the recorded open count on an email; Deloosh will disclose it with a mandatory inaccuracy warning.
Every send passes one final safety battery immediately before it goes out, and any single failed check stops it. The block names itself: you get a failed check code and a plain reason, both of which appear below with what to do about each.
An email-suspended account cannot send anything at all — every send is denied with tenant suspended, and the reason carries the recorded explanation: "tenant {your workspace} is email-suspended: {reason}" . This is the broadest stop in the send path: it is checked before any per-recipient rule, so it blocks every send type and audience. Drafting and planning remain available.
The same email never goes to the same person twice. Deloosh records every send against the specific draft it came from, and a second attempt with that same draft and recipient is denied with ledger dedup: "already sent artifact {draft} to {recipient} for tenant {your workspace} — duplicate send blocked" .
Deloosh counts how many campaign emails each person has received from you in the last 30 days, and it protects them at two levels: a soft cap that coaches you (around 4 by default) and a hard ceiling that blocks the send (around 8 by default). The hard ceiling denies with frequency hard ceiling.
The live platform marketing cap limits how much marketing mail one workspace can send in a month (5,000 by default). It denies with within cap: "tenant {your workspace} is at its monthly send cap: {used}/{cap}" . A separate plan send limit is designed but not currently enforced.
A recipient dossier is one person's history with you, shown inside the send plan: every message you have sent them, what happened to it, and anything that suppresses them. It is how you check who you are actually about to mail before you approve.
Every send plan includes an advisory pacing projection. It calculates a safe-send-by result, checks whether the deadline is feasible, and recommends split or move deadline when the arithmetic does not fit.
Deloosh will not send campaign email to role accounts — shared, non-human addresses like noreply@, postmaster@, and abuse@. The denial code is list quality, and the reason is exactly: "{recipient} is a non-human role account" .