ReKYC at scale: how NBFCs cut re-verification cycles by 72%
A deep dive into how risk-based triggers, WhatsApp reminders, and a self-serve portal transformed a 14-day ReKYC cycle into a 48-hour flow for a leading NBFC.
Why ReKYC breaks at scale
Periodic re-verification is simple in principle: confirm that what you know about a customer is still true. In practice, most teams run it as a batch exercise — export a list, send emails, chase replies and reconcile documents by hand. The work grows linearly with the customer base, and so does the backlog.
The result is a cycle measured in weeks, with compliance teams spending their time on follow-ups instead of on the cases that genuinely need judgement.
Trigger on risk, not on the calendar
Risk-based triggers flip the model. Instead of re-verifying everyone on the same schedule, the system scores each customer and opens a ReKYC case when the score or a regulatory deadline requires it. Low-risk customers get a lightweight confirmation; higher-risk profiles are routed for a fuller review.
Meet customers where they already are
Reminders that arrive on WhatsApp, with email and SMS as fallbacks, get opened. Each message links to a self-serve portal where the customer confirms details or uploads a document in a few taps — no branch visit, no call-back.
In the deployment described here, the WhatsApp-first self-serve flow drove a 72% customer response rate and brought the cycle from 14 days to under 48 hours.
Keep the audit trail automatic
Every reminder, response and document is logged against the case, so the audit trail builds itself. A bulk processing dashboard gives the compliance team one view of what is complete, what is pending and what needs a human decision.