Today's post on this side of the site is about WhatsApp templates, the approved wording that lets a business message a customer first. Writing it meant reading Meta's pricing page again, and it reminded me of something I found in late September that I have not written about.
Three of my own posts went out of date overnight
I had written several posts about what WhatsApp costs a business. They were accurate on the day I published them. Then Meta changed how it charges for replies, with the change taking effect on 1 October, and when I went back to check, three of my own posts still described the old rules.
Nobody had told me. Nothing broke. The pages still loaded and still read confidently. They were simply wrong, and a customer deciding what to budget would have trusted them.
I found them only because I was checking my own work against the source before publishing something new. The correction is staged. The point of this post is not the fix, it is how easy the problem was to miss.
Why this is a communications problem, not a writing problem
A price quoted in a blog post is a message to a customer. So is a reminder, a follow-up or an after-hours reply. Each one is a statement your business made, in your name, that stays in the world after you stop thinking about it.
When the rule behind it moves, nothing tells the message to update. A template that mentions an offer that ended keeps going out. A reply that quotes a policy that changed keeps being sent. The business looks careless and nobody inside it can say when it started.
What I do differently now
I stopped treating a published message as finished. Every figure that depends on someone else's rules now has the date I read it and where I read it, so the next person to touch it knows how old it is. And before I build on an older post, I check it against the source instead of trusting my own earlier work.
It is not clever. It is the same thing I would ask of any client: know which of your messages depend on a rule that can change, and know who is looking at them.
The honest part
I only caught this because I happened to be in the right place. If I had been busy that week, the three posts would still be live, still confident and still wrong. That is the real risk with any message that goes out on a schedule or sits in a library: it keeps working long after it stops being true.
This is the part of NexBrand that does not show up in a demo. One place where every customer message lives, who sent it and what it said, with an owner, so that when a rule changes there is a list to check instead of a memory. If you want to see which of your own customer messages depend on someone remembering, the free Business Autopsy maps it. Today's post has the practical side of templates.
Frequently Asked Questions
Why did your own posts go out of date?
Because they quoted a rule that Meta later changed. A published post does not update itself, so it stayed live and confident after the rule moved. I only found it by checking against the source.
How do you stop that happening again?
Every figure that depends on someone else's rules now carries the date and place it was read. I also check older posts against the source before building on them, rather than trusting what I wrote earlier.
What does this have to do with NexBrand?
Customer messages are statements your business makes and then forgets. NexBrand keeps them in one place with an owner and a history, so when a rule changes there is a list to check.