Broadcasts
Let the bot reach out first.
Send a personalized campaign across twelve channels from one composer — WhatsApp templates, SMS, email, in-app and more. Rylvo enforces each platform's cold-send rule, caps your throughput below the provider's ceiling, honors unsubscribes and frequency limits, and records what happened to every single recipient.
12
delivery channels
5
composer steps
9
recurring cadences
4
audience sources
The composer
Five steps, and the rules are checked before you send, not after.
A broadcast is your bot reaching out first. Rylvo walks the audience, the channels, the message, the schedule, and the review in order — and refuses the combinations the platforms would reject anyway.
BROADCASTS / SPRING RESTOCK
STEP 05 · Review1,204 recipients
Template · order_update_v3
1,880 recipients
Open send · 600 / min
SMS
312 recipients
Opt-in verified · 60 / min
Telegram
0 recipients
Blocked — user must /start first
Frequency cap: 3 / recipient / 7 days
Choose who receives it
A broadcast targets a saved Audience segment, an uploaded list, everyone who has chatted with the bot, or an explicit set of recipients you picked.
A segment is resolved from its materialized member index when the broadcast fires — not frozen at the moment you composed it — so a scheduled send reaches who qualifies then, not who qualified last week.
Channel rules
Every channel has a rule. We enforce it for you.
These are the platforms' rules, not our preferences. Telegram users really do have to start the bot first, WhatsApp really does need an approved template, and Twilio really does require consent. Ignoring any of them is how an account gets suspended.
Open send
600 / min
In-app
Open send
1,200 / min
Approved template required
4,800 / min
SMS (Twilio)
Prior opt-in required
60 / min
LINE
Must have added your account
120 / min
Messenger
24-hour window or message tag
120 / min
Instagram DM
24-hour window or message tag
120 / min
Slack
Connected workspace only
60 / min
Microsoft Teams
Connected tenant only
60 / min
Telegram
No cold-send — user must /start
30 / min
Web Widget
No cold-send — needs a live session
120 / min
Discord
No cold-send yet
30 / min
Caps are messages per minute, set below the documented platform ceiling so a burst of retries cannot trip an account-level throttle. An operator can lower a cap for one broadcast; nobody can raise it.
Consent and suppression
The message you don't send is part of the product.
Outbound messaging goes wrong quietly: one list sent twice, one person messaged five times in a week, one unsubscribe ignored. Broadcasts is built to make each of those a recorded skip rather than a send.
Rules come from the platforms
One rules table drives both the composer and the send runner, so what the UI allows and what the runner will actually dispatch cannot drift apart.
Unsubscribe is honored
A recipient who unsubscribes by email is suppressed for future broadcasts, and an admin can see and reverse the suppression list.
Frequency cap per person
Set a maximum number of broadcast messages one recipient can receive in a rolling seven days, enforced across every broadcast in the workspace.
Skipped, not half-sent
A missing template, a missing opt-in, or a recipient the channel cannot reach writes a skipped row with its reason instead of a partial send.
Segments arrive with their consent scope already applied
Broadcasts does not re-decide who consented — it reads the Audience record and then re-checks channel compatibility for each recipient at dispatch.
Delivery evidence
After the send, you can prove exactly what happened.
Sent, failed, and skipped are three different outcomes, and a gap between your recipient count and your sent count always has a stated reason attached to it.
A row per recipient
Every dispatch writes a delivery row — queued, sent, failed, or skipped — with the provider's message ID where the platform returns one, so you can reconcile against Twilio or Meta directly.
A record per firing
Each run stores what it sent verbatim, its per-channel tallies of sent, failed, and skipped, per-variant results for an A/B test, and a sample of errors for triage.
An entry in the audit log
Creating, scheduling, and deleting a broadcast land in the organization audit log with the member who did it.
Caps you can see
The settings view lists the effective per-minute ceiling for every channel, so an operator knows the throughput before the run rather than after a throttle.
A/B variants report separately
Recipients are split across variants by a deterministic hash, so the same person stays on the same arm — and the run reports each arm's sent, failed, and skipped counts on its own.
An upload stays with the broadcast
The rows you uploaded remain on the broadcast after the run completes, so History can show who was targeted — even when you chose not to save the list into your Audience.
Access and plans
Broadcasts is a Pro capability.
Reaching out to people first carries real regulatory and provider risk, so it sits behind a paid plan with an explicit per-bot cap rather than being available to any new signup.
Free
Not included
—
Lite
Not included
—
Pro
Included
20 broadcasts per bot
Team
Included
50 broadcasts per bot
Enterprise
Included
Unlimited
The per-bot cap is enforced where it matters
Broadcast limits are checked on the server at create time and again at dispatch, so the cap is a real boundary rather than a greyed-out button in the interface.
FAQ
What sends, what gets skipped, and why
The rules worth understanding before you point a bot at a list of real phone numbers.
Which channels can I broadcast on?
Twelve: Email, In-app, WhatsApp, SMS via Twilio, LINE, Messenger, Instagram DM, Slack, Microsoft Teams, Telegram, Web Widget, and Discord. Each carries its own cold-send rule, and three of them — Telegram, Web Widget, and Discord — cannot be cold-sent at all.
How do I get a recipient list in?
Pick a saved Audience segment, upload a CSV or XLSX, paste phones and emails one per line, or target everyone who has chatted with the bot. Uploaded rows stay on the broadcast unless you tick the option to also save them into your Audience.
Why does WhatsApp need a template?
Meta requires an approved business template to message someone outside the 24-hour session window. You author the template in Meta Business Suite; Rylvo pulls your approved catalog into the composer and sends the one you pick.
Can a recipient be messaged too often?
Set a frequency cap and a recipient cannot receive more than that many broadcast messages in a rolling seven-day window, counted across every broadcast in the workspace, not just the one you are composing.
Can I A/B test the message?
Yes. Add variant bodies alongside the base template. Each recipient is assigned a variant deterministically, and the run reports sent, failed, and skipped counts per variant.
Does Broadcasts guarantee compliance with SMS or WhatsApp law?
No product can. Rylvo encodes the platform and carrier rules it knows about — opt-in for SMS, templates for WhatsApp, session windows for Meta — enforces them at dispatch, and records what was sent. Your consent and messaging policy is still yours to run.
Let the bot speak first — without getting you banned.
Pick an audience, respect the channel rules, personalize the message, schedule it, and keep a per-recipient record of what actually went out.