Three customers call the same bank on the same morning. The first asks what the minimum balance is on her savings account. The second wants his registered address changed. The third says a ₹1,200 annual fee was charged on a card he was promised would be lifetime-free, and he is unhappy about it. All three are “calls” in the dialler’s statistics. Operationally, they are three different kinds of work, and treating them alike causes real trouble.

Three kinds of contact

A query is a request for information. The customer wants to know something: a balance, a policy, a status, how a feature works. It is usually resolved on the spot, and the measure of success is whether the answer was correct and complete.

A request asks the organisation to do something that is part of normal service: change an address, issue a duplicate statement, upgrade a plan, block a lost card. Nothing has gone wrong. Requests often need fulfilment by another team or system, so they have a turnaround time, and success means the action was done correctly and on time.

A complaint is an expression of dissatisfaction about the product, the service or how the customer was treated, where a response or resolution is expected. ISO 10002, the international guideline on complaints handling, defines it in broadly these terms. The key element is dissatisfaction, not the topic. “Why is there a ₹1,200 fee on my card?” can be a query if the customer simply wants to understand it. “I was told this card was free and now you have charged me” is a complaint, even if the agent can reverse the fee in two minutes.

Why the label matters so much

In regulated sectors, complaints carry obligations that queries and requests do not. Under RBI’s Integrated Ombudsman Scheme, 2021, a customer of a regulated entity can approach the RBI Ombudsman if the complaint is rejected, not answered satisfactorily, or not resolved within 30 days. Insurers have their own grievance timelines under IRDAI rules, and telecom operators under TRAI’s consumer complaint regulations. Regulators also expect complaints to be counted, analysed and reported. If agents log a genuine complaint as a query because it was “resolved on the call”, the company understates its complaints, misses root causes, and may be caught out when the customer escalates externally.

There is also an internal reason. Complaints are the clearest signal of what is broken. A process that hides them to look good on a dashboard loses its best source of improvement ideas.

A practical rule used by many operations: if the customer expresses dissatisfaction and expects something to be put right, log it as a complaint, even if it is resolved immediately. Resolved-at-first-contact complaints can be reported as such; they still count.

The lifecycle of a ticket

Whatever its type, any contact that cannot be closed on the spot becomes a ticket (or case, or service request, depending on the CRM). Following the card fee complaint through shows the typical stages.

  1. Logging. The agent creates the ticket with verified customer details, the issue in the customer’s own terms, what was promised at onboarding (if known), and the outcome the customer wants. A reference number is given to the customer.
  2. Classification and prioritisation. Type (complaint), category (cards, fees), severity and due date. A fraud-related complaint would be prioritised far above a fee dispute.
  3. Acknowledgement. The customer receives written confirmation with the reference number and expected timeline. This step is often skipped, and its absence drives many “status check” repeat calls.
  4. Assignment and investigation. The ticket goes to the team that can resolve it, here a card servicing team that checks the original offer terms and sales records.
  5. Resolution. A decision is made: fee reversed, or fee upheld with an explanation. Either is a resolution; what matters is that it addresses the actual complaint.
  6. Communication. The customer is told the outcome, the reasoning, and, if the answer is unfavourable, what further recourse exists. In banking that includes the escalation route and, ultimately, the Ombudsman.
  7. Closure. The ticket is closed with a closure code and notes. Some organisations confirm with the customer before closing, others close on communication and allow reopening.
  8. Reopen and review. If the customer comes back unhappy, the ticket is reopened rather than a fresh one being created, so the history stays in one place and reopen rates can be measured.

Where tickets get stuck

Ageing reports, which show open tickets by how long they have been open, reveal the usual blockages. Tickets sit “pending with another team” with no internal deadline. They bounce between teams because nobody agrees who owns the category. They wait for customer documents with no reminder sent. Or they are closed by the resolver team as “done” while the customer was never told, which produces a repeat call that looks like a new issue.

Several practices help. Set internal TATs for each hand-off, not just the overall deadline. Make a single owner accountable for the customer communication throughout. Track “pending with customer” separately, and pause or not pause the SLA clock according to a clearly agreed rule. Review the oldest tickets daily rather than the total count, because one 25-day-old complaint near a regulatory deadline matters more than fifty fresh queries.

What good complaint data shows

Once complaints are logged honestly and categorised well, they can be analysed by root cause rather than symptom. The card fee complaint might turn out to be one of hundreds caused by a sales script that described a “first-year-free” card as “free”. The fix is not faster fee reversals in the contact centre; it is changing what the sales team says. That link, from individual tickets to a systemic cause, is the real payoff of classifying contacts correctly.

Written by the RP Strativa Team. The customers and amounts in the examples are illustrative; regulatory timelines should be checked against current rules for each sector.

Leave a Reply

Trending