A broadcast sends a single message to many contacts, now. Unlike a channel post, each recipient gets an individual one-to-one message from your real account, personalized with their own fields — so it arrives in their private chat with you, not in a feed they may have muted.
Broadcasts are the right tool for announcements with a clock on them: a launch, a price change, an event, a last call. When you need a sequence of touches over days or weeks, use a campaign instead; the two share segments and accounts, so switching between them costs nothing.
Send a broadcast
- 1
Build the segment
Filter contacts by tag, custom column, or pipeline stage. The tighter the segment, the better the reply rate — 'everyone' is almost never the right audience.
- 2
Write the message
One clear message with personalization tokens like [[username]] and your custom fields. Write it like a DM to one person, because that is exactly how each copy will land.
- 3
Choose sending accounts
Pick which connected account or accounts send it. Large sends can be spread across several accounts so each one stays within a modest, safe volume.
- 4
Send and watch replies
GramClaw throttles delivery per account automatically and routes every reply into the unified inbox, where tags, tickets, and the pipeline pick up from there.
Deliverability is built in, but behavior still counts
Every broadcast is paced per account rather than fired all at once — that throttling is what separates a broadcast from spam blasting, and it is not optional. Telegram limits how fast an account can message people who have not messaged it first, and accounts that ignore those limits get restricted by Telegram itself.
The other half is consent and relevance. Broadcast to people who know who you are — customers, community members, leads who opted in. A perfectly throttled message that nobody wanted is still a bad broadcast, and enough reports will hurt the sending account no matter how carefully it is paced.
What separates good broadcasts
- One message, one point, one call to action — broadcasts are not newsletters.
- Personalization beyond the name: reference the segment ('as an early user…') so the message explains why they are receiving it.
- Send at a humane local time for your audience.
- Plan for replies: a good broadcast generates conversations, so have the team ready in the inbox.
- Tag the segment before sending, so you can measure replies and conversions per broadcast afterwards.