Guide · Conversion
KYC onboarding drop-off: where applicants give up, and how to keep them.
Applicants rarely drop off because they changed their mind. They drop off while waiting: for a document request, a callback or a decision.
Where applicants drop off
| Stage | Why they leave |
|---|---|
| Download an app or open a long form | Too much effort before any value |
| Upload documents | Unclear what is needed; files rejected without a reason |
| Wait for follow-up | Each emailed request adds a day |
| Video KYC | No slot that suits them |
| Wait for a decision | No update on status |
How to reduce drop-off
- Start where the customer already is: WhatsApp or a short web link.
- Tell them exactly which documents are needed before they start.
- Read documents the moment they arrive and say at once if one is unclear.
- Ask for all missing items in the same conversation, not by email days later.
- Book the video-KYC slot in the same chat.
- Send clean files straight through; put people on the exceptions.
- Keep the customer updated on status at each step.
What to measure
- Time from first message to account opened.
- Share of applicants who finish, by stage.
- Share of files that needed a person, and why.
- Time an exception waits for review.
KYC requirements, periodicity and acceptable documents are set by your regulator and your own board-approved policy; confirm them with your compliance team.
How AutoKYC does it
AutoKYC handles onboarding and periodic re-KYC for banks, NBFCs and insurers. Customers send documents on WhatsApp, the web or at a branch; ID, address and income documents are read on arrival, and name, date of birth and address are matched to the application. Anything missing is asked for in the same conversation, and a video-KYC slot can be booked there too. PAN, CKYC and account-aggregator checks run where you allow them. Your policy rules and bands are applied the same way every time; outside the band a person decides, and only the exceptions reach a person, with the reason. Below threshold, maker-checker requires a second person to approve before anything is written to your core, and it writes only through the APIs you open; it is read-only by default, with a kill switch per agent. Re-KYC runs on WhatsApp by risk segment, and every read, decision and write is in one audit log. It runs on managed cloud, in your VPC or on-premises.
Questions
Why do customers drop off during KYC onboarding?
Mostly while waiting: for document requests by email, callbacks, video-KYC slots or a decision, rather than because they changed their mind.
How can banks reduce onboarding time?
Collect and read documents in a channel the customer already uses, ask for missing items at once, book video KYC in the same conversation and send only exceptions to a person.
See it on your own data. AutoKYC — Onboarding in hours, on WhatsApp. Book a 30-minute working session with an engineer.