You have probably noticed it. You raise a complaint on your banking or payments app late at night, and somebody replies within minutes. Not a canned auto-reply, but a real person writing fluent English who appears to have your account open in front of them.
Many customers assume this is a bot. Often it is not. Here is how round-the-clock support actually works, and how to use it so your problem gets solved on the first attempt instead of the third.
Where that person is sitting
Most Indian banks run their own contact centres. But a large share of digital lenders, wallets, payment apps and international fintechs serving Indian customers run their support from outsourced operations — and a significant number of those sit in the Philippines.
There is a practical reason, and it is mostly about the clock. Indian evening hours — when most of us actually get round to checking our accounts — fall inside an ordinary working shift in Manila. Nobody is being woken up to answer you. Industry material on how financial technology firms build support teams in the Philippines describes the same arrangement from the company’s side: one floor, several markets, each covered during ordinary working hours for somebody.
None of this should worry you. The agent is working inside the company’s systems, bound by the same rules, and usually better trained on that specific product than a general bank branch employee would be.
“The person replying to you at eleven at night is working an ordinary day, not a graveyard shift,” said John Maczynski, chief executive of PITON-Global, an advisory firm that helps financial companies choose support partners in the Philippines. “That is the entire design, and it is why the answer reads like somebody who is actually awake.”
But it does change what you should expect, and what you should ask for.
What the agent can and cannot do
This is the part worth understanding, because it explains almost every frustrating support conversation.
Support agents work within defined authority limits. On most products, an agent can check your transaction, explain a charge, raise a dispute, reissue a card, unblock a login or arrange a callback. Those are decisions somebody has already authorised them to make.
What they usually cannot do is make a decision that commits the company — approving a loan restructure, waiving a charge above a certain value, closing a case with a final ruling, or anything that a regulator expects a named officer to own. Those go to a different team, often in India, and often only during business hours.
So if you are told “I will need to escalate this,” that is frequently not evasion. It is the process behaving exactly as it was built to behave. The useful response is not to argue with the agent but to ask three specific questions.
Three questions that speed everything up
“What is my reference number?”
Get it at the start, not the end. Every subsequent conversation becomes faster because the next agent can read the history instead of asking you to repeat it.
“What happens next, and by when?”
A clear commitment — “a specialist will review this within two working days” — gives you something to hold the company to. A vague one tells you the agent does not know, which is itself useful information.
“Is this logged as a complaint or as a query?”
This matters more than most customers realise. A complaint usually starts a regulated clock with defined timelines; a query does not. If you believe something has gone wrong rather than simply needing information, say the word “complaint” explicitly and confirm it has been recorded as one.
Getting it right the first time
A few habits make the difference between a single contact and a week of them.
Have the specifics ready before you start: the transaction date and amount, the last four digits of the card or the UPI reference, and what you expected to happen. Agents resolve faster when they are not drawing information out of you one question at a time.
Describe the outcome you want, not only the problem. “This ₹2,400 charge is not mine and I want it reversed” moves faster than “there is a problem with my statement.”
Use the channel that creates a record. In-app chat and email leave a trail you can refer back to. A phone call may feel faster but leaves you relying on the agent’s notes if the matter continues.
And if the first answer does not solve it, escalate by reference number rather than starting again. Beginning a fresh conversation resets your position and loses the history.
If it still is not resolved
Every regulated financial provider operating in India has a grievance redressal mechanism, a nodal officer and published timelines. If the app’s support team has not resolved your issue within the stated period, ask directly for the escalation to the grievance officer and quote your reference number.
Knowing that the first-line agent genuinely wants to close your case — and is measured on whether it stays closed — tends to make the conversation more productive than treating it as a contest.
Most support failures are not caused by the person on the other end. They are caused by the question never reaching somebody with the authority to answer it. The three questions above are simply the fastest way to find out whether it has.



