On Saturday, 24 October, I had a WhatsApp follow-up message written, approved and ready to go to a list of people who had asked us for a guide. I did not send it. Not one message went out, because when I checked, none of those people had told us they wanted to hear from us on WhatsApp.
A list that looked ready
The people on the list had all asked for the same guide, and every one of them had given a phone number. The message itself was friendly and useful: a short first step, an offer to talk it through, and a clear way to stop.
Everything about it looked ready. The one thing I had not looked at yet was whether each person had actually said yes to WhatsApp.
A phone number is not permission
So before sending, I went through the list and asked one question of every record: where is the yes?
There wasn't one. Not a single record held an explicit permission to be contacted on WhatsApp. One label that looked like it might count only described how the person had found us. That is attribution, not consent, and it is an easy pair to confuse when you want a campaign to go out.
A number in a form field tells you how to reach someone. It does not tell you they want to be reached that way.
What we changed
The message stayed unsent. Instead, we changed the form. It now carries an optional box, unticked by default, asking whether the person would like help on WhatsApp. If they tick it, their record keeps the answer, when it was given and the exact wording they agreed to. If they do not, nothing changes for them and they still get the guide.
Before trusting it, I tested it on my own record, first with a no and then with a yes, and checked that each answer was stored the way it should be. Then I put my record back the way it was.
The people already on the list were left alone. Going back to message them on WhatsApp would have meant assuming a yes nobody gave us.
Why it matters past one list
Plenty of businesses have a list like this: numbers gathered from enquiries, orders and old chats, sitting on a phone or in a spreadsheet, with no record of who agreed to what. The temptation is to broadcast to all of it. The cost shows up later, in blocks, reports and a number WhatsApp starts to restrict.
The fix is not a cleverer message. It is keeping the permission on the same record as the contact, so the question "may we message this person here?" has an answer before anyone presses send. That is how we set up NexBrand for the businesses we work with: one record per customer, the permission on it, and replies coming back to one shared inbox.
Sending nothing that Saturday was the right call. The list we build from here will be smaller, and every person on it will have said yes.
Frequently Asked Questions
Is a customer's phone number enough to send them WhatsApp marketing?
No. A number tells you how to reach someone, not that they agreed to be reached that way. Record an explicit yes for WhatsApp, with when and how it was given, before sending marketing.
What should a WhatsApp opt-in record include?
The answer itself, the date it was given, where it was given and the exact wording the person agreed to. That lets anyone check later that a message was wanted before it was sent.
What should you do with an old list that has no recorded consent?
Leave it alone on WhatsApp. Ask for permission where people already engage with you, such as forms or replies, and build the new list only from those who say yes.