This is a walk-through of one call, start to finish, in an early-stage collections process for a personal loan. The customer, Sanjay, is invented, and so is the lender. Sanjay has missed two monthly instalments of ₹6,200 each, and late charges of ₹1,000 in total have been added. The overdue amount on the system is 2 × 6,200 + 1,000 = ₹13,400. The agent, Divya, has a list of accounts, a script outline, and permission to offer a limited set of options. We will go through the call stage by stage and say why each part is there.

Before the dial

Divya checks the account notes. Has Sanjay paid partially? Did he raise a dispute? Has he already promised a date that is still in the future? Calling a customer who has an open complaint or a valid promise is the quickest way to turn a routine call into an escalation. She also checks the time. The Reserve Bank of India directed in 2022 that recovery agents should not contact borrowers before 8 am or after 7 pm, except in special circumstances, and should not intimidate or harass them. Lenders’ own policies and client contracts often add further limits, such as how many calls per day or week. Dialler campaigns are normally configured around these rules, but the agent still owns the judgement about a particular call.

Opening and verification

The call connects. Divya says her name, the lender’s name, and asks for Sanjay. She does not mention the loan or the overdue amount to whoever answers if it is not Sanjay. Third-party disclosure is a serious breach: telling a family member or colleague that someone owes money is both a privacy violation and a conduct problem. If a different person answers, she asks for a good time to reach Sanjay and ends politely.

When Sanjay confirms he is speaking, she verifies identity with agreed details, for instance date of birth or the last digits of an account number, before discussing anything. In a collections funnel this is the “right-party contact”, and nothing about the debt happens until it is achieved.

State the purpose, then listen

“Mr Sanjay, I am calling about your personal loan. Two instalments have not been received, and the total due is ₹13,400. Can you tell me what happened?” Notice the sequence: a plain statement of the facts, and then a question. No accusation, no raised voice, no threat of consequences in the first minute.

Then she stops talking. Sanjay explains that his company delayed salaries by three weeks and that he expects them on the 20th. This is the heart of the call. She is looking for the reason because the reason determines what is possible: forgetfulness (a reminder and an easy payment link solve it), a temporary cash flow gap (a dated promise), a dispute (route to the right team), or genuine hardship (hand over to a specialist team or a restructuring option if the lender provides one). Agents who skip the listening step offer the wrong remedy.

Options within authority

Divya cannot waive charges or change the loan terms unless the process gives her that authority; making promises she cannot keep is worse than saying “I will check”. What she can usually do is explain the payment channels, offer to split the payment into two dates, and note a promise. Sanjay says he can pay ₹7,000 on the 20th and the rest, which is ₹6,400, by the 28th. Divya checks: 7,000 + 6,400 = 13,400. Good.

She also mentions, factually, that a further instalment will fall due next month, so the total will rise if the overdue amount is not cleared. This is not a threat. It is information the customer needs, and she says it in the same level tone as everything else. She avoids statements she cannot support, such as claims about legal action that has not been decided, and she never implies consequences for family or employer. Those are exactly the behaviours the conduct rules aim to prevent.

The dated promise

A promise-to-pay (PTP) is only useful if it is specific: amount, date, mode. “I’ll try this week” is not a PTP. Divya repeats it back: “To confirm, you will pay ₹7,000 on the 20th through the payment link I will send now, and ₹6,400 by the 28th. Is that right?” Sanjay agrees. She asks what might stop him paying on the 20th, which sounds odd but works: people name the real obstacle. If salary comes late again, he says, he will tell her. She gives him the helpline number and a callback preference.

Closing and recording

She thanks him, repeats the dates one last time, and ends the call. In the system she picks a disposition code for a promise to pay, sets the PTP amount and date, and writes a short note: reason for delay (salary delay), source of funds, any request. The note matters because the next agent, who might call on the 21st, needs the history without making Sanjay repeat himself.

What happens afterwards

A reminder message goes out the day before the 20th. If payment arrives, the promise is marked kept. If not, the account is queued for a follow-up call the next day, and a broken promise is recorded; teams often track the percentage of promises kept, because a PTP that is not honoured is a poor predictor of anything. Over time this “promise kept” rate tells you more about call quality than the raw number of promises taken. An agent who extracts ten promises that all break is doing less useful work than one who gets six that hold.

Collections work is judged on recovery, but the call above shows that it is mostly an exercise in respectful problem-solving under rules. The agent who stays calm, verifies before disclosing, listens before offering, and writes down exactly what was agreed protects the customer, the lender, and herself.

Figures and names in the examples are illustrative.

Leave a Reply

Trending