What counts as permission
A WhatsApp marketing opt in is not a vague “they talked to us once” idea. It is permission from the customer to a named business, for a clear purpose, with a way to stop later. That sounds simple, but a lot of teams blur service messages and marketing messages, then act surprised when the customer did not expect both.
The safest reading is practical: if someone asks about an order, a booking, or support, that does not automatically mean they agreed to future promotional messages. The WhatsApp business policy says businesses need the person’s mobile number and permission for subsequent messages or calls, and they must respect stop requests. It also says applicable law still matters. WhatsApp business policy
Service chats are not the same as marketing
A customer asking a question opens the door to respond about that question. It does not open a blank cheque for ongoing campaigns. If you want to send promotions later, you need permission that covers that purpose.
This is where many teams get loose with language. “They bought from us” is not the same as “they agreed to hear from us on WhatsApp about offers.” A returned customer or a product order may be relevant context, but it is not blanket consent by itself.
If you use WhatsApp marketing, keep the message purpose clear. One note in the CRM should not be doing the work of actual permission. In DripTell inbox, the point is to keep the conversation tied to the right person and the right context, not to assume every message is a green light for more.
Record the permission, not just the contact
If you cannot show what the customer agreed to, the permission is hard to trust. That record does not need to be dramatic, but it should show who agreed, which business they agreed to hear from, and what kind of messages they expected.
The useful question is not “Do we have the number?” It is “Do we know what this person said yes to?” That matters when the same contact later moves from support into DripTell CRM and someone wants to add them to a campaign list. Teams still need clear ownership and configuration.
| Situation | What it usually means | What it does not mean |
|---|---|---|
| Support question | Permission to reply to that request | Permission for future marketing |
| Product order | A customer relationship exists | Automatic consent for promotions |
| Ad click | Possible entry point with conditions | Guaranteed free messaging window |
| Opt in | Permission for a named purpose | Permission for every message forever |
Meta’s public pricing page says charges are based on delivered messages by recipient market and category, while service messages are free and utility responses in the service window are free. A user message opens a 24 hour service window. That is useful, but it is not a promise that every ad click or every reply creates the same result. WhatsApp pricing
Stop requests have to be easy
If a customer says stop, that should be easy to act on. The policy is clear that businesses must respect stop requests. That matters as much as the original permission, because permission that cannot be withdrawn is not real permission in practice.
For a team, this means the process has to be simple enough that the person replying can actually use it. If a campaign is running from DripTell campaigns or a workflow in DripTell automation, the stop request still needs to be honored in the real conversation. No system should make the customer repeat themselves.
What to check before you send
Before a marketing message goes out, check three things: did the customer agree to this business, did they agree to this purpose, and can they stop easily. If any one of those is missing, the message is on weaker ground than your team may think.
You do not need a universal legal claim to make this useful. Different legal markets matter, and the public rules are not the same everywhere. So the smarter habit is to keep permission specific, documented, and easy to withdraw.
Frequently Asked Questions
Does a customer order mean I can send marketing on WhatsApp?
No. An order may create a customer relationship and may justify service messages, but it does not automatically mean the customer agreed to promotional messaging.
Is a checkbox enough on its own?
A checkbox can be part of permission, but by itself it is not enough if the business, purpose, or stop option is unclear.
Do I need to treat every market the same way?
No. Applicable law can differ by market, so teams should not assume one permission rule works everywhere.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
