A TAT breach is not just a process failure — it is a promise broken. When an institution tells a borrower "your loan will be disbursed in 7 working days" and the disbursement takes 11, the borrower experiences not only the delay but the silence: no one called to explain, no one offered a new date, no one acknowledged that what was committed was not delivered. The Onboarding SLA Agent AI's breach escalation workflow addresses both sides of the failure simultaneously. Internally, it escalates through a structured hierarchy until the breach is owned by someone with the authority to resolve it. Externally, it triggers a proactive borrower communication that acknowledges the delay, provides an honest revised timeline, and offers a direct contact for questions — before the borrower calls to complain.
Why breach escalation must be automatic — and why "the team knows" is not escalation
In most institutions, the response to an SLA breach is informal: the RM notices the delay, mentions it to the Branch Manager, and assumes someone is handling it. "The team knows" is not escalation — it is a shared awareness of a problem with no assigned owner, no deadline, and no accountability. The Onboarding SLA Agent AI creates formal, timestamped escalation events for every breach: an escalation is sent, received, acknowledged, and resolved — or escalated further if unacknowledged within the prescribed window. The escalation record is auditable, showing exactly who was notified at what time, whether they responded, and how the breach was ultimately resolved. This is the basis on which management can assess whether the escalation process is functioning, and the basis on which the institution can demonstrate to regulators that its TAT commitments are actively managed, not aspirationally stated.
The live escalation record: LA-2025-18808 · Home Loan ₹28L · 9-day breach
New timeline provided Nov 13, Nov 14
Borrower has not escalated to grievance
The four-tier escalation structure
75% SLA
consumed
A specific, time-aware alert to the responsible person — with the exact time remaining before breach
The Tier 1 alert fires at 75% of the step SLA. It is sent to the RM responsible for the application and the Branch Manager. It names the specific step, the time remaining, and the action required. It is not a generic "application at risk" notification — it is a specific operational alert with enough context for the recipient to act immediately. For credit assessment SLA at 75% (3 of 4 hours consumed), the alert says: "Credit assessment for LA-2025-18851 has 1 hour remaining. Analyst: Ramesh. Action required: complete assessment or escalate to Credit Manager if capacity is constrained." Response window: within the SLA remaining time.
SLA
breached
Formal breach notification with cause, impact, and a 2-hour acknowledgement window — plus borrower communication
At the moment of SLA breach, two simultaneous events occur. Internally: a formal escalation is sent to the Ops Head (for process steps) or the relevant functional head (Credit Head for credit steps, Legal Head for legal steps) with the breach cause, the downstream impact on overall TAT, and a 2-hour acknowledgement window. Externally: a proactive WhatsApp to the borrower acknowledges a delay and provides a revised timeline — before the borrower has experienced the silence that leads to a complaint. If the breach is due to an external party (valuer, borrower delay), the escalation includes documentation of the external cause.
T+2 hours
unacknowledged
If Tier 2 escalation is not acknowledged within 2 hours, the escalation goes to MD with a full breach summary
A functional head who receives a breach notification and does not acknowledge it within 2 hours triggers Tier 3: the MD receives a full breach summary — application ID, borrower name, product, amount, SLA commitment, breach duration, cause, and the Tier 2 escalation that was not acknowledged. The Tier 3 notification is not intended to override the functional head but to ensure senior management visibility of breach events that are not being managed at the operational level. In practice, most Tier 2 escalations are acknowledged within 30 to 60 minutes — Tier 3 fires rarely and signals a management attention problem rather than a process problem.
T+1 day
no resolution
24 hours after breach with no resolution: TAT risk is assessed, borrower updated again, and Board awareness triggered if the overall breach exceeds the product SLA by 3+ days
If a breach extends 24 hours with no resolution, the SLA Agent AI recomputes the expected overall disbursement date and assesses whether the commitment to the borrower is recoverable or requires a formal revision. A second borrower update is sent with the revised date. If the overall breach will exceed 3 days beyond the product SLA, the Board Risk Committee is notified as part of the monthly SLA performance report — large TAT breaches are a governance metric that the Board monitors under the enhanced oversight framework for NBFCs.
The borrower who receives 3 proactive updates about a delay does not file a grievance. The borrower who waits 11 days in silence and then discovers the loan is late does.
Surekha Naik's loan is taking 10 days instead of 7. She has received 3 WhatsApp updates from the institution: Nov 13 ("delay in property visit, arranging new visit"), Nov 13 afternoon ("new timeline: disbursement by Nov 17"), Nov 14 ("property visit completed today, on track for Nov 17"). She knows exactly what is happening, why it is happening, and when it will be resolved. She has not called the branch. She has not filed a grievance. She is slightly frustrated — she was told 7 days and it is taking 10 — but the institution's proactive communication has converted a potential complaint into a managed expectation. The internal escalation resolved the valuer problem in 24 hours. The external communication prevented a grievance that would have taken 48 hours to resolve. The SLA Agent AI's escalation workflow does two things simultaneously: it resolves the internal problem and it manages the borrower relationship through the problem. Both matter. Both are automated. Neither requires a campaign manager, a customer care agent, or a manager's morning review.