The claim already started on WhatsApp. The question is whether your system knows about it.
Your customers already claim and query on WhatsApp — usually on the broker's number, often after hours. Wappari turns that conversation into a validated, structured record in your claims or quoting system, without a portal or an app.
Wappari is a Chat-Native™ business execution platform. For an insurer or brokerage, that means the WhatsApp conversation stops being a place where work gets described and becomes the place where work gets done: the customer's message is read, the missing detail is gathered, the information is validated, and a structured record lands in the system you already run — while the customer is still in the conversation.
The first notification of loss arrives in a chat thread, not a claims system.
Your customers do not open a portal to report a bumper scrape. They send three photos and a sentence to whatever number they have — usually the broker's, often after hours.
That message is the first notification of loss. It contains most of what a claim needs. But it exists in a chat thread, not in a claims system — and the distance between those two places is covered by a person, manually, in working hours.
Take first notification of loss, end to end.
A customer sends photos of the damage and a short description. Wappari reads what arrived and works out what a claim of this type requires. It asks — in the same conversation, in the customer's own thread — only for what is genuinely missing: the date, the location, whether anyone was injured, the policy number if it can't be matched from the sending number.
It validates as it goes. A policy number in the wrong format is caught in the conversation, not three days later by a claims handler. Photos are attached to the record rather than left in a phone.
When the intake is complete, the customer gets a claim reference in the thread. The structured record — fields, media, timestamps, full conversation trail — is written into your claims system.
No portal. No app download. No form. The customer did what they were always going to do, and this time the system knows about it.
The same execution pattern runs a quote intake, a policy amendment, or a proof-of-payment confirmation. The process differs; the shape does not.
The same conversation — now it writes to your system.
| Today | With Wappari | |
|---|---|---|
| Where the claim starts | A chat thread on someone's phone | A chat thread — that writes into your system |
| Who gathers missing detail | A handler, in working hours | The conversation itself, immediately |
| Validation | After the fact, by a person | In-conversation, before the record is created |
| Customer reference | Issued once someone gets to it | Issued in-thread at completion of intake |
| After hours | Waits until morning | Intake completes; handler picks up a complete record |
| Audit trail | Screenshots, if anyone thinks to take them | Full conversation retained against the record |
| Three agents, one number | Duplicate replies, no accountability | Routed, tracked, attributable |
Insurance runs on evidence.
A conversation that lives on a personal handset is not evidence — it is a liability, and it walks out of the building when the person holding it leaves.
Wappari produces an auditable record: what was asked, what the customer answered, what was sent, when, and what was written to the system as a result. Not a screenshot. A retained trail attached to the claim or the quote — one that stays routed and attributable across every agent on the number.
Wappari does not make the underwriting call.
Wappari does not assess damage. It does not price risk, make an underwriting decision, or approve a claim. Those are your people's judgements and they stay that way.
What it removes is the part in between: the gathering, the chasing, the re-keying, the "can you send that again."
Questions insurers ask.
Does the customer need to install anything?
No. The conversation happens in WhatsApp, on the number they already use.
Does this replace our claims system?
No. Wappari writes into the system you already run. It is the execution layer between the conversation and that system, not a replacement for it.
What happens when a case needs a human?
It goes to one. Wappari handles intake and validation and hands over a complete record. Anything requiring judgement — assessment, pricing, approval — routes to your team with the full context attached.
Can several agents work the same WhatsApp number?
Yes. Conversations are routed and attributable, so two people don't answer the same customer and every response is traceable afterwards.
Is the conversation retained?
Yes — the full trail is held against the record written into your system.