In Kazakhstan, WhatsApp is not an "additional channel" but the primary messenger where customers actually read your messages and reply. That's why almost every company sooner or later asks us the same question: "Can I broadcast a promotion to my entire database in WhatsApp from Bitrix24?" The short answer is yes, you can, but the method you choose determines whether you lose your working number in a single day or build a channel that generates leads for years. In this article we'll cover three topics that businesses usually search for separately and confuse with one another: the technical difference between broadcasting from a regular number versus the official WhatsApp Business API, the reasons for bans in 2026, and the requirements of Kazakhstan's personal data law. No fluff and no promises of "broadcasting without consent with impunity" — that doesn't exist.
Why businesses in Kazakhstan need WhatsApp broadcasts and where the legal line is
WhatsApp broadcasts solve clear-cut tasks: reminding about an abandoned cart, reporting order status, inviting customers to a repeat purchase, sending a promotion to a segment that hasn't bought in a while. The open rate of the messenger is incomparably higher than email, and the customer's reply lands straight in the manager's hands in Bitrix24 as a new deal or a message in an open channel. The problem starts where a "broadcast" turns into mass-sending advertising to people who weren't expecting it.
The line runs along two boundaries at once. The first is the rules of Meta itself (the owner of WhatsApp): it dislikes cold promotional messages from regular numbers and bans them quickly when complaints come in. The second is Kazakhstan's law "On Personal Data and Its Protection" No. 94-V and the law "On Advertising": an advertising message may only be sent to someone who has consented to it, and the person must have an easy way to opt out. Cross either of these lines and you'll get either a technical ban or a complaint and a fine. A safe broadcast is one that passes both checks.
Two ways to broadcast: a regular number via Wazzup vs the official WhatsApp Business API (WABA)
Technically, from Bitrix24 via Wazzup you can work through two different channels, and this is the key distinction that is most often misunderstood.
Regular number (WhatsApp Personal via Wazzup)
This is your ordinary SIM card with WhatsApp installed, connected to Bitrix24 via Wazzup. The channel is excellent for live conversations: a manager talks to customers right from the deal card, sees the history, and never loses a dialogue. But it is not a tool for mass broadcasts. WhatsApp on a regular number is not designed to send the same message to hundreds of unfamiliar contacts — that is exactly what gets numbers banned first.
Official WhatsApp Business API (WABA)
This is Meta's legal channel for businesses. You connect a separate number through a provider (BSP), get a green checkmark and a company name, and can send messages using approved templates. Wazzup acts as the intermediary that connects WABA to Bitrix24. WABA has a number quality rating and limits on the number of dialogues per day, which grow as you behave well. WABA is precisely the right tool for broadcasts because it is designed for mass communication and, when the rules are followed, does not lead to an instant ban.
- Regular number via Wazzup — for dialogues and replying to inbound messages, not for broadcasting to a cold database.
- WABA — for template-based notifications and approved broadcasts to a database that has given consent.
- WABA is billed by Meta per dialogue (session), and the cost depends on the template category — this should be factored into the channel budget.
- Connecting WABA requires a verified business account in Meta Business Manager and a properly completed profile.
Why mass broadcasts from a regular number lead to a ban in 2026
In the past, "grey" broadcasts from regular numbers through third-party services somehow got through. In 2025–2026 this is an almost guaranteed path to a ban, and here's why. Meta has spent years refining its anti-spam algorithms: the system sees that a number sent a lot of identical messages in a short time to new contacts who don't have you in their address book. Add to that recipients' complaints via the "Block" or "Spam" button — and the number gets banned. Often irreversibly, along with the entire conversation history and reputation.
The danger is that it's not the "broadcast service" that gets blocked, but your working number — the very one listed on your website, business cards, and in 2GIS. Recovering it is not always possible. For a sales department this means losing contact with active customers, not just a failed promotion.
Saving on WABA and broadcasting a promotion from your working number is a bet where the win is a couple of thousand tenge and the loss is your main communication channel with your customer base. The math is always against the "grey" broadcast.
A separate note: the "colder" the database and the more aggressive the advertising copy, the higher the chance of complaints. A broadcast saying "buy from us, 50% off" to a list purchased from a third party is the worst possible scenario, both for ban risk and under the law.
Kazakhstan's "Personal Data" law: consent, opt-out, withdrawal of consent, and fines up to 200 MCI
The legal side in Kazakhstan is no less important than the technical one. The basic principle of law No. 94-V: processing personal data (and a phone number is personal data) — and especially sending advertising to it — is only permitted with the person's consent. The consent must be verifiable, meaning you must be able to prove when and how the customer gave it.
- Consent to an advertising broadcast is separate and informed. A "I agree to data processing" checkbox at checkout is not equal to consent to receive advertising in WhatsApp.
- The recipient must have a simple way to opt out — for example, replying "STOP" or pressing an "Unsubscribe" button in the template.
- A person has the right to withdraw consent, and the company is obliged to stop the broadcast within the period set by law — in practice, aim for 15 business days and always verify the current version of the law with a lawyer.
- Violations entail administrative liability under Kazakhstan's Code of Administrative Offenses; fines for violations in the area of personal data and advertising can reach around 200 MCI depending on the offense and the subject.
We deliberately do not provide turnkey legal advice here: specific fine amounts and time limits depend on the article, the version of the law at the time of the violation, and on whether the violator is a sole proprietor or an LLP. Before launching broadcasts, align your consent wording and opt-out policy with your lawyer. Our job is to make sure Bitrix24 technically records consent, provides an opt-out, and does not send advertising to those who have withdrawn it.
WABA templates: how they get approved by Meta and what you can and can't write
In the official channel you cannot send arbitrary advertising text to your database — only a template pre-approved by Meta. A template goes through moderation and belongs to one of several categories, and the category determines both the cost of a dialogue and the permissible content.
- Utility (service/transactional) — order status, appointment confirmation, payment reminder. Cheaper and easier to pass moderation.
- Marketing — promotions, new arrivals, database reactivation. More expensive, stricter moderation, and a proper consent context is mandatory.
- Authentication — one-time codes and confirmations.
What gets rejected most often: aggressive sales wording in service templates, promises and clickbait, errors and "junk" variables, the lack of a clear message meaning. To reduce complaints and extend the life of the number, an unsubscribe button is added to marketing templates — this is both common sense and effectively an element of compliance with the opt-out law. If your templates get mass complaints, Meta lowers the number's rating and cuts daily limits, and the template itself may end up with a "rejected" status.
How to set up segmentation and triggered broadcasts in Bitrix24 powered by Wazzup
A proper broadcast in Kazakhstan is almost always not "everyone at once" but targeted communication by segment and by event. This is exactly where Bitrix24 as a CRM fully shines, while Wazzup serves as the transport to WhatsApp.
- Segmentation: we filter the database by deal stage, city, amount, date of last purchase, source — and work only with those who have given consent.
- Triggered scenarios (robots and business processes): the message goes out automatically on an event — order placed, payment overdue, deal not moving for N days, customer hasn't bought in a long time.
- Consent storage: a dedicated field in the contact/deal card that records the fact, date, and channel of obtaining consent, plus a withdrawal flag.
- Response handling: a customer's reply in WhatsApp creates a deal or revives an existing one, the manager sees it in Bitrix24 and continues the dialogue from a regular number.
This approach delivers a double win. From Meta's perspective, triggered messages are relevant and almost never trigger complaints. From the legal perspective, you only send to those who consented, and you can prove it with a CRM export.
Safe broadcast checklist: number warm-up, frequency, opt-out, consent storage
Before launching, go through this list — it covers most of the causes of bans and complaints.
- Use WABA for broadcasts and a regular number only for live dialogues.
- Warm up a new WABA number: start with small volumes and scale up as the quality rating and limits grow.
- Broadcast only to a database that has given consent; do not buy or use other people's contact lists.
- Control frequency: don't bombard a customer with messages, or complaints and opt-outs will rise.
- Add an opt-out to marketing templates and actually process refusals — remove the contact from broadcasts.
- Record consent and its withdrawal in Bitrix24 with date and channel — this is your protection during an audit.
- Monitor the number's quality rating in Meta Business Manager and slow down if it drops.
- Test templates on a small segment before mass-sending.
Typical mistakes of Kazakhstani companies and how we fix them during implementation
Over years of Bitrix24 implementations in Kazakhstan, we see the same set of mistakes that cost businesses dearly.
- Broadcasting from the working number to a cold database — and losing the number. We fix this by moving broadcasts to WABA, leaving the regular number for conversations.
- One template "for everyone" instead of segments — high complaint rates. We fix this with segmentation and triggers in the CRM.
- No consent recording — nothing to confirm the legality of the broadcast. We set up fields and processes for storing consent and opt-outs.
- An opt-out "for show" that no one processes. We set up automatic exclusion of those who refused from all scenarios.
- Marketing copy in a service template — rejection by Meta. We help correctly split messages across categories and pass moderation.
- No one monitors the number's rating until a restriction lands. We set up a procedure for controlling quality and pace.
The bottom line is simple: WhatsApp broadcasts in Kazakhstan work and generate leads if you do them through the right channel, to a consenting database, and via well-designed scenarios in Bitrix24. The "grey" path gives short-term savings and a long-term risk of losing both your number and money on fines. If you want to launch the channel the right way — set up WABA, templates, segmentation, and consent in Bitrix24 — we'll help you do it turnkey and tailored to the specifics of Kazakhstani legislation.
