SMS campaigns Live

How SMS outreach works in Landing Zone — registered numbers, the eligibility pipeline that screens every batch, and automatic opt-out handling.

Open this screen in Landing Zone →

SMS campaigns send text messages in reviewed batches from your Landing Zone phone numbers. SMS is the strictest channel in the platform: it generally carries stricter consent, carrier, and registration considerations than ordinary commercial email, and Landing Zone enforces a stricter sending pipeline to match.

How it works

Registered numbers

Sending SMS at scale requires A2P 10DLC registration. The Trust Center tracks your registration status — you register with the carrier registry externally, enter your Brand and Campaign IDs, and SMS sending gates on approved status. See the A2P 10DLC setup guide.

The eligibility pipeline

Every SMS sent through batches, campaigns, or automations passes each contact through the same checks before it can go out:

  • Verified consent. Batch and campaign SMS only go to contacts whose SMS consent status is VERIFIED, with recorded proof. Imported and skip-traced contacts default to UNVERIFIED until an opt-in is recorded.
  • 30-day cooldown. A phone that received an outbound SMS in the last 30 days is excluded — unless the contact replied after your last outbound message. See repeat-contact cooldowns.
  • Suppression. Contacts on the workspace suppression list are excluded.
  • Line type. Phone verification classifies each number as MOBILE, LANDLINE, VOIP, or UNKNOWN, and batch eligibility uses the result. Batches containing unverified line types ask you to confirm "Send to unverified numbers?" before sending, and your acceptance is timestamped.
  • Quiet hours. Sending respects quiet hours — by default 9 PM to 8 AM in the contact's local time.
  • Same-campaign rule. A contact already texted within the same campaign is excluded regardless of the 30-day window.

Excluded contacts appear in the pre-send preview with the reason for each exclusion, so you always see who is filtered out and why.

Opt-outs handled automatically

The first outbound SMS to a contact automatically appends "Reply STOP to opt out." When a contact replies STOP — or with a similar keyword or a free-form revocation — Landing Zone suppresses the number, sets consent to REVOKED, sends a confirmation reply, and records an audit entry.

When to use it

Use SMS for audiences whose consent you have verified and recorded. The pipeline is built around that expectation: see SMS consent for what counts as verified consent, and read cold SMS risk before considering any colder audience.

Limitations

  • The 30-day cooldown is fixed and not configurable.
  • The eligibility pipeline reduces risk; it is not a legal determination and does not make any message compliant. Audience, consent, content, and timing remain your responsibility.
  • A2P 10DLC registration happens outside the app — the Trust Center tracks status but there is no in-app submission flow.

Frequently asked questions

Why was a contact excluded from my SMS batch?

Open the batch's pre-send preview: every excluded contact is listed with the reason — consent not verified, cooldown, suppression, line type, or the same-campaign rule.

Does a reply make a contact eligible again?

An inbound message after your last outbound lifts the 30-day cooldown for that contact. The other checks — consent, suppression, quiet hours — still apply.