Send to the list you just cleaned.

One credit is one message that actually left the building. Credits are reserved when a campaign launches, so you always know the ceiling before you press send.

They come back. When a campaign settles, everything reserved but unsent — suppressed contacts, addresses that bounced before dispatch, recipients never attempted because you cancelled — is refunded automatically. You do not have to ask.

No. They are separate wallets with separate ledgers, and sending never spends the credits you bought for cleaning lists. The single exception is re-verifying a contact that has gone stale, which spends verification credits and tells you before it does.

Yes. Connect Amazon SES, Postmark, or any SMTP server — Zoho, Fastmail, your own box. Credentials are tested against the provider before they are stored, so a typo fails at setup rather than halfway through your first campaign. There is no shared pool, which is why your sending reputation is yours alone.

Five things: a domain you have verified by publishing three DNS records, a sender address on that domain, a connected provider, some contacts, and a template. The dashboard shows which of the five are still outstanding and links straight to each one.

Every message carries a one-click unsubscribe header, and suppression is checked on the send path itself rather than when the audience was built. Someone who opts out while a campaign is mid-flight is still skipped. The record survives even if you later delete the contact, so a re-import cannot make them mailable again.

That is the point of the two products sharing an account. Import a finished verification task directly — no export, no file. Only addresses the engine confirmed as deliverable come across by default, and duplicates collapse on the canonical form, so J.Doe+news@gmail.com and jdoe@gmail.com are one contact rather than two sends.

It resumes without re-sending anyone. Each recipient is claimed before dispatch, so a crash leaves a row either untouched or claimed, never "maybe sent". Where we cannot be certain a message went out, the recipient is marked unconfirmed and never retried — a duplicate email is a compliance problem, a missing one is an inconvenience.

Yes, and it cannot change what was already sent. Every save creates a new version, and a campaign pins the version it launched with. Editing today has no effect on a report from last week.

A list holds exactly the contacts you put on it and changes only when you change it. A segment is a saved question — "deliverable and scored above 80" — asked again every time you send, so it grows and shrinks on its own.

Both, and we are careful about what they mean. Opens fetched by a mail client rather than a person are counted separately instead of inflating the number. Click links resolve an internal id rather than carrying a destination in the URL, so your sending domain can never be used as an open redirect.

Not yet. The adapters for LinkedIn, X, Facebook and Instagram are written but publishing is not switched on, so today this is an email product. Nothing on any plan is charged for social, and this answer changes the day it ships.

There is no shared pool to send from. Connect SES, Postmark, or any SMTP server — Zoho, Fastmail, your own box. It is a real setup step before your first campaign, and it is the reason your sending reputation is yours rather than shared with strangers.

Apple Mail Privacy Protection fetches every image on delivery, so a large share of opens are machines. We count those separately and label them rather than folding them in to make a number look better. Replies are the only signal a mail client cannot fabricate.

Some report it and some do not. Where it is missing, every rate is quoted against messages sent instead, and the denominator is printed next to the number so you always know which one you are reading.

It can be archived — hidden, restorable, intact. But the report is the only record those messages exist, for you and for anyone who later asks. There is no button that destroys it.

Campaign credits and verification credits never mix. The one crossing is re-verifying a stale contact, which spends verification credits and tells you before it does.