AutoKYC: guides, playbooks and tools.

By the Autowhat AI team · Updated 7 Oct 2026

• Blog posts

• Why a KYC Agent Should Start Read-OnlyAn AI agent in KYC should start read-only: reading documents, matching details and asking for what is missing carry little risk, while writes to the core change records. Widen write access one API at a time, keep maker-checker below threshold, a kill switch per agent and one audit log.
• Start KYC Automation With One Journey, One MetricKYC automation stalls when it tries to fix every product at once. Pick one journey with real volume, a written policy and a clear pain, agree one metric, and go live within weeks with read-only defaults. The second journey reuses the channel, document reading, controls and core connection.

• Guides

• Digital KYC Onboarding on WhatsApp for BFSIDigital KYC onboarding on WhatsApp lets customers send ID, address and income documents in a chat; they are read on arrival, matched to the application, gaps asked for and a video-KYC slot booked. Policy rules route clean files on and exceptions to a person, with maker-checker and one audit log.
• Periodic Re-KYC Process for Banks and NBFCsPeriodic re-KYC works best by risk segment: customers with no change confirm by self-declaration where policy allows, those with changes send documents digitally, higher-risk cases go to a person, and non-responders get reminders and branch lists, with progress tracked by segment and every step logged.
• How to Reduce KYC Onboarding Drop-offKYC onboarding drop-off happens mostly while applicants wait: for app downloads, document requests by email, callbacks, video-KYC slots or decisions. Start on WhatsApp or the web, read documents on arrival, ask for gaps at once, book video KYC in the chat and send only exceptions to a person.

• Playbooks

• KYC Exceptions Playbook: Maker-Checker Done RightA KYC exceptions playbook writes policy as rules and bands, applies them to every file, sends only out-of-band files to a person with the reason, requires maker-checker approval before any write to the core, keeps systems read-only by default with a kill switch, and logs everything in one audit log.

• Comparisons

• Manual vs Automated KYC VerificationManual KYC collects documents by email, re-keys data and reviews every file unevenly. Automated, policy-driven KYC reads documents on arrival, applies your policy the same way every time and sends only exceptions to a person, with maker-checker before any write and one audit log.

The product behind these guides. AutoKYC — Onboarding in hours, on WhatsApp. Book a 30-minute working session.

More products and guides: all guides · all products · glossary.