01Emailed documents
Documents read in the chat, the moment they arrive.
- Name, date of birth and address matched; anything missing asked for
- A video-KYC slot booked in the same conversation
Onboarding in hours
CommercialAutoKYC · onboarding & re-KYC for banks and NBFCs
Onboarding in hours, not days.
For banks, NBFCs and insurers. Customers send documents on WhatsApp or the web; AutoKYC reads them, checks them against your policy, asks for what is missing and hands only the exceptions to a person — with maker-checker before anything touches your core.
- < 24 h onboarding target
- Read-only by default
- One audit log for every action
WhySound familiar?
Three things we hear in every first conversation.
From heads of operations, onboarding and compliance at banks, NBFCs and insurers. Composite quotes from discovery calls — the problems are real; the names are left out.
-
“Half our applicants drop off waiting for documents.”
Documents arrive by email in pieces; each follow-up adds a day and loses a customer.
Head of onboardingMulti-day TAT, high drop-off
-
“Every application goes to a person, even the clean ones.”
Checks are manual, so the team spends its day on files that needed nobody.
Operations managerPeople on the wrong files
-
“Re-KYC season means frozen accounts and branch queues.”
Customers are asked to visit a branch to confirm what has not changed.
Compliance headFrozen accounts and complaints
HowWhat changes with AutoKYC
The same three problems, on the screens that solve them.
Product screens with illustrative data. In a working session we map one of your journeys.
02Every file manual
Only the exceptions reach a person — with the reason.
- Your policy applied the same way every time
- Maker-checker before anything is written to the core
People on the files that need them
03Branch re-KYC
Re-KYC on WhatsApp, by risk segment.
- Self-declaration where nothing changed; documents where it did
- Campaign progress by segment, with branch lists for the rest
No frozen accounts
FieldAutoKYC in the field
The people, the phone, the place.
The workplace it runs in, the person who uses it on a phone, the team at the desk and the detail it reads.
Photographs are illustrative — real customer sites are not shown.
- < 24 hOnboarding TATtarget · typically from 3–5 days
- 6–8 weeksTo first valueon one product journey
- Read-onlyBy defaultwrites only via APIs you open
- Maker-checkerBelow thresholdkill switch per agent
- Re-KYCOn WhatsAppno branch visit for most
- Cloud · VPC · on-premResidencyyour keys
01The screens
From a photo of a PAN card to an account opened.
The pipeline, the re-KYC campaign and the customer’s side on WhatsApp.
autowhat · AutoKYC / Onboarding pipeline
Illustrative data
Every application by stage, with documents read and checks run — exceptions explained.
Product screens with illustrative data — every name, place and figure is a placeholder.
02Before and after
Customers drop off while documents wait in email.
Onboarding and re-KYC still run on emailed documents and phone calls. That is where the days and the drop-off come from.
| Area | Today | With AutoKYC |
|---|---|---|
| Documents | Emailed, re-keyed | Read on arrival, matched to the application |
| Checks | Manual, uneven | Your policy, applied the same way every time |
| Exceptions | Everything goes to a person | Only exceptions, with the reason |
| Re-KYC | Branch visits, frozen accounts | Completed on WhatsApp by risk segment |
| Audit | Spread across systems | One log for every read, decision and write |
03Above your core
Five layers, one audit log.
AutoKYC sits above your systems of record. It reads by default and writes only through the APIs you open.
-
01
Converse
WhatsApp · web · branch
The customer starts where they already are — no new app.
-
02
Read
Document AI
ID, address and income documents structured on arrival.
-
03
Verify
Registries
PAN, CKYC and account-aggregator checks where you allow them.
-
04
Decide
Your policy
Rules and bands you write; outside the band, a person decides.
-
05
Approve
Maker-checker
Below threshold, a second person approves before any write.
-
06
Write
Your core
Account opened through the API you open — nothing else.
-
07
Remind
Re-KYC
Periodic re-KYC by risk segment, on WhatsApp.
-
08
Prove
Audit log
Every read, decision and write in one log.
04The platform
Journeys, documents, decisions and controls.
Start with one product journey; the same spine runs every other.
Journeys · 4
- Savings & current
- NRI accounts
- Loans & cards
- Insurance proposals
Documents · 4
- ID & address
- Income & business
- Video KYC hand-off
- Liveness & face match
Decisions · 4
- Policy rules
- Risk segments
- Exceptions queue
- Re-KYC schedule
Controls · 4
- Maker-checker
- Kill switch per agent
- One audit log
- Data residency
05How we deliver
One journey, one metric, six to eight weeks.
You pick the metric; we build on your stack and stay after go-live.
- Weeks 1–2 · MapThe journey, your policy and the systems in scope mapped; the metric agreed.
- Weeks 2–6 · BuildWhatsApp journey, document reading, rules and maker-checker on your stack.
- Weeks 6–8 · Go liveLive on one product with read-only defaults.
- Then · Next journeyRe-KYC and other products on the same spine.
FAQQuestions we get about AutoKYC
Straight answers, before the call.
AutoKYC is an Autowhat AI product for heads of onboarding, operations and compliance in BFSI. Short, factual answers for buyers, procurement and the assistants people ask first.
In short. AutoKYC is an Autowhat AI product for heads of onboarding, operations and compliance in BFSI. It is built for heads of onboarding, operations and compliance in BFSI. It exists to remove the problems those teams describe in almost every first conversation: multi-day onboarding and drop-off while documents wait in email; every file reviewed by hand, even the clean ones; and re-KYC season means branch queues and frozen accounts. With AutoKYC, teams get documents read in the chat; anything missing asked for, your policy applied the same way; only exceptions to a person, and re-KYC by risk segment on WhatsApp. It connects to WhatsApp Business API, CKYC / account aggregator, Your core via API and Maker-checker, is used by Customers · ops · compliance, and runs on whatsapp + web. Like every Autowhat AI product, AutoKYC goes live on one site, lane or process first, usually within weeks, on managed cloud, in your own VPC or on-premises, and shares one operational record with the other products, so the second deployment reuses the data and integrations of the first.
Who is AutoKYC for?
Heads of onboarding, operations and compliance in BFSI. Onboarding and periodic re-KYC for banks, NBFCs and insurers.
What problems does AutoKYC remove?
multi-day onboarding and drop-off while documents wait in email; every file reviewed by hand, even the clean ones; re-KYC season means branch queues and frozen accounts.
What do we get with AutoKYC?
documents read in the chat; anything missing asked for; your policy applied the same way; only exceptions to a person; re-KYC by risk segment on WhatsApp.
What does AutoKYC connect to, and who uses it?
It connects to WhatsApp Business API, CKYC / account aggregator, Your core via API, Maker-checker. Users: Customers · ops · compliance. Channel: WhatsApp + web.
How do we start with AutoKYC?
With a 30-minute working session on your own data — an engineer from the relevant sector, not a sales queue. The first wave is scoped in that call; most products go live on one site, lane or process within weeks and then scale.
Where does AutoKYC run, and who owns the data?
On managed cloud, in your own VPC (AWS, Azure or GCP) or on-premises, with your keys. SOC 2 Type II and ISO 27001 controls, India data residency when required, and local or open-weight models when policy demands it. The data stays yours.
06Working session
Name one journey and one metric. We’ll show you how it runs on your stack.
Thirty minutes: your onboarding steps mapped, the documents that slow it named, and a first scope.