Send to a segment, then answer the replies in the same inbox.
Broadcast handles campaign templates, scheduling, and delivery state – and the replies land in Channels, so a campaign does not create a second, unanswered queue.
Campaign tools usually stop at "sent". The operational problem starts there: replies arrive, nobody owns them, and the customer concludes the company only listens when selling.
Broadcast connects to the same conversation layer, so replies route to a team with an owner and an SLA like any other inbound message.
- SegmentAudience built from contact data and tags
- TemplatePer-channel templates with variables
- StateQueued, sent, delivered, read, failed per recipient
- RepliesRouted into Channels, not lost
Audience, message, schedule – and a stop button.
A campaign defines its audience from contact data and tags, its template per channel, and its schedule. Launch is a deliberate action with a preview, and a running campaign can be paused when something is wrong with the copy.
- Audience from contact fields, tags, and segments
- Preview per channel before launch
- Pause and resume a running campaign
- Per-recipient delivery state
Variables resolved at send time, not at design time.
Templates hold variables such as name, due date, or branch, resolved per recipient at send. Channels that require pre-approved templates show their approval state, so a campaign is not blocked at launch by a template nobody submitted.
- Variables resolved per recipient
- Approval state visible per template
- Language variants per template
- Opt-out line included by policy
Respect the clock and the cap.
Sending windows, per-recipient frequency caps, and opt-out are enforced by the sender. A campaign scheduled outside the window waits rather than barging in at midnight.
- Sending window per campaign
- Frequency cap per recipient
- Opt-out enforced before every send
- Retry policy for failed deliveries
What Broadcast covers
Audiences
Segments from contact data and tags.
Templates
Variables, approval state, language variants.
Scheduling
Windows, frequency caps, retries.
Delivery state
Queued, sent, delivered, read, failed.
Reply routing
Answers land in Channels with an owner.
Compliance
Opt-out and DNC enforced at send time.
Questions before the first campaign
Which channels can we broadcast on?
WhatsApp, email, and webchat announcements; voice campaigns live in the Voice module.
How do we avoid spamming?
Frequency caps, sending windows, and opt-out are enforced by the sender, not by the operator.
What happens to replies?
They route to Channels and are handled like any inbound conversation.
Can we test on ourselves first?
Yes, a test send to selected recipients before launch.
See this app running on your own data.
We install the suite on your server or in our cloud, then walk your team through the exact flow you described.