Launch Batch SMS

Overview

Batch SMS is designed for controlled scale, because one validated message strategy can be applied to many recipients with shared scheduling and compliance checks. When audience data is clean and line settings are correct, the platform can dispatch large sends with fewer manual interventions.

How it works

• The workflow validates outbound line readiness, recipient file structure, and launch timing before dispatch, which reduces avoidable delivery failures. Structured setup matters more in bulk SMS because small data errors multiply quickly at scale.
• Suppression logic is enforced during execution, so Do Not Call entries are automatically skipped without manual filtering. This keeps compliance consistent even when source files change between launches.

Important fields

• phone_number column: Required header in your CSV file.
• Messaging pathway: Set per line under Phone Numbers → Messaging Settings.
• Schedule: Optional future send time for the batch.

Tips

• Good to know: testing with a small CSV first exposes formatting or content problems early, when fixes are still cheap and low risk.

Batch Setup

Batch Setup creates operational context before sending, so each SMS wave can be tracked and attributed correctly in history views.

Set batch identity, then upload recipients in the Audience step.

• A clear batch name and a configured outbound line are selected first, establishing identity before recipient import begins. This ordering improves traceability once multiple campaigns are running in parallel.
• Batch Name: Shown in SMS History.
• From Number: Outbound SMS line.
• Good to know: consistent naming conventions make post-send performance analysis much faster across campaign waves.

Upload Recipients

Upload Recipients determines who receives the message, so file integrity checks happen before launch controls are applied.

Resolve any file issues, then configure launch timing.

• The importer validates required columns like phone_number and confirms usable row counts before continuing. Early detection of formatting issues prevents silent delivery drops during execution.
• phone_number: Required CSV column header.
• Good to know: start with a small sample file to verify formatting conventions before loading full production audiences.

Launch Controls

Launch Controls sets send timing strategy, which affects engagement windows, staffing coverage, and downstream support load.

Choose timing, then confirm final configuration in Launch Summary.

• You can dispatch immediately or schedule for a future window, and that timing choice is applied to the whole batch. Planned timing usually improves response handling compared with ad hoc sends.
• Schedule: Optional future send time.
• Good to know: scheduling during business-relevant hours often improves reply quality and reduces complaint risk.

Launch Summary

Launch Summary is the final safeguard before bulk dispatch, so audience size and messaging context are reviewed together.

Launch the batch after totals and timing align with your rollout plan.

• The summary consolidates line, recipient totals, and launch timing into one confirmation surface. This final validation catches mismatched assumptions before messages are sent at scale.
• Recipients: Ready rows from CSV.
• Good to know: compare summary counts with your source CSV to catch filtering or import drift before launch.

Next step

Run a pilot batch, validate delivery behavior, then schedule the full audience send.