When a lending institution's repayment rate drops from 94.2% to 91.8% in a single quarter, two responses are possible. The first is a collections escalation: increase call frequency, add agents, and push harder. The second is a root cause investigation: why did the rate drop, and is the cause something that collections can address or something that an operational, product, or macroeconomic change has created? The Customer Insights Agent AI runs the second response automatically when repayment rate deviation is detected — correlating the timing of the drop with operational changes, external events, borrower segment shifts, and feedback signals, and surfacing the cause rather than the symptom.
Why collections escalation is the wrong first response to a repayment rate drop
A repayment rate drop has many possible causes. If the cause is economic — a sector-specific income shock, a localised employment disruption, a monsoon failure affecting agricultural income — then more collections calls will not improve the repayment rate. The borrowers who are not paying cannot pay. More calls produce more grievances, more FPC complaints, and no more collections. If the cause is operational — a processing error that caused NACH mandates to be submitted with wrong account numbers, an interest rate reset that changed EMI amounts without adequate notice, a system error that misapplied partial payments — then the collections team is calling borrowers who think they have already paid. If the cause is a product mix shift — the institution onboarded a new segment of borrowers in the prior quarter whose risk profile differs from the institution's historical portfolio — then the collections effort is addressing the symptom of an underwriting policy question. Each of these causes requires a different response. Only the root cause analysis can distinguish between them.
The root cause investigation: Q3 2025 repayment rate drop 94.2% → 91.8%
incremental
missers
incremental
missers
incremental
missers
The three responses — completely different from collections escalation
Textile sector
income shock
Response: proactive restructuring for the 378 affected MSME textile accounts
The Loan Modification AI prepares a revised repayment schedule for each of the 378 accounts in the textiles-affected geography — a 3-month moratorium with capitalised interest, followed by a step-up EMI schedule that matches expected sector recovery. The contact is a support call, not a collections call. The first word the account manager says is "we understand what is happening in the textiles sector" — not "your payment is overdue." For first-time missers in an economic shock, the institution that responds with understanding and a practical solution retains the relationship. The one that responds with a collections escalation loses it permanently.
No enforcement
NACH mandate
error
Response: mandate correction + penal waiver + borrower apology
The 184 affected accounts are identified and their NACH mandates corrected within 24 hours of the root cause being identified. Every penal charge accrued during the period of the error is waived. Every affected borrower receives an apology message explaining what happened and confirming that their credit record has been corrected. The IT team is given the root cause and the CBS migration audit is expanded to check all 48,000 accounts for similar errors. None of these borrowers should have been in a DPD position — the institution created their DPD through its own error.
Penals waived
DSA quality
issue
Response: targeted collections for 137 accounts + DSA quality review for the future
The 137 Q1 MSME accounts with DPD 90+ receive standard collections treatment — these are genuine credit events and the standard collections process applies. The parallel action is the policy response: the 6 DSAs whose Q1 MSME sourcing has produced early DPD rates above 12% are flagged to the DSA AI for performance review and commission hold. Origination criteria for MSME accounts sourced through these DSAs are tightened for Q4. The collections team addresses the symptom; the policy change prevents the next cohort from having the same problem.
+ policy fix
A 2.4pp repayment rate drop that triggers collections escalation before root cause analysis will escalate on the wrong accounts and miss the operational error entirely
The standard institution response to a repayment rate drop is to increase collections intensity across the portfolio. In this case, that response would have put collections calls on 841 first-time misser textile MSME borrowers who cannot pay because their sector's primary buyer disappeared — generating FPC complaints and permanently damaging 378 relationships that could have been restructured and retained. It would have put collections calls on 184 borrowers whose NACH mandates the institution itself corrupted — generating Ombudsman complaints and regulatory scrutiny. And it would have applied generic collections treatment to 137 genuinely high-risk accounts without identifying the DSA sourcing pattern that produced them. The Customer Insights Agent AI runs the root cause investigation before the collections escalation is approved — so the institution knows what it is actually dealing with before it decides what to do about it.