The problem
Claim notifications arrive by email among renewals, quote requests and admin. A burst pipe that has left a family without a kitchen can sit behind a dozen routine messages until someone reads down the inbox. A broker sorting 80 claim emails a month at about 4 minutes each spends over 5 hours a month just working out what each one is and who should pick it up.
What the AI does
Jev is a decision model that software calls through an API; insurance claim triage is one of the uses TypeSafe lists. A Zapier automation sends each email that arrives at the claims address to Jev with questions set in advance: which class it belongs to (motor, home, commercial property, liability, other), whether it mentions an injury, and whether the property sounds unusable. Jev answers each with one of the allowed options or a probability. Zapier labels the email and sends the claims handler an alert for injuries and unusable homes. Anything Jev is unsure about is labeled for a person to sort. Every claim is still read and handled by a person: Jev only sets the order.
A worked example
A five-person general insurance broker in Kent receives about 80 claim notifications a month at a shared claims address. A developer sets up a Zapier automation that sends each to Jev, labels it by class and alerts the claims handler to injuries and homes that can't be lived in.
Before
About 4 minutes sorting each of 80 claim emails, over 5 hours a month
After
Claims arrive labeled, with about 1 hour a month on the uncertain ones and urgent losses called first
What it's worth
About $172£129€154A$248C$243 a month of time saved, against about $20£15€18A$29C$28 to $29£22€26A$42C$41 for Zapier and a few pence for Jev. Sorting drops from about 5.3 hours to 1 hour a month, saving 4.3 hours, which is $172£129€154A$248C$243 if that time is worth $40£30€36A$58C$56 an hour; reaching urgent losses sooner matters more but isn't counted.
How to set it up
- Check that TypeSafe will give you an API key from its console: Jev is in early access.
- Agree the claim classes and what counts as urgent with the claims handler, in plain words, as Jev's questions.
- In Zapier (Pro plan or above, which includes webhooks), trigger on new emails to the claims address and send each to Jev's API with your questions.
- Add steps that label each email, alert the claims handler for injuries and unusable homes, and label anything below your confidence level for a person to sort.
- Run it alongside your usual sorting for two weeks, compare Jev's labels with the handler's, and adjust the questions.
- Record every claim in your broking system as now: the labels are a reading order, not a claims record.
What goes wrong
- This is technical setup: someone has to build and maintain the Zapier steps that call Jev's API.
- Claim emails can include health details about injuries, which are special category data under UK GDPR. Check TypeSafe's and Zapier's terms and data processing agreements first; TypeSafe states it doesn't train on customer requests.
- A wrong or missing label must never delay a claim. Under the FCA's Consumer Duty the broker still owes every client fair, prompt handling, so read the whole claims inbox every day.
- Automations can fail silently. If labels stop appearing, check Zapier's task history; 80 claims use about 160 tasks, well inside the 750-task Pro tier.