Email and automation
Sending your first campaign
Verification, sender, double opt-in and the suppression list — what delivery depends on.
Updated
Before anything goes out
- 1Verify your email with the link sent at registration. Until an owner of the organisation has confirmed an address, no campaign can be sent.
- 2Settings → Email: the sender name and address. Mail goes out through your SMTP provider — domain authentication (SPF, DKIM) is configured there.
- 3A template: Templates → New. The variables {{first_name}}, {{last_name}}, {{full_name}}, {{email}} and {{company}} are safe; a variable nothing fills in goes out empty.
To whom
A static list or a dynamic segment (a saved filter). A segment's members are resolved when the campaign goes out; the preview runs the same predicate as the send, so the number you see is the number that goes.
Only subscribed recipients get mail, and suppressed addresses — unsubscribed, bounced, complained — are skipped even if their record says otherwise.
Double opt-in
Switched on for a form, the submitter is not subscribed until they click the confirmation link. The link lives seven days. The confirmation goes into the consent history with IP and browser — which is what a complaint or a regulator asks for.
The send
The Send button does not send: it expands the campaign into rows — so you learn at once if the list is empty or the monthly quota full — and a worker sends them, fairly across companies. The campaign page shows queued, sent, opens and clicks.
A failed send retries after 10, 20 and then 40 minutes, then stays failed. A mail server that is refusing, retried every thirty seconds, turns a short outage into a long one.