DPD 31–90 is the most compliance-sensitive zone in the collections lifecycle. The institution must create urgency — the borrower has missed multiple payments and the risk of permanent default is growing. But the RBI's Fair Practices Code and collections guidelines set explicit limits on how that urgency may be communicated, when contact is permitted, what language is permissible, and what conduct is prohibited absolutely. The Mid Bucket Agent AI navigates this tension with precision: escalating urgency at each DPD stage while remaining within the exact boundaries the regulator draws.
The mid-bucket tension — urgency versus compliance
In the early bucket (DPD 0–30), the primary collections objective is engagement — getting the borrower into a conversation. In the mid bucket (DPD 31–90), the primary objective shifts: the borrower now knows they owe, knows they are behind, and in many cases has already broken one or more promises-to-pay. The institution needs to communicate genuine urgency — the consequences of continued non-payment are real and are approaching — while not crossing into the conduct that the RBI's Fair Practices Code prohibits.
The FPC prohibition list in collections is specific. Calling before 8 AM or after 7 PM is prohibited. Threatening violence or using abusive language is prohibited. Contacting relatives, employers, or third parties who are not guarantors is prohibited. Making false representations about the institution's legal authority is prohibited. Calling from numbers that are not registered with the institution is prohibited. In the mid-bucket, where both the borrower's stress and the institution's urgency are elevated, the probability of a human agent crossing these lines — particularly on a high-volume, high-pressure afternoon shift — increases significantly. The Mid Bucket Agent AI does not cross them. Its escalation is calibrated into its design.
What the RBI Fair Practices Code actually says about collections conduct
The RBI's Fair Practices Code for NBFC-MFIs and the collections conduct guidelines in the KYC Master Direction together specify: no contact outside 8 AM–7 PM, no abusive or threatening language, no contact with non-guarantor third parties, no false representation of legal consequences, no shaming or public exposure, no use of unregistered numbers, and written advance notice before visiting a borrower's residence. The Mid Bucket Agent AI has each of these as hard constraints in its operating parameters — they cannot be overridden by instruction or urgency.
The tone calibration scale: DPD 31 to DPD 90
The borrower has missed a full cycle — consequences are now stated clearly, not implied
At DPD 31, the AI shifts from the early bucket's assumptive oversight framing to a clear statement of status: "Your account is now 31 days past due." Credit bureau reporting is disclosed explicitly — not as a threat but as factual consequence. A specific resolution timeline is introduced: "Accounts at this stage typically move toward formal recovery proceedings after 90 days — we want to help you avoid that." The tone remains respectful and solution-oriented, but there is no ambiguity about the account's status.
FPC compliance: All calls between 8 AM and 7 PM · No language implying legal action before it is initiated · Bureau reporting disclosed factuallyThe institution's legal options are introduced as context — not as threats
At DPD 45, the AI introduces the legal and formal recovery process as a factual context: "At this stage, accounts in this status may be referred to our legal and recovery team — we would much prefer to resolve this with you directly." This is not a threat — it is an accurate description of what the institution does at this DPD stage, disclosed to the borrower so they can make an informed decision. The distinction is critical: the FPC permits accurate factual disclosure of legal options; it prohibits false representations or intimidation. A settlement offer or part-payment arrangement is introduced at this stage.
FPC compliance: Legal process described accurately, not used as intimidation · No false claims about imminent legal action · Restructure option offeredA specific timeline is given — the borrower is told when escalation will happen
At DPD 60, the AI provides a specific timeline: "Your account will be referred to our formal recovery process on [date] unless resolved before then." This is the most urgent pre-escalation communication — it names a date, names the consequence, and offers a resolution window. The AI simultaneously probes whether a hardship situation explains the continued non-payment, offering restructure or a formal review as an alternative to formal recovery. The tone is urgent but never threatening — the urgency comes from the timeline, not from the language.
FPC compliance: Specific date-based urgency is factual, not threatening · No third-party contact · Human agent pre-queued for same dayAI's role becomes facilitator — human agent or legal team takes over
At DPD 75–90, the AI's primary role shifts from collections to handoff facilitation. The AI makes a final-notice contact, states clearly that the account is moving to formal recovery, and offers one last resolution window before that handoff occurs. If the borrower engages, the AI captures the interaction details and immediately queues a human agent. If the borrower does not engage, the account package is assembled and transferred to the recovery or legal team with a full history of all AI contacts, commitments, and outcomes.
FPC compliance: Final notice is informational · Written notice requirement checked before any field visit · Account package includes full FPC compliance logWhat is permitted, what is required, and what is prohibited
| Conduct Area | Permitted | Required by FPC | Prohibited | Mid Bucket AI Approach |
|---|---|---|---|---|
| Contact hours | 8 AM to 7 PM only | All contacts within 8–7 window | Any contact before 8 AM or after 7 PM | All contacts scheduled and executed within 08:00–18:59 window — hard system constraint |
| Language and tone | Direct, firm, factual statements about account status and consequences | Respectful treatment regardless of DPD | Abusive, threatening, or degrading language | Tone calibrated by DPD stage — firm at DPD 45+, urgent at DPD 60+, never abusive — language reviewed against prohibited vocabulary list |
| Consequence disclosure | Accurate description of bureau reporting, legal process, recovery proceedings | Disclosure of credit bureau reporting before it occurs | False representations about legal action not yet initiated | Bureau reporting disclosed factually at DPD 31 · Legal process described accurately at DPD 45 · No exaggeration of institutional authority |
| Third-party contact | Contact with guarantors who have signed the loan agreement | Prior written notice to borrower before field visit | Contact with non-guarantor relatives, employers, or neighbours | Zero third-party contact unless guarantor flagged in loan record · Field visit notice generation automated before any field referral |
| Contact frequency | Reasonable frequency appropriate to DPD stage | Contact log maintained | Harassment through excessive or repeated contact | Contact frequency defined per DPD stage — maximum 2 attempts per day, with documented purpose. All contacts logged with timestamp and outcome |
| Settlement offers | One-time settlement, part-payment arrangements, restructure options | Any settlement offered must be confirmed in writing | Verbal settlement without written confirmation | All settlement or restructure offers auto-generated as written communication within 30 minutes of verbal discussion |
A DPD 45 script — firm, legally accurate, not threatening
The FPC is not a collections constraint — it is a quality standard
An institution that violates the Fair Practices Code in collections is not being more effective at collections — it is creating liability. A borrower who files an FPC complaint with the RBI Ombudsman forces the institution into a defensive process that is more expensive, more time-consuming, and more damaging to the borrower relationship than any amount that might have been recovered by the prohibited conduct. The Mid Bucket Agent AI never creates that liability — because compliance is built into the design, not added as an afterthought. The FPC exists because aggressive collections conduct is counterproductive even on its own terms: borrowers who feel harassed disengage, borrow from moneylenders to make partial payments, and become harder to recover. Respectful urgency consistently outperforms aggressive contact in DPD 31–90 resolution rates.