Broadcasts

A broadcast sends one message to every contact carrying a tag, as N individual texts. Recipients never see each other, and merge fields personalize each body.

Merge fields

{{name}}, {{first_name}}, {{phone}}, {{field:company}}, resolved per recipient at send time, so a contact edit made after scheduling still lands. Unresolvable fields render as empty, never as the raw tag.

Opt-outs are enforced per recipient

Every recipient passes the full send pipeline independently. Contacts who replied STOP are counted in skipped_opt_out; they are never texted and never silently dropped from the math.

Scheduling and progress

Pick a future time to schedule; leave it blank to send on the next queue flush (within a minute). The broadcast page shows sent / total live, and a broadcast.complete webhook event fires when the last job settles.

Limits

Up to 2,000 recipients per broadcast. Each send counts against your normal message quota and billing; a broadcast is exactly N messages.