Broadcasts

A broadcast is one message to a whole list or audience, sent now or on a schedule. You design the content once, pick who receives it, and send. Use a broadcast for one-off sends: newsletters, product launches, and policy updates. A broadcast is those two things together: content written the way a is written, addressed to a .

​

Which one to use

Broadcasts and both send to many people, and the difference is what starts the send. Sending the same message to a group at a chosen moment is a broadcast. A user’s action that should send a message or start a sequence is a journey.

​

How it works

​

From draft to sent

A broadcast moves through three states:

• Draft: created but not yet sent or scheduled.
• Scheduled: queued for a set time. You can reschedule or cancel, but the content is locked. To change the message, cancel, edit, and schedule again.
• Sent: delivered, with .

Each broadcast sends on a single channel. To reach the same group elsewhere, create a separate broadcast. Recipients are a you curate by hand, or an Courier keeps current from rules.

​

Its content

You write a broadcast’s content in the same editor a uses, and it is stored as the same document. Variables resolve from each recipient’s profile, so one broadcast reads differently for every person.

​

Limits & behavior

• Console or API. Build a broadcast in the console, or drive the whole flow through the : create, write content, then send or schedule.
• One channel per broadcast. A broadcast cannot span channels. Make one per channel.
• Content locks when scheduled. To edit a scheduled broadcast, cancel it, edit, and reschedule.

​

FAQ