New format
WhatsApp* broadcasts: Business API, consent, and no spam
WhatsApp* for business is a channel for service and marketing messages to people who agreed to hear from you. Mass spam to strangers breaks trust and hits platform rules.
When a manual app broadcast is enough, why Business API and templates matter, and which topics you must not promote. Don’t treat “billions of users” or 2022 menu screenshots as fixed norms: check current WhatsApp Business rules.
When WhatsApp* fits
The channel is strong for order status, appointment reminders, support, and short offers to a warm base. People read messages fast — and block pushy spam just as fast.
It doesn’t replace a site, email, or search ads. It’s a messenger touch next to other channels.
Manual broadcast from the app
In WhatsApp* you can build a recipient list from your contacts and send one message to the group (broadcast UI wording depends on the app version).
Plus — control and no “agency” layer. Downside — manual work, limited to your contact book, harder scale and analytics.
Forwarding limits and anti-spam mechanics change: don’t build a process on bypassing restrictions.
Minimum before send:
- recipients expect messages from the brand
- copy is short, with value or a status update
- there is a way to opt out / not write again after a block
- don’t mix personal chats and an ad stream without a clear label.
Business API and templates
The official business path is WhatsApp Business Platform / API via vetted providers: message templates, dialogue sessions, catalogs, CRM linking.
If the customer wrote first, a free-form reply window usually opens for a limited time (check exact rules in Help). To start a dialogue yourself, approved templates are usually required.
Business registration and verification, a number not casually mixed with a personal account — part of access. Verification details and profile badges have changed: follow current Meta/WhatsApp Help, not a 2022 guide.
What to write — and what to avoid
Order status, visit reminders, booking confirmation, and a useful FAQ bot with a human handoff work well.
Threats, deception, and pushy ads without context land badly. Some niches (prescription drugs, alcohol, gambling, and others) are limited by WhatsApp advertising rules — check the current prohibited list.
Tone: respectful, without “buy now or else.” A bot fits routine questions; complex cases go to a person.
Agencies and vendors
A vendor can help with templates, API integration, and reporting. Ask: where the base comes from, whether there is consent, which API provider, who owns the number and templates after the contract.
A “ready base of millions of numbers” is a red flag. Check reputation, the contract, and a pilot on your own opt-in sample.
What to remember
WhatsApp* runs on consent and usefulness — not cold spam.
Scale — through official Business API and templates; small volume — manual broadcast to your contacts.
Rules and UI change: check platform Help before launch.
FAQ
Can I advertise to everyone in the phone book?
Only if people expect messages from you and it doesn’t break platform rules or advertising/personal-data law. Cold spam to other people’s contacts leads to blocks and complaints.
How is Business API better than a manual broadcast?
Scale, templates, CRM integrations, reporting. A manual list suits small volume to your own warm contacts.
Do I need business verification?
For full API work and profile trust — follow current WhatsApp/Meta requirements. Without confirmation some options stay unavailable.
Should I buy a “number base” from an agency?
Not as a strategy. Opaque lists without consent = spam, complaints, and brand risk. Work with your own opt-in base.
How is WhatsApp different from SMS?
Different channel and rules. Consent and usefulness logic is the same; choose where the customer actually replies. See also the SMS piece.
Bought a “WhatsApp number base” — and got blocks instead of leads?
We’ll set an opt-in path and official Business API templates — consent first, no grey senders.
Discuss the task
