This piece was prompted by a recent post from Gabor Tubino at FIXERZ Academy on customer claims in manufacturing. His point was simple: a customer claim does not only test the defect, it tests the organisation behind it, including whether teams can identify what happened, take ownership and communicate clearly under pressure.
That made me think about the same question in regulated communications.
It starts with one sentence:
"That's not what you told me."
At first, it can look like a wording problem. Perhaps a term was unclear, a disclosure was outdated, or the customer understood something differently from what the organisation intended.
But in a regulated environment, that single sentence has a way of not staying small. Ask the next question and the issue starts to expand.
Which version of that communication was actually sent? Who changed the wording, and when? Was it reviewed before it went live? Who approved it, and can you show that they did? Did the email, PDF and in-app message all say the same thing, or had one channel drifted away from the approved wording? And if needed, could you reproduce exactly what that specific customer received on that specific date?
By the third question, this has stopped being a complaint about wording.
It has become a test of whatever sits behind the wording: the controls governing how a communication is created, changed, reviewed, approved and released.
That distinction matters.
In many organisations, the compliance process is strong on reviewing wording, while the evidence behind how that wording was changed, approved and released can sit across several different systems.
The challenge is that there may not be a single, reliable record tying the specific communication a customer received back to a specific approved version.
Reconstructing that history may mean searching through email threads, shared drives, development tickets and fragmented records.
That gap can remain largely invisible until somebody asks the question.
The pressure changes when the same question has to be answered across multiple communications, customers or channels. At that point, "we're pretty sure this was right" is very different from being able to demonstrate what happened.
The same underlying problem can appear across very different regulated sectors, including financial services, insurance, pensions, debt collection and utilities, wherever customer-facing communications need to match an approved version and the organisation may later need to demonstrate what was communicated.
The industries differ. The wording differs.
The control problem underneath can be remarkably similar.
Building for that moment does not mean rewriting how compliance teams work.
It means making the ordinary lifecycle of a communication easier to reconstruct.
When a template changes, the organisation should be able to establish what changed, who reviewed it, who approved it and when it went live.
That is not a guarantee that nothing will ever go wrong.
It is a way to reconstruct, quickly and accurately, what happened when somebody asks.
So here is the question worth considering:
If a customer challenged one of your communications tomorrow, on any channel, how long would it take your team to reconstruct exactly what they received and the approval history behind it?
If the answer is longer than the team would like, that delay may not be a problem with the people involved.
It may be a sign that the communication control itself is fragmented.