Automating PDD and Overdue Recovery Calls for UAE Lenders with Voice AI

UAE lenders managing large retail loan books face a scale problem that human call centres cannot solve efficiently: reaching every overdue customer at the right moment, with the right tone, in the right language, while staying within CBUAE conduct boundaries. Voice AI solves this by automating the full PDD recovery call waterfall — from first-day reminder to restructuring offer — at a fraction of the cost of human-only outreach.

What Is PDD in UAE Lending?

PDD stands for past-due date — the point at which a scheduled loan repayment has not been received by the lender. The moment an account crosses its due date, a lender's collections clock starts ticking.

Different lenders use slightly different internal terminology — overdue, delinquent, default — to describe accounts at various stages beyond PDD. For practical purposes, the PDD waterfall in UAE retail lending typically progresses through these stages:

The business imperative is to resolve accounts as early in this waterfall as possible. A customer cured at Day 5 costs far less to recover — in call time, human effort, and credit provision — than a customer who reaches Day 90.

Why UAE Lenders Face a Scale Challenge in Recovery Calling

UAE retail loan books have grown substantially over the past decade, driven by personal loan, auto finance, and credit card products across both the national and expatriate customer base.

That scale creates a fundamental operational problem. A mid-sized UAE lender may have thousands of accounts enter PDD status every month. Many of these will self-cure if contacted promptly and professionally. But calling every one of them with a human agent, in the right language, at the right time of day, with a compliant script — and doing it again the following day for those who did not pick up — is simply not achievable with a human-only contact centre at reasonable cost.

The results of inadequate early-stage contact are predictable: accounts that could have been cured at Day 5 drift to Day 30, credit provisions rise, and the cost of recovery increases significantly at every stage.

This is the problem voice AI was built to solve.

How Voice AI Handles the Full Recovery Waterfall

YuVoice automates outbound recovery calls across the full PDD waterfall. Here is how each stage works in practice.

Stage 1: Early PDD Reminder (Days 1–7)

At this stage, the majority of overdue customers are not willfully defaulting — they have forgotten, are temporarily illiquid, or have had a payment processing failure. The tone should be helpful, not adversarial.

YuVoice deploys a courteous reminder call that:

• Identifies the account and confirms the overdue amount
• Offers immediate payment via IVR DTMF or voice confirmation
• Provides a callback number for customers who wish to speak to a human
• Logs the outcome (paid, promise-to-pay, no answer, escalate)

This call is fully automated, requires no human agent involvement for the majority of outcomes, and can be deployed at scale across an entire PDD population within hours of the due date passing.

Stage 2: Active Collections (Days 8–30)

Accounts that have not self-cured by this stage require a more structured conversation. The customer may have a reason for non-payment — temporary hardship, disputed charge, or a payment already in transit — or they may need a short-term arrangement to resolve the balance.

YuVoice handles this stage with a more structured dialogue that:

• Acknowledges any previous contact and stated intentions
• Probes for reason for non-payment using structured branching
• Offers a short-term payment arrangement or partial payment
• Records any promise-to-pay with date and amount for downstream follow-up
• Escalates to a human agent when the situation requires judgment — disputed amounts, hardship declarations, or hostile customers

The system is connected to YuCamp for campaign orchestration, which manages the timing, sequencing, and outcome routing of all outbound contacts across the portfolio.

Stage 3: Intensive Collections and Restructuring Offers (Days 31–60)

Accounts reaching this stage require a more direct conversation that includes the possibility of formal restructuring. The CBUAE has specific conduct requirements around how lenders must communicate with customers at this stage — including the requirement to inform customers of their rights.

YuVoice deploys a compliant script at this stage that:

• States clearly the total amount overdue and any applicable fees
• Delivers the required regulatory disclosures in the customer's preferred language
• Presents restructuring options where they have been configured by the lender's credit team
• Captures the customer's response and routes to a specialist human agent for final agreement
• Documents the call for compliance purposes

This is a general explainer, not legal or compliance advice.

Stage 4: Pre-NPL Contact (Days 61–90)

At this stage, the lender's primary goal is either a final cure or formal escalation to a specialist or legal team. YuVoice contacts remaining overdue accounts with a formal tone, delivers required notices, and routes confirmed escalation cases to the appropriate team.

Voice AI at this stage primarily provides the documentation trail and ensures every account has received the required contact attempts before formal escalation, reducing the risk of procedural challenge.

Compliance with CBUAE Conduct Requirements

The Central Bank of the UAE publishes conduct standards covering how regulated lenders must treat customers in collections. Key requirements that apply to AI-driven recovery calls include:

• Contact time restrictions. CBUAE guidance limits the hours during which collections contact may be made. YuVoice enforces configurable contact windows that respect these restrictions automatically, so calls are never placed outside permitted hours.
• Disclosure obligations. Regulated disclosures — including the identity of the calling institution, the purpose of the call, and the customer's right to request a human agent — must be delivered at each contact. These are built into the YuVoice script layer and cannot be bypassed.
• Treatment of vulnerable customers. Customers who declare hardship, distress, or vulnerability must be escalated immediately to a trained human agent. YuVoice detects hardship indicators in speech and routes these calls out of the automated flow in real time.
• Record-keeping. Every call must be logged with a full transcript, outcome code, and timestamp. YuVoice produces these logs automatically, with storage compatible with CBUAE record-keeping requirements.

The Al Etihad Credit Bureau (AECB) is the national credit bureau and receives updates from lenders on account status. Accurate, timely reporting of PDD outcomes is part of a lender's obligations — and requires that the outcome data captured during collections calls is clean, structured, and actionable.

This is a general explainer, not legal or compliance advice.

Arabic and English Script Coverage in Recovery Calling

Recovery calls must be made in the customer's preferred language. In the UAE, that means both Arabic and English — and within Arabic, Gulf dialect is the norm for a significant portion of the customer base.

Generic collections scripts translated from English into Arabic often fail in practice because the tone, phrasing, and conversational structure that reads as professional and respectful in English can come across as blunt or even threatening in Arabic, particularly in the Gulf register.

YuVoice maintains separate, culturally authored scripts for Arabic and English at every stage of the recovery waterfall. This is not a translation relationship — each language version is developed with native-speaker input to ensure the right tone for the collections context.

Code-switching is handled as described in our piece on bilingual AI call agents: YuVoice detects the customer's language at the utterance level and responds in the appropriate language throughout the call.

Connecting Recovery Calls to Campaign Orchestration

Individual recovery calls do not operate in isolation — they are part of a broader contact strategy that sequences voice calls with SMS, email, and in-app notifications across the customer's delinquency journey.

YuCamp provides the campaign orchestration layer that determines:

• Which channel reaches each customer most effectively based on prior response data
• When to send a reminder SMS before a voice call to improve answer rates
• When to pause automated contact because a human conversation is in progress
• How to sequence re-attempts for no-answer calls without breaching contact frequency rules

This orchestration layer is what separates a collection voice bot from a collection strategy. The voice call is one touchpoint in a coordinated journey — YuCamp manages the full journey.

Measuring Recovery Call Outcomes

How do you know whether your voice AI recovery programme is working? These are the metrics that matter:

Comparing these metrics between AI-handled and human-handled populations — in a controlled rollout — is the most reliable way to quantify the value of automating recovery calls.

YuSight provides the analytics layer for recovery portfolio performance, surfacing these metrics at the portfolio, segment, and agent level to support data-driven decision-making.

What Voice AI Cannot Replace in Collections

Voice AI is not a replacement for human judgment in complex or sensitive recovery situations. It is a tool for scaling the high-volume, structured portions of the recovery waterfall efficiently.

Cases that should route to human specialists include:

• Customers in declared financial hardship
• Disputed charges or fraudulent transactions
• Customers expressing distress, hostility, or emotional difficulty
• Accounts requiring negotiated restructuring agreements
• Accounts with legal complications or multiple lenders

YuVoice is designed to identify these scenarios quickly and route them out of the automated flow. The goal is not to automate everything — it is to automate appropriately, so that human agents spend their time on the conversations that genuinely require human judgment.

Frequently Asked Questions

Q: At what stage in the PDD waterfall does voice AI work best? Early-stage PDD — Days 1 to 30 — is where voice AI delivers the highest value. Contact rates are higher, customers are more reachable, and the conversations are more structured. Later-stage recovery benefits from voice AI primarily for documentation and contact attempt logging rather than for direct cure.

Q: How does YuVoice prevent multiple automated calls irritating the same customer? Contact frequency limits are configured within YuCamp's orchestration rules. The system tracks all contact attempts across all channels — voice, SMS, email — and enforces the maximum contact frequency set by the lender's policy, respecting CBUAE conduct guidelines.

Q: Can a customer request a human agent during an automated recovery call? Yes. At any point in the call, the customer can request a human agent, and YuVoice routes them immediately. The call transcript and context are passed to the receiving agent so the customer does not have to repeat themselves.

Q: How does the system handle customers who speak only Arabic? YuVoice detects the customer's language at the first utterance and responds in Arabic for the entirety of the call. Gulf Arabic dialect tuning ensures that the system understands the natural speech of UAE customers rather than requiring them to speak in a formal register.

Q: Does automating recovery calls require changes to CBUAE-regulated processes? Any automated customer contact system in a regulated environment should be reviewed against the current CBUAE conduct framework before deployment. YuVoice is designed with CBUAE compliance requirements in mind, but each lender's compliance team must assess their specific obligations. This is a general explainer, not legal or compliance advice.

Q: How quickly can a voice AI recovery programme be deployed? A well-structured YuVoice deployment for early-stage PDD calling can go live in a matter of weeks, not months. The most time-intensive component is typically script review and approval by the lender's compliance team, not the technical integration.

Conclusion

UAE lenders face a scale challenge in recovery calling that grows with every additional loan on the book. Voice AI does not replace the human collections function — it ensures that every account receives a professional, compliant, language-appropriate contact at every stage of the PDD waterfall, without the cost and capacity constraints of a human-only model.

The result is faster cure rates at early stages, better documentation at later stages, and a human agent team that spends its time on the cases that genuinely require judgment rather than routine reminders.

YuVoice is built for UAE lenders, with bilingual scripts, CBUAE-aligned conduct controls, and YuCamp orchestration that manages the full recovery contact journey. Talk to the team to see how it fits your portfolio.

Talk to the YuVerse team

References

• Central Bank of the UAE (CBUAE) — https://www.centralbank.ae
• Al Etihad Credit Bureau (AECB) — https://www.aecb.gov.ae