The reach is visible before you send
You build a slice — everyone subscribed who wrote to you after March — and see the count and the first names right away. Before, not after.
ProductBroadcasts
Say it once, and everyone hears it
You need to tell a hundred people the same thing. Gather the ones who let you write to them, see the number before you send, send it — and get back more than the word sent, a line for every person, who received it and who did not and why.
What it does
What a broadcast includes
The list freezes the moment you send
The recipients are fixed once. While the broadcast runs, someone will unsubscribe and someone will write to you first; none of it changes a send already in flight.
Skipped is broken down by cause
Not one flat number, but counters that say what happened — no address in this channel, permission withdrawn, the channel could not carry it. This is usually where the answer to why so few actually lives.
A check right before delivery
Someone blocked you an hour after you pressed send? The message is put out on approach instead of flying into a wall.
Unsubscribing works by itself
One word — stop, unsubscribe, leave me alone — takes a person off your broadcasts, with no form and no work from you. After that they are out of reach.
Permission is checked as the list freezes
Not when you first thought about the broadcast. Someone who withdrew before you pressed send is left out, and nothing has to be rebuilt for that to be true.
Sending does not flood the messenger
It goes in batches of a hundred, and the queue picks itself up where it left off until the list is exhausted.
Replies arrive as conversations
Someone answers your broadcast and it is a normal thread with the whole history behind it, not a line in a report.
How it works
How it works in practice
Gather the people who need this
Subscription status and last activity. "Everyone who wrote to me after March" is one choice, not an export to a spreadsheet.
Look at the number
If twelve people match instead of the two hundred you expected, it is better to learn that now.
Write the message
The draft is saved separately from sending. Write today, send tomorrow — two different actions, and the second one asks you to confirm.
Send it and read the report
Seven numbers instead of one — total, eligible, queued, delivered, skipped, failed, cancelled.
What is guaranteed
A broadcast cannot reach someone who never allowed it
Permission is not a checkbox but a history — who granted or withdrew it, when, and on what basis. Withdrawn yesterday holds today, and "where did you get my number" has an answer with a date on it.
Questions
What people ask about broadcasts
- Will I get banned for sending in bulk?
- We work through the platforms' official interfaces, delivery goes in batches and in order, and only someone who allowed it can receive anything.
- What happens to people who unsubscribed?
- They are left out of the send and marked with their own reason. Unsubscribing takes effect from the moment the person did it.
- Can I resend to the ones who did not open it?
- Build a new slice and send a new broadcast. The one already sent stays unchanged along with its list — that is exactly what makes it a report you can trust.
- Who can see the broadcast came from me?
- The person gets an ordinary message in their ordinary chat with you. No labels, and no shared lists.
- What if someone has several channels?
- The message goes to the address that fits the broadcast's channel. Nobody gets two copies.
Broadcasts
Send the thing you have been meaning to say
Start with the people who already wrote to you. Build the slice, look at the number, send one message — then you will know whether you need a second broadcast.