Using Galactic

Safety checks

Twenty checks over the batch that is about to leave, and one verdict that can stop it.

The verdict

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.

Safety checks: twenty checks over the rendered batch, ending in one word.

What it looks at

The checks cover the things that are expensive to get wrong: a missing postal address or unsubscribe link, a batch that has already been sent, addresses on the do-not-contact list, a daily cap already spent, a campaign suspended for 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.