Repeat-contact cooldowns

How Landing Zone's 30-day SMS cooldown works: where it applies, what counts as a reply, and what happens to blocked contacts.

Updated 2 min readMaintained by Landing Zone

Landing Zone restricts sending another SMS to a contact who was already texted within a 30-day period, unless that contact has replied. This limits repeat-contact pressure on people who have not engaged — a common source of complaints, opt-outs, and carrier filtering.

Where the rule applies

The cooldown is part of the SMS eligibility pipeline used by batches, campaigns, and automations. Any SMS generated through those paths is subject to it. It does not block individual manual replies you send from the unified inbox in an existing conversation.

How it works

  • A phone number that received an outbound SMS in the last 30 days is excluded from new batch, campaign, and automation sends.
  • What counts as a reply: any inbound SMS from that number received after your last outbound message. Once a contact has replied, the cooldown no longer excludes them.
  • A separate, stricter rule also applies: a contact who was already texted within the same campaign is excluded from further sends in that campaign regardless of the 30-day window.

Can it be configured?

No. The 30-day window is currently fixed and cannot be changed by workspace administrators. (Test mode with designated test contacts bypasses it so teams can safely test sends to themselves.)

What happens when a message is blocked

Blocked contacts are excluded before the batch sends, not errored after. The batch preview shows a cooldown exclusion count with details — the last outbound date, days remaining, and the prior batch involved — so you can see exactly who was held back and why. The exclusion appears in the preview tallies; it is not written as a separate per-contact entry in audit history.

The cooldown reduces repeat-contact risk. It does not evaluate consent, content, or the many rules that govern texting.