A customer signing up for cover is often asked to leave the WhatsApp conversation, download a separate app, and wait for a verdict before coming back to finish. WhatsApp-based identity verification means running that check inside the same thread the customer is already in, so the sign-up and the verification happen in one conversation instead of two disconnected ones. Where the redirect used to be, the conversation just continues.
Where Sign-Up Usually Breaks
Most KYC-gated sign-ups follow the same shape: a customer gets most of the way through an application, then hits a verification step that sends them somewhere else. They download an app they didn't have, work through an unfamiliar interface, and wait for a result with no visibility into how long that will take. Some come back. A meaningful share don't, not because they failed the check, but because the process asked them to leave what they were doing and pick it up again later, on a different screen.
Two Ways to Verify, Inside the Same Thread
WhatsApp-based verification offers two lanes, and the customer chooses which one to use. The photo lane asks for a picture of the identity document, then a second photo: a randomly assigned liveness challenge, like a specific gesture, captured fresh rather than reused from an earlier photo. The video lane captures both in a single short clip. Either way, nothing leaves the conversation the customer is already having, and nothing requires an app they don't already have installed.
Three Checks, Kept Separate
Verification is not one pass-or-fail decision. It is three independent checks, each producing its own verdict rather than being collapsed into a single opaque result.
| Check | What it confirms |
|---|---|
| Extraction | The fields on the identity document itself - name, ID number, date of birth |
| Liveness | A live person is present for the capture, not a static photo of a photo |
| Match | The person captured in the liveness moment is the same person shown on the identity document |
Keeping the three checks separate means each one can be reviewed on its own terms. A document that fails extraction is a different problem from a liveness challenge that fails, and a business trying to understand what actually happened with an application needs to see which check produced which result, not a single combined score.
What the Agent Sees
The verification results, the stage the customer is at, and the confidence behind each check appear inline in the same conversation thread the customer used, not in a separate audit tool the agent has to open and cross-reference. Anyone reviewing an application sees the same thread the customer went through, with the verification outcome attached to it rather than filed somewhere else.
How Long It Actually Takes
In three live test runs, verification completed in about two minutes, start to finish. That is a small, methodology-stated sample rather than an audited benchmark, but it reflects what the flow looks like end to end: document capture, liveness capture, and a result, without a redirect in between.
Wappari runs this inside WhatsApp for insurers and other regulated sign-up flows, where the funeral cover market has been the proven use case so far. The principle extends anywhere a KYC step currently sends a customer somewhere else to finish what they started in the conversation.