Comment PLAN on a Reel and the program link arrives by DM.
Reply to a story, leave an email, get the routine guide.
Send BOOK and pick a free time without leaving the chat.
An ad opens the DM, two quick questions pick the right course.
Comment AUDIT on a Page post, answer two questions, reach the team.
AI answers product questions in DMs and hands off to a person on request.
Send MENU and get the menu and a reservation link on one card.
The bio link opens a DM that asks which day and sends that ticket link.
A broadcast is one message sent to many contacts at once, in the chat apps they already use. You choose who receives it, write it a single time, and ChatinFlow delivers it contact by contact and records what happened to each one. It takes the place of pasting the same message into threads by hand, and of the email blast that most of your list never opens.
12,420
Queued
99.4%
Delivered
31%
CTR
Audience resolved at
Send time
You pick a channel and an audience.
Either every contact in the workspace or a saved segment. The audience is resolved when the send starts, so a segment that grew overnight goes out at its current size rather than the size it had when you wrote the message.
You write the message once and it saves as a draft.
Nothing leaves the workspace while it is a draft. The draft holds the channel, the audience, and the text, so a teammate can read it before a single contact does.
You send now, or schedule it.
A scheduled broadcast waits in the queue and can still be paused or canceled before it starts, which is what you want the day a launch date moves.
ChatinFlow sends contact by contact and writes down each result.
Every recipient gets a delivery row marked pending, sent, failed, or skipped, carrying the reason the provider gave. A partial send is something you can read line by line instead of guess at.
You watch it finish.
The broadcast moves from running to completed while the sent and failed counts climb. One that cannot start at all lands in failed rather than sitting there looking busy.
Email, SMS, Telegram
3
Channels open to a cold send
The three channels marked supported in the broadcast channel catalog. WhatsApp needs an approved template outside the 24-hour window, and Instagram and Messenger only reach people who wrote in the last 24 hours.
pending, sent, failed, skipped
4
Delivery states per contact
Every recipient carries its own delivery row with one of those four states plus the reason the provider returned, so a partial send can be read line by line.
Free text inside it, templates outside
24h
Meta messaging window
Meta's customer service window. ChatinFlow checks it per channel before a send starts rather than reporting the rejection afterwards.
Each recipient gets their own message with their own tokens filled in, and a fallback when a field is empty, so nobody opens a greeting addressed to a blank.
Build an audience out of what contacts actually did: orders placed, replies sent, how recently they wrote, which flow brought them in. The segment is resolved when the send starts, not when you saved it.
Pick a time instead of sending now, and keep the ability to pause or cancel while it is still queued. A launch date that moves costs you one click instead of a support thread.
Channel rules are checked before the send starts rather than after. Contacts who opted out are skipped, Meta window limits are enforced, and a channel that cannot carry this message says so up front.
The audience goes out in chunks with one idempotent row per contact, so a retry never delivers the same message twice and every skip carries the reason it was skipped.
Creating and sending sit behind the broadcast.manage permission and the feature.broadcasts entitlement, so a teammate who should only read results cannot start a send by accident.
A channel you have already connected
Broadcasts go out through an authorized channel connection. Email and SMS need a verified sender, and Telegram only reaches contacts who started the bot themselves.
Consent you can point to
Every channel expects the contact to have opted in. ChatinFlow honors opt-out and skips those contacts, but collecting the consent in the first place is yours.
An open window or an approved template on Meta channels
WhatsApp allows free text only inside the 24 hour customer service window. Outside it you need a Meta-approved template, and Instagram and Messenger follow the same rule.
The feature on your plan and the role to use it
Reading the list needs the broadcast.view permission and sending needs broadcast.manage, both behind the feature.broadcasts entitlement your plan carries.
Write it once, send it to a segment, and see per contact
whether it arrived.
More messages, less mess.
Everything you need to know before your first automation goes live.