The Complaint You Cannot Receive

Most customer service thinking is built around the complaints you get. Response times, resolution rates, recovery offers, win-back rates. All of that assumes the dissatisfied customer tells you, and in a lot of categories that assumption holds well enough to build a function on.

It does not hold in ours, and I suspect it holds far less widely than most businesses realise.

I founded Miracle Botanicals in 2011 with my family on the Big Island of Hawai'i. We sell pure and certified organic essential oils, sourced direct from distillers and farmers, and every oil is third-party tested for synthetics, pesticides and adulteration before it is sold. Essential oils are unusually easy to adulterate and unusually hard for a buyer to assess. Someone who receives a bottle that has been cut with a cheaper oil will very likely never know. It smells approximately right. It performs acceptably. They may leave a positive review.

That is the complaint you cannot receive, and it changes what a customer relations function is actually for.

If your customers can detect quality problems, your inbox is a reasonably honest sensor. Complaint volume goes up when something goes wrong, and a well-run service team closes the loop. If they cannot detect them, complaint volume tells you almost nothing about whether you are delivering, and a quiet inbox is not evidence of a healthy business. It is evidence of an uninformative one.

Three practical consequences follow.

The first is that quality assurance cannot be downstream of customer contact. In categories with a working feedback loop, you can afford to let some problems be caught by customers, because they will tell you and you can recover. Where the loop is broken, anything that reaches a customer undetected stays undetected, and the recovery opportunity never arrives. That is why our testing sits before the sale rather than after the complaint. It is not diligence; it is the only position where the check can do any work.

The second is that the small number of customers who can tell are disproportionately valuable, and most service processes are designed to make them go away. A customer who writes to say this year's oil smells different from last year's is doing something remarkable: they are supplying a signal your instruments cannot generate. In a standard service workflow that arrives as a low-priority, hard-to-resolve contact, gets a goodwill gesture, and is closed. The gesture is fine. Closing it without aggregating it is the loss. Those remarks are the earliest indication that something has changed at a farm or a still, often well before anything else surfaces.

The third is that service recovery has to be honest about what it cannot fix. When someone raises a concern about the product itself rather than the order, the useful response is information rather than a discount. What we can say is what species it is, where it came from, how it was distilled and what the testing showed. A refund resolves the ticket. It does not answer the question, and in a trust-dependent category the question is the entire relationship.

The broader point I would offer is that most customer relations teams should establish, explicitly, which kind of category they operate in. Ask whether a customer who received a materially worse version of your product would find out. If the answer is yes, your complaint data is a sensor and you should trust it. If the answer is no, or not for months, then your complaint data is measuring your logistics and your interface and almost nothing about your product, and you need a source of truth that does not depend on customers noticing.

That source has to be external. Anything self-reported degrades quietly, because there is no one on the other side to notice when it stops. We use a laboratory. Another business might use audits, mystery purchases, or independent inspection. The mechanism matters less than the fact that it produces evidence you did not generate about a product your customers cannot evaluate.

Loyalty in these categories is not really built in the service interaction. It is built by being the kind of company that is still doing the expensive invisible thing on a quiet Tuesday when nobody would have caught it. Customer relations cannot manufacture that. What it can do is stop treating silence as good news.