ChatApp Broadcast Service
Broadcast messaging across WhatsApp, Telegram, MAX and e-mail in one place
One campaign goes out to every channel your customers actually write on. Split the list into segments by tag and get a report on each send.
3,500+ companies · 15 channels · 97% happy with support
One message — nine delivery routes
All channels connect and configure from a single dashboard
WhatsApp
MAX
Telegram
WACA
WABA
Telegram bot
MAX bot
VK-notify
Email
Broadcast channels for different tasks
Each channel has its own audience and rules: your own list is free and template-free, a cold list needs an approved template
01
Broadcast through a bot: MAX and Telegram
The message goes to people who already wrote to your bot — a continued conversation, not cold outreach, so no template or moderation is needed. Cheapest and fastest to launch
02
WhatsApp Business API / WhatsApp Cloud API
The only legal way to reach people who haven't written to you yet. For businesses in Kazakhstan this is the WACA line. Messages go out only through a pre-approved template. Works on cold lists too
03
Number-based Telegram, MAX, WhatsApp
Sent from a personal number, not a bot. Technically it works, but platforms block the number almost as soon as they suspect a mass send.
Roughly how many messages before the ban risk climbs:
≈20 on Telegram≈5 on MAX≈10 on WhatsApp
Advice: use this method in small doses and only inside a cascade.
04
E-mail
ChatApp adds no limits of its own — only the usual email rules apply: domain reputation, SPF/DKIM, your provider's limits. Connects over SMTP: your own server, Amazon SES, or a dedicated provider. No limit on recipients
Cascade model: a customer isn't lost if a channel fails
If a message doesn't land or gets no reaction, the send moves on to the next channel by itself
Bot on Telegram / MAX
WACA / WABA
Number-based channel
Email
Write different copy for each channel: the same message everywhere at once gets you blocked faster.
Broadcast scenarios for a business
Welcoming new customers
Right after the first message to your bot, walk them through the product and the next steps.Abandoned cart
Remind them about the unfinished order and add a promo code to bring them back.Event reminders
Flag that a webinar is starting, an appointment is near, or a subscription is about to expire.Promotions and promo codes
Discounts and special offers reach only the segment they actually matter to.Holiday greetings
Personal greetings for a customer's birthday or calendar dates.Winning back inactive customers
Special terms for people who haven't bought or opened a message in a while.Segmentation: by tag and field, not "everyone at once"
Bots on MAX and Telegram don't message the whole list — they build a selection from the conversation data: a tag, a filled variable, a stage in the scenario. Different copy for different audiences lowers the block risk, unlike a single message to everyone.
By tag
Only contacts tagged "Regular customer" or "Abandoned cart"By filled field
Only contacts with the "City" field filled inSample selection for a bot broadcast
Tag: Regular customer Tag: New lead Field "City" filled in Field "Promo code" filled in
1,284recipients in the selection
From contact list to report in four steps
- 1
Collect your list
Bot conversations, a CSV or Excel file, an export from Bitrix24 or amoCRM, or just a tag filter. - 2
Set up the send
Dates and weekdays, time, the gap between messages, one line or several. - 3
One message, different people
Variables pull the name and other fields from your list. Send yourself a test before launch. - 4
Follow the report
Status of every send, a retry for anyone missed, export to Excel.
The fate of every message, not just the campaign in total
Sent → delivered → read — or an error with the reason
+7 7•• ••• 41 82 Read
+7 7•• ••• 07 55 Delivered
+7 7•• ••• 63 20 Sent
+7 7•• ••• 19 44 Error
Resend only to the people it missed — no need to rebuild the whole broadcast.
Questions about broadcast messaging
Nine delivery routes from one dashboard: WhatsApp, MAX, Telegram, WACA, WABA, bots on Telegram and MAX, VK-notify and Email. Channels combine for the task — from a warm list to cold contacts.
Not if the broadcast goes out through a Telegram or MAX bot to people who already wrote to you first - it's a continued conversation. A template is only required for WACA/WABA and for broadcasts to a cold phone list.
Set up a cascade: if a message isn't delivered or the customer doesn't reply, the send automatically moves to the next channel. For example, from a bot to WACA/WABA, then to a number-based channel or Email.
You can build a selection by tag ("Regular customer", "Abandoned cart") or by a filled field (like "City"). Different copy for different segments cuts the risk of the channel getting blocked.
Roughly ≈20 on Telegram, ≈5 on MAX, and ≈10 on WhatsApp before platforms may ban the number over suspected mass sending. Use this method sparingly, as one link in a cascade.
Yes. The report shows the status of every message: sent, delivered, read, or an error with the reason. You can rerun the send for just the addresses that errored, no need to rebuild the whole broadcast.
Connect the channel your customers actually write on
Build a broadcast on your own list in a few minutes — or start with the launch guide
