Batches Live

A batch is Landing Zone's unit of outreach: one reviewed send to a defined set of contacts. Email and SMS both use the same batch engine, so once you understand the lifecycle here, you understand how everything in Batches sends.

How it works#

Draft#

Every batch starts as a draft — the audience you chose plus the template it will send. Nothing goes out at this stage, and a draft you no longer need can be discarded.

Preview and eligibility#

Before a batch can start, Landing Zone builds a pre-send preview: who will receive the message, and which contacts are excluded, with the reason for each exclusion. For SMS batches the eligibility checks include verified consent, the 30-day cooldown, the suppression list, line type, and quiet hours. Cooldown exclusions appear as a tally with details — the last outbound date, days remaining, and the prior batch. See repeat-contact cooldowns for the exact rules.

Approve and start#

A batch never sends on its own. Someone on your team approves and starts it, and the send loop then works through the eligible recipients. SMS sending respects quiet hours — by default 9 PM to 8 AM in each contact's local time.

Pause, resume, stop, or discard#

While a batch is sending you can pause it and resume later, or stop it entirely. Drafts can be discarded. See pause or stop outreach for when to use each control.

Campaigns and results#

Campaigns group related batches so a multi-touch effort stays organized. They also add their own rule: a contact already texted within the same campaign is excluded from later SMS batches in it, regardless of the 30-day window. Each batch has its own drill-down, and the Dashboard rolls results up across sends.

When to use it#

Use a batch any time you message more than one contact — cold or warm, email or SMS. One-to-one conversations belong in the unified inbox instead. Automations use batches too: they generate drafts that wait for your review, then follow this same lifecycle.

Limitations#

• The 30-day SMS cooldown is fixed — it cannot be configured or shortened.
• Cooldown exclusions are shown as a preview tally, not as individual per-contact audit-log entries.
• Eligibility filtering is a product control that reduces repeat-contact risk. It is not a legal determination and does not confirm that any message is compliant — audience, consent, content, and timing remain your responsibility.

Frequently asked questions#