Digital Lenders: Training Recovery Partners on Two Notices

Quick answer
Digital lenders stay liable for recovery partners, and two notices may stack from January. What fintechs, NBFCs and service providers must teach partners.
A digital lending programme can look tidy on an org chart. The NBFC holds the licence. A fintech runs the app and originates the loans. A collections platform runs reminders. Two tele-calling vendors work the early buckets, and a network of field agencies takes the rest. Then a borrower complains about a call at 9 pm from a number nobody recognises, and all five organisations start pointing at each other.
RBI has already answered the question of who's responsible. Under the Digital Lending Directions, the regulated lender stays "fully responsible and liable for all acts and omissions of the LSP" (lending service provider), and it has to guide any LSP acting as a recovery agent (RBI Digital Lending Directions, paras 5(v), 5(vii)).
On 1 January 2027, the recovery Directions arrive on top of that (NBFC Third Amendment). So digital lender recovery partner training has become a practical question: what do people several contracts away from you need to know, and how would you prove they know it? Until 31 December 2026, the existing paragraphs still apply.
This post sticks to the partner chain and the notices. For the wider picture of fintech collections, see our post on collection training for fintech lenders. Have your counsel check everything here against your own structure.
The two notices
This is the most concrete change for digital loans, and we haven't seen it set out clearly elsewhere.
| Digital lending notice | First-visit notice | |
|---|---|---|
| Source | Digital Lending Directions, para 8(v) | Para 100L for NBFCs, 454L for commercial banks |
| In force | Now | From 1 January 2027 |
| Applies to | Digital loans | All loans under the Directions |
| Trigger | Default, when an agent is assigned or replaced | An in-person visit |
| What | Details of the agent go by email or SMS | Details of the agency |
| When | Before the agent makes contact | "At least one day prior to the first visit" |
| Covers phone calls? | Yes, it says before contact | No. On our reading, it applies to in-person visits |
On our reading, these two stack for digital loans from January. Your counsel should confirm this, but plan as though you'll need to satisfy both. Note that older guidance required telling the borrower about the recovery agent at sanction. That's from the 2022 guidelines, which were replaced by the 2025 Directions, so if your templates still rely on the sanction letter, you'll need to look again.
There are also two further triggers. If the agency changes, the borrower must get immediate notice (100M), and if it's terminated, the same applies (100N). In a fintech partner chain, where accounts move often between vendors, that's a lot of notices.
Here's an illustrative timeline for one loan.
| Day | Event | What the system should do |
|---|---|---|
| Day 0 | Loan overdue. Account moves to the tele-calling partner | Email or SMS with agent or agency details, before the first call |
| Day 4 | First call, 10 am, within 08:00 to 19:00 | Call logged and recorded |
| Day 31 | Account moves to a different vendor | Immediate notice of the change; new agent details by email or SMS before contact |
| Day 45 | Field visit planned | Agency details at least one day before the first visit; evidence stored |
| Day 46 | Field agent visits | Carries ID, authorisation letter and a copy of the notice |
Drawing this out for your own product will almost certainly reveal a step that nobody owns.
Why agents need to know about notices
You might think of notices as a systems job, and they largely are. But a person is often the last check.
A field agent needs a simple rule: don't go until the app shows the notice has been given. A tele-caller needs to know not to call an account that's just been reallocated until the notice has gone out. A team leader needs to be able to answer when a borrower says, "Who are you? Nobody told me."
If your allocation file doesn't carry this information, your partners can't follow the rule, however good your training is. So fix the data first, and then teach people to look at it.
Who counts as a recovery agency in your chain?
The definition is broad. A recovery agency is an entity or individual other than your own employees, engaged under an outsourcing arrangement, "irrespective of the contractual designation / nomenclature". A recovery agent is that agency's representative at the point of customer interface.
Go through your chain with that in mind.
| Partner | Likely position | Question to ask |
|---|---|---|
| Fintech LSP that also does collections | Within the definition if it does recovery under outsourcing, on our reading | Is it on your agency list? Do its callers hold the certificate? |
| Tele-calling vendor | Recovery agency; its callers at the point of customer interface | Do they know the rules are about them too? |
| Field agency | Recovery agency | Do its subcontractors appear on the list? |
| Reminder or automated voice vendor | Depends on what it does, and whether a person is involved | Where does it stop and an agent start? |
| Payment or software platform with no borrower contact | Possibly not, but check | What data does it see? |
The certificate point catches fintechs off guard. From January, agencies must engage only those agents who hold the IIBF certificate, and agents already engaged at NBFCs get one year (100I). A tele-calling vendor with fresh graduates hired last month needs a plan. See our certificate plan for NBFCs and agencies.
What RBI has already penalised
These two public penalties matter for digital lenders, because the charges are so specific.
| Lender | Penalty | What RBI cited | Inspection position |
|---|---|---|---|
| Navi Finserv | ₹3.80 lakh, February 2026 | Contacting customers after 7 pm and before 8 am for overdue loans; not following due protocol when sending messages | 31 March 2024 |
| Krazybee | ₹42.48 lakh, February 2023 | Failing to ensure recovery agents did not resort to harassment or intimidation; persistent or repeat complaints; breaches of the outsourcing code and Fair Practices Code | March 2021 |
The amounts aren't large. The time lag is what I'd pay attention to: in both cases, the penalty came about two years after the position inspected. What your partner's callers do this month could come up in 2028, by which time that vendor may no longer exist, and your records may be all you have.
These are small numbers of cases, and they don't suggest a wave of enforcement. In the list we reviewed for FY2025-26, only one of 70 RBI actions cited recovery conduct (FACE compilation, our text search). But they do tell you what's easy to check: time of contact and message protocol.
The risks that are specific to digital lending
A partner trained for a traditional book will miss these.
Contact lists and phone data. Law-firm summaries report that the Digital Lending Directions bar apps from accessing contact lists and call logs, apart from one-time access for KYC, though they vary in how strongly they state it (SS Rana). Check the RBI text yourself. Either way, a caller shouldn't be working from a list of a borrower's contacts, and the new text limits dues discussions to the borrower or guarantor anyway. Our post on tracing borrowers goes through this.
Volume and repetition. Digital books can generate a lot of automated contact. There's no daily number in the rules, but excessive calling or messaging is deemed harsh from January (100Z(4)). If your dialler, your reminder vendor and your agency are all contacting the same person, nobody may be counting the total. Someone should be.
Young borrowers and small tickets. A ₹15,000 loan may not justify a field visit, so pressure tends to concentrate on phone and messages, which is exactly where harsh practices show up.
Messages. Navi's penalty included a failure to follow due protocol when messaging customers. Messages sent by agents from personal phones aren't logged, aren't approved, and can't be retrieved. Bihar's Act, once in force, treats threats by SMS, WhatsApp, email or social media as a specific offence (Bihar Act). So we'd teach a simple rule: partners' agents don't message borrowers from personal accounts. Anything else that gets sent, on any channel, should go through what your legal team has approved.
Numbers. Reports describe 1600-series numbers being required for service and transaction calls by regulated entities. No RBI or TRAI text we found names recovery calls, so we won't state this as a rule for them. Ask your counsel what your vendors should be using, since a call from an unknown mobile number is exactly what borrowers complain about.
What partners must be taught
Here's a core set. Nothing on this list should take more than five minutes, and it can be sent to any partner, in any language.
| # | Lesson | What it covers |
|---|---|---|
| 1 | "Who are you calling for?" | Say your name and the lender's name. Anonymous calls are harsh practices |
| 2 | "Has the borrower been told?" | Check the notice status before contact |
| 3 | The clock | 08:00 to 19:00, with the date it starts; how to treat a request for another time |
| 4 | Only the borrower or guarantor | What to say if someone else answers |
| 5 | Nothing from their phone | No contact lists; nothing from social media |
| 6 | Approved words only | No personal WhatsApp, no shaming, no posting |
| 7 | Don't invent consequences | Bureau, legal action and police. False statements about the debt are harsh |
| 8 | You can't promise a settlement | Approval sits above you (RBI) |
| 9 | You're being recorded | Calls are logged and kept for six months; use the approved line |
| 10 | "I want to complain" | Give the grievance officer's details, every time |
Send items that change a current rule in the last days of December, with both dates stated. Our clause-to-lesson map has the timing.
How to run training across a partner chain
The hard part isn't content. It's reaching someone who works for a vendor of a vendor.
Write one code, and make it binding. You must have a code covering agents and employees, with an undertaking from each agency (100J). Don't let each partner write their own version. Issue yours, and ask them to send you their people's completion data, not just a signed undertaking.
Train the partner's people directly, if you can. If you hand a partner a PDF and ask them to cascade it, you'll get a signed declaration and very little else. It's better to send lessons straight to each agent's phone, and let the partner see their team's progress.
Get a live list. Tele-calling floors can turn over quickly. Ask each partner for a weekly list of who's on your accounts, and test it against your call logs. Our learner list post sets out the method.
Check calls. Pull a sample of recordings from each partner every month, and score them against the ten lessons. If one partner keeps failing lesson 4, send that lesson again to that floor, and raise it with the owner.
Tie it to allocation. Your policy has to set penal action for non-compliant agencies (100E). The practical version is that allocation follows conduct as well as recovery. Our agency checklist has a sample scorecard.
What belongs in the contract
The training problem gets much easier if the contract supports it. Ask your legal team to consider these.
- Everyone at the point of customer interface is named on a list, updated as they change
- Certificate status per person, with evidence
- Completion of lender lessons before accounts are allocated
- Access to recordings and logs, and the right to audit
- Rules on subcontracting: none without approval, and the same duties flow down
- Rules on data, including phones, screenshots and exports
- Penalties, and how they're applied
- Notice of any complaint or incident within a stated time
- What happens to records when the contract ends
That last line is underrated, given the two-year lag I mentioned above. If a vendor closes, you'll still need those recordings and training records.
Data protection is arriving on a similar timeline
The Digital Personal Data Protection Act's core duties are expected to begin in mid-May 2027, about four months after the recovery Directions, although sources differ on the exact day between 12 and 14 May (Shardul Amarchand Mangaldas). Commentators suggest the lender would generally be the fiduciary and the agency the processor, with written agreements covering scope, security, sub-processing, breach notice and retention.
So it's sensible to refresh your vendor contracts and training only once, for both. One detail for your counsel: RBI asks for call records to be kept for six months, and some readings of the DPDP Rules point to longer retention for certain logs. Check how these fit together before you set a deletion policy.
A plan for the next eight weeks
| Week | What to do |
|---|---|
| 1 | Draw the chain for one product: every entity touching a borrower. Mark who's a recovery agency |
| 2 | Draw the notice timeline. Find the gaps. Raise system changes |
| 3 | Get legal answers on stacking, on certificates for tele-callers and on messaging |
| 4 | Finalise the code. Issue it to partners. Get lists |
| 5 | Translate and review the lessons. Pilot with one partner floor |
| 6 | Roll out safe lessons. Brief partner team leaders |
| 7 | Update contracts. Pull a first sample of calls |
| 8 | Send date-specific lessons in the last week of December. Report status to your risk committee |
Where Leap10x fits
I run Leap10x, and we sell a training platform. Here's what it does and doesn't do.
Leap10x MicroLearning can send these lessons directly to any partner agent's WhatsApp, with no app or login, in languages including Hindi, Tamil, Telugu, Kannada, Marathi and Bengali. You can see completion by partner, team and person, and export it. That covers the "train the partner's people directly" part. Finnable and HDFC Bank are among our BFSI customers, and HDFC Bank has had "32,000 collection agents trained" on the platform, with "95%+ learner engagement".
This is about training your partners' staff. We don't send collection messages to borrowers, and nothing here should be read as advice on messaging them over WhatsApp or anywhere else. That's a question for your legal team. We also don't award the IIBF certificate. For more on how this fits your compliance programme, see our NBFC compliance training guide.
FAQ
Is a lender liable for its fintech partner's recovery conduct? Yes. The Digital Lending Directions say the lender stays fully responsible and liable for all acts and omissions of the LSP, and outsourcing rules say something similar.
Do both notices apply to a digital loan? On our reading, yes, from 1 January 2027: email or SMS before an agent makes contact, and at least one day before the first in-person visit. Have your counsel confirm this.
Do tele-calling vendors' staff need the IIBF certificate? On our reading, they fall within the definition of a recovery agent, since it covers the point of customer interface. NBFC lenders get one year for those already engaged.
Can agents message borrowers on WhatsApp? We'd teach partners' agents not to message borrowers from personal accounts. Whether and how a lender should use any messaging channel is a question for your legal team.
How do we prove partners were trained? Keep per-person records of lesson, version, date and score, alongside the undertaking. A signed undertaking alone doesn't show understanding.
The chain is yours
A partner model spreads the work, but RBI's text makes it clear that it doesn't spread the responsibility. Draw your chain, work out who's on it, and make sure each person at the end of it has heard the same ten things, in a language they understand. You'll want that record in 2028, when someone asks about a call made this January.
CTA: See how lessons reach partner agents directly, with records by partner and person. Book a Demo.
Frontline training
Training software built for deskless teams
Onboarding, SOPs, safety refreshers, and compliance evidence for workers with no corporate email and no company device — tracked by site, role, and shift.


