You call customer care after a failed delivery, wrong bill, refund delay, or broken service. The IVR asks you to press 1, then 2, then 5. A bot says your issue is important. A ticket number comes by SMS. Then nothing happens.
You call again on Saturday. A new agent says the old ticket is closed. You explain everything from the start. They say, “We will get back to you.” Nobody calls.
Quick answer. If customer care keeps delaying, stop only calling. Start documenting every call, ticket, email, chat, and payment proof. Send one clear escalation email to the company nodal officer or grievance officer. If the issue remains unresolved, use the National Consumer Helpline or the proper regulator for that sector.
If you are short on time, go to what to do in the next 30 minutes.
Many people think customer care fails because one agent is careless. Sometimes that is true. But in many cases the system itself is designed to slow you down.
A company may not openly refuse your complaint. It may keep you busy. It may send bot replies. It may transfer you between teams. It may ask for the same details again and again. It may close the ticket before the issue is solved.
This is complaint exhaustion. The customer becomes tired before the company becomes accountable.
It is common in refund disputes, courier delays, telecom billing, app-based services, insurance servicing, credit card charges, e-commerce returns, and loan app support. The pattern is similar even when the industry changes.
Customer care often does not call back because the complaint is handled through queues, scripts, automated ticket systems, outsourced call centres, and closure targets. A genuine delay has a clear reason and timeline. Complaint exhaustion has repeated transfers, bot replies, closed tickets, and no written decision.
An IVR is the phone menu that asks you to press numbers. It can help route calls. It can also tire you.
Common IVR problems are:
Do not fight the IVR for days. Use it once or twice. Then move to written communication.
A bot reply may say your issue is under review. It may ask you to wait 24 to 48 hours. It may send a standard apology.
A bot reply is not a solution. Treat it as proof that you contacted the company. Save it, but do not depend on it.
Many companies reply quickly on X, Instagram, or Facebook. They ask you to share details by direct message. This reduces public pressure.
You can use DM for privacy, but keep a screenshot of the public post and the DM. Ask for a ticket number. Ask for an email address where the same complaint can be sent.
Sometimes the company closes a ticket after sending a reply like “we tried calling you” or “issue resolved”. The issue may still be pending.
Reply immediately in writing:
The ticket has been marked resolved, but my issue is not resolved. Please reopen the ticket or issue a written closure reason. My unresolved issue is: [short summary].
| Sign | Genuine delay | Complaint exhaustion |
|---|---|---|
| Reason | Company gives a specific reason | Only says “under process” |
| Timeline | Gives a date or service-level time | Keeps asking you to wait |
| Record | Sends email or ticket updates | Mostly phone calls and bot chats |
| Ownership | One team owns the issue | You are transferred repeatedly |
| Closure | Closes after fixing or written reason | Closes without solving |
| Evidence | Accepts documents and replies | Asks for same proof repeatedly |
A genuine delay can happen. Systems fail. Refund gateways fail. Courier partners delay. Bank reversals take time. But a genuine delay still has a written trail.
Complaint exhaustion is different. The company keeps activity alive, but avoids a clear decision.
Phone calls feel immediate. They are also weak proof.
After 2 phone calls, move to written complaint. Use email, app support, website complaint form, or registered grievance portal. If you call again, use the call only to refer to the written complaint.
Say this:
I have already sent the full complaint by email on [date]. Please give me the status of complaint number [number]. Please do not create a fresh ticket unless the old ticket is linked.
A timeline turns frustration into evidence. Make it simple.
Use this format:
| Date | Time | Channel | Person or ticket | What happened | Proof saved |
|---|---|---|---|---|---|
| 10 May | 11:20 am | Phone | Ticket 123 | Agent promised callback | Call log screenshot |
| 10 May | 6:05 pm | Ref: refund | Sent full complaint | Email PDF | |
| 12 May | 3:10 pm | App chat | Chat ID 456 | Bot said wait 48 hours | Chat screenshot |
This helps when you escalate. A nodal officer, regulator, or consumer forum will understand the matter faster.
Do not depend on memory. Save proof as soon as it happens.
Keep:
For a deeper checklist, read how to preserve screenshots and proof before filing a complaint.
Many complaints die because the customer accepts a verbal answer.
Ask for a written closure reason. This changes the pressure.
Use this line:
If the company is rejecting my request, please send a written closure reason with the policy, clause, date, and name of the responsible grievance officer.
A weak company reply becomes useful evidence. A clear company reply helps you decide the next step.
Many sectors require or publish escalation contacts. Banks, insurers, telecom companies, payment apps, e-commerce platforms, and regulated entities usually have a grievance route.
Look for these pages on the company website:
Send one clean email. Do not send 20 angry emails. One strong email is better.
Subject: Escalation of unresolved complaint [ticket number] regarding [issue] Dear Nodal Officer / Grievance Officer, I am escalating my unresolved complaint. Customer name: [name] Registered mobile/email: [details] Order/account/policy number: [number] Original complaint number: [number] Amount involved: Rs [amount] Date of transaction: [date] Issue in brief: [Explain in 5 to 7 short lines.] Timeline: 1. [date] - [what happened] 2. [date] - [what happened] 3. [date] - [what happened] Relief requested: 1. [refund/replacement/correction/service restoration] 2. Written reason if rejected 3. Confirmation of closure only after issue is resolved Documents attached: 1. Invoice 2. Payment proof 3. Ticket screenshots 4. Chat/email copies Please resolve this within a reasonable time and reply in writing. Regards, [name] [phone]
Use the National Consumer Helpline when a company is not responding, delaying a refund, closing tickets without reason, or refusing to give a written answer.
The official portal is consumerhelpline.gov.in. It is useful for many consumer disputes. It is not a court order. It is a government-supported grievance channel that pushes the company to respond.
Before filing, keep:
If the matter is about a bank, NBFC, payment system, or failed bank grievance, also read the RBI complaint route.
Do not send every complaint everywhere. Pick the right route.
| Problem | First escalation | Further route |
|---|---|---|
| E-commerce refund | Company grievance officer | National Consumer Helpline |
| Bank or payment dispute | Bank grievance officer | RBI CMS or Ombudsman route |
| Insurance claim delay | Insurer grievance officer | Insurance complaint guide |
| UPI issue | UPI app and bank | NPCI complaint route if applicable |
| Cyber fraud payment | Bank and 1930 | cybercrime.gov.in |
| Telecom billing | Telecom operator grievance | Sector appellate authority route |
For cyber fraud, report quickly at cybercrime.gov.in or call 1930. Read fake work from home job scams and Telegram trading group scams if your complaint started with a scam.
Evidence checklist. Save the invoice, payment proof, ticket number, call log, chat screenshot, email copy, product photo, policy page, courier tracking page, company reply, and final closure message. Put everything in one folder before filing any escalation.
Use this folder structure:
Name files clearly:
2026-05-10-ticket-123-closed-without-resolution.png 2026-05-12-payment-receipt-rs-2499.pdf 2026-05-13-email-to-nodal-officer.pdf
Companies do not always use the same words. But the scripts sound familiar.
This line is safe for the company because it says nothing specific. Ask what process, which team, and what date.
Use this reply:
Please confirm the exact stage of processing, the team handling it, and the expected date of written resolution.
Sometimes this is true. Sometimes it is used to close tickets. Ask for call time and number.
Please share the date, time, and number from which the callback was attempted. My phone call log does not show a missed call from your support number.
Waiting once is fine. Waiting 48 hours 6 times is not fine. Count the waiting periods in your timeline.
Backend issue means an internal system problem. It does not explain anything to the customer. Ask for a resolution date and written confirmation.
Ask for the policy clause. A verbal refusal is weak. A written refusal can be challenged.
A public complaint on social media can harm a brand. Companies often move the user to private chat quickly. This is not always bad. Personal details should not be public. But the public thread should not disappear before a ticket is created.
Use this method:
This keeps pressure without exposing private data.
Repeated transfers are a classic exhaustion method. Sales sends you to support. Support sends you to accounts. Accounts sends you to branch. Branch sends you to app support.
After the third transfer, write:
I have been transferred between [team names] without resolution. Please assign one responsible officer or desk for this complaint and confirm the owner in writing.
If no owner is given, mention this in Consumer Helpline or regulator complaint.
Some complaints cannot wait for normal customer care.
Urgent issues include:
In urgent cases, call the emergency helpline of the bank, insurer, or service provider. Then send written proof immediately. For cyber financial fraud, call 1930 quickly.
Use this when attaching a PDF summary.
Complaint summary 1. Customer name: 2. Company name: 3. Product/service: 4. Order/account/policy number: 5. Amount involved: 6. Original complaint number: 7. Date of first complaint: 8. Current status shown by company: 9. Relief requested: 10. List of attached evidence: Short facts: [Write 8 to 10 lines only.]
A one-page summary saves time for the officer reading your complaint.
RTI does not apply to most private companies. But it can help when a public authority has records.
Examples:
For sports-event refunds, RTI cannot force a private organiser to pay. It can still help collect public records. See RTI for IPL ticket refund information.
Ask for records, not opinions. Example:
Please provide the current status and file movement details of my complaint number [number] received by [public authority] on [date].
See how to file RTI online in India before drafting.
Not always in the way you expect. Many companies promise callbacks as part of service practice. The stronger point is written grievance handling. Ask for a written reply, ticket status, and closure reason. For regulated sectors, check the official grievance policy of that sector.
Reply in writing that the issue is not resolved. Ask them to reopen the ticket or issue a written closure reason. Save the closure message. It can help in Consumer Helpline or regulator complaint.
Call recording rules can vary by app, device, and context. A safer method is to keep call logs and immediately send a written email summary after the call. Example: “As discussed at 4:10 pm, your agent said refund will be processed by 18 May.”
Use it after you have first complained to the company and have proof of delay, rejection, or no response. In urgent fraud matters, also use the cybercrime helpline 1930 and your bank immediately.
RTI normally applies to public authorities, not private companies. But RTI can help where a government regulator, public authority, or public sector body holds records about your complaint. Read how to file RTI online in India.
Ask for a specific date and written reason. If they cannot give one, escalate to the nodal or grievance officer. Attach your timeline and proof. Do not restart the story from zero.
15 May 2026