The moment a mid-bucket account is identified as a restructure candidate, the collections relationship ends and the operations relationship begins. This handoff — from the Mid Bucket Agent AI to the lending operations or customer solutions team — is not an escalation. It is a transfer of ownership, with a complete brief, a specific case classification, and a defined set of resolution options for the ops team to present to the borrower. The quality of the handoff determines the quality of the restructure outcome.
Why the handoff is where restructure cases succeed or fail
Restructure conversations fail most commonly not because the borrower does not want to restructure, and not because the institution cannot offer viable terms — but because the ops team receiving the referral does not have enough context about the borrower's situation to conduct a productive first conversation. The ops agent calls a DPD 55 borrower whose account has been escalated with no information beyond the account number, the amount due, and a flag that says "hardship — please review." The conversation starts from zero. The borrower has to re-explain their situation to someone new. The ops agent has no brief on what options might be viable. The first ops call fails to achieve anything, and the account ages further.
The Mid Bucket Agent AI assembles a complete case brief before the referral is made — the hardship signals that triggered the referral, the borrower's own words (from the conversation transcript) about their situation, the account's payment history, the current arrears and projected trajectory, and a structured assessment of which restructure options are likely to be viable based on the borrower's stated situation and financial profile. The ops team agent receives a brief, not an escalation number.
The referral decision: when does the Mid Bucket AI trigger a restructure referral?
Not every mid-bucket account is a restructure candidate. The Mid Bucket Agent AI triggers a restructure referral when one or more of three conditions is met: the hardship score exceeds the moderate threshold (score 45+), the borrower explicitly requests restructure or a moratorium during a conversation, or the AI's assessment suggests that the account is unlikely to self-cure — the combination of DPD age, broken PTP history, and engagement pattern indicates that further standard collections will not produce payment without a structural change to the loan terms.
The referral is not a write-off recommendation. It is a recommendation that the resolution pathway shifts from collections pressure to structured negotiation — a different tool for a borrower who is not refusing to pay but is genuinely unable to pay the current terms.
The 5-stage referral and handoff process
Referral Decision — Hardship score exceeds threshold or borrower requests restructure
The Mid Bucket AI generates a referral trigger when the hardship score reaches 45+ or when the borrower explicitly raises a restructure request. The trigger immediately pauses all standard collections contacts on the account and initiates the brief assembly process. The collections log entry is closed and a restructure case file is opened — the account is now in the lending ops workflow, not the collections workflow.
Case Brief Assembly — Complete borrower situation package generated
The AI assembles the full case brief: the borrower's account and payment history, the hardship signals that triggered the referral with their evidence, the key excerpts from the borrower's own statements about their situation (from call transcripts), the current arrears position and DPD trajectory, the borrower's income and financial profile at origination (to provide a baseline), and — critically — a structured assessment of which restructure options are likely to be viable given the borrower's situation and the institution's policy parameters.
Borrower Communication — Confirmation that the case has changed hands
The borrower receives a communication confirming that their account has moved from the collections queue to the customer solutions team: "We've reviewed your situation and have passed your account to our customer solutions team, who will call you within 4 hours to discuss options. No further collection calls will be made until then." This communication is critical — it prevents the borrower from experiencing the handoff as invisible, which often causes them to disengage further. It also creates a deadline that the ops team is accountable to.
Ops Team First Contact — Brief-informed conversation, not a cold call
The lending ops agent receives the case brief before calling the borrower. They know the hardship context, the borrower's stated situation, the account history, and the viable restructure options to present. The first ops call is therefore a structured conversation about options — not an exploratory call trying to understand a situation the collections team has already documented. The ops agent can immediately offer concrete alternatives: EMI holiday, repayment rescheduling, interest capitalisation, or a one-time settlement at a defined discount.
Outcome Logging and Monitoring — Restructure agreement or return to collections
The outcome of the ops team contact is logged in the case file. If a restructure agreement is reached, the new terms are documented, the loan modification is processed, and the account is monitored under the restructured terms. If no agreement is reached — the borrower declines all options or the options are not viable at the policy level — the case is returned to collections with the full context from the ops engagement, and the account is assessed for formal recovery. The Mid Bucket AI's monitoring continues throughout the restructured repayment period, flagging any early signals of the new terms being stressed.
The case brief: what the lending ops team receives
The AI's boundary: what it hands off and what it never decides
The brief is the handoff — not the escalation ticket
The difference between a 44% restructure resolution rate and a 78% rate is not the institution's restructure policy — it is the quality of the first ops conversation. A brief-informed ops agent who calls knowing the borrower's situation, their stated constraints, their payment history, and the two viable options to present is not making a collections call. They are making a resolution call. That call converts 78% of the time because the borrower is not being asked to re-explain themselves to a new stranger — they are being offered a solution that the institution has already understood they need. The Mid Bucket Agent AI's restructure referral process turns the ops team's first contact into the resolution conversation — not the intake conversation.