A complaint tells you something. Take the ₹400 credit-card transaction from a 2005 programme. The customer’s issue was not only a missed payment. The statement did not arrive. The payment was missed. Interest and late charges built up. A settlement was discussed and paid. Then a statement still showed an outstanding amount.
For the customer, this was one experience. For the organisation, it ran across processes, systems, teams, and hand-offs. The complaint still has to be closed. The organisation also has to ask what the complaint is saying about communication, process clarity, ownership, and alignment when work moves from one desk to another.
The most useful question is what we are doing with what we have learnt.
Regulation has moved on. There are clearer customer-protection rules, formal grievance routes, and an ombudsman when the regulated entity does not resolve the matter. That framework matters. It cannot, by itself, produce good service.
Good service still needs organisational intent, a structure that lets teams work together, measurement that finds where the experience actually breaks, and a habit of using complaints as inputs for change rather than cases to close.
Technology and regulation have evolved since that 2005 conversation. The question has not. Progress is not fewer complaints. It is whether we are getting better at learning from the ones we receive.