Check and send

Safety checks runs over the rendered batch (the actual messages, to the actual addresses) and returns SEND or HOLD. A HOLD is enforced by the code that sends, not by the button being greyed out, so it holds for a scheduled send at three in the morning exactly as it does for you at your desk.

The checks cover the things that are expensive to get wrong: a missing postal address, a footer link that goes nowhere, a batch that has already been sent, addresses on the do-not-contact list, leads in countries that require opt-in, a sending domain without SPF or DMARC.

Three limits sit outside the verdict and stop a send on their own: the email credits you have left, your email provider's own sending limit, and a suspension we place on a campaign by hand, usually over spam complaints.

They are computed over what is rendered. An empty or half-rendered batch is caught rather than passing vacuously. A check that nothing failed because nothing was there is the failure this was built for.

A campaign with a sending domain runs 29 checks. A blocking check holds the send until it is fixed; an advisory one is shown but does not stop it. Where a check can do either, the table says when it blocks.

Until a sender address is set, or while DNS cannot be reached, the five domain checks (SPF, DKIM, DMARC, Replies reach you, Name matches domain) are replaced by one, Sending domain, which blocks when no address is set and only advises when DNS is down. That makes 25.

The Send page writes the batch and sends it. It was called Review & send until October 2026; the reviewing happens on Templates and Safety checks. Every email is written for its lead and checked before anything can go out — the preview, which runs by itself (there was a Preview button until October 2026, and a Dry run button before that). There is no template to pick: each lead gets the template set for its industry, and the Template filter under Which emails shows how many are waiting for each, to narrow a send to one. The preview is not decorative: the gate reads the rendered batch, so a send without a fresh one is refused rather than guessed at.

Send a test sends one email to an address you type, with the template you pick, through the same provider. It is free: it uses no credit and stays out of every chart and total. A campaign can send up to 20 test emails a day.

After a lead search or a CSV import finishes, or a template is published, the preview runs by itself, so the batch is already written when you open the Send page. It needs an email provider connected, since the preview renders with its settings, and a published template set for an industry; the search's finish card points you to whichever is missing. It uses the panel's defaults: every template, each to its own industries, the whole queue. Narrow the send, to one template or a city, and the batch is written again a moment later, so the checks read the batch you will actually send; the same happens when you open the page with no batch, or after connecting a provider. Once you have fixed something a safety check flagged, press Check again in the Send card. Nothing is sent until you press Send or a schedule runs.

Send sits in the Send card's header, and one press sends. It stays off until sending would go through, so you are never told no after pressing it: the card's description says why it is off and links to the fix — wait for the batch, fix a safety check and check again, connect a provider, add a From name, get credits. If you change the template, city or limit, the batch is written again before Send turns back on. On the Follow up tab it stays off while a safety check that holds follow-ups is failing, such as a missing postal address.

When a send you started finishes, the next batch is written by itself with the same settings, so sending more is pressing Send again. For an hour after, the Send card's description also offers Schedule this send: it opens the schedules with that send's templates and limit filled in, so you pick the days and time and add it. A schedule cannot narrow by city or by when leads were found, so if your send did, the form says so above it.

Three things hold a batch back, and they are separate: a send stops at whichever it reaches first.

A new sending domain has no reputation yet, and mailbox providers judge it by how fast its volume grows. Raise each run's limit — Most per run, on a schedule — one step a week, and only after a clean week.