Live demo | 2026.2 launch

What happens to claims email with no claim reference?

How to automate claims email triage with AI you can check. Every email and attachment read, matched to the right open claim, checked for what's missing and prioritised before your team opens it.

  • Wednesday 9 December 2026
  • 11:00 GMT
  • 45 min + live Q&A

With Frederic Stallaert and Maarten Callaert

Save your seat It takes 30 seconds. ↓
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Sound familiar?

Your claims team didn't get bigger this year. The inbox did.

After first notification of loss, the emails keep coming. Most of them land on claims that are already open, and plenty arrive with no claim reference at all.

  • 01

    The orphan email

    A medical report arrives with a policyholder's name and nothing else. Someone spends the morning finding its claim.

  • 02

    The shared mailbox backlog

    A solicitor's letter sits in a shared mailbox for two days because nobody could match it.

  • 03

    The storm surge

    A storm or a freeze hits, the inbox floods, and every handler is sorting instead of handling claims.

  • 04

    The pilot that stalled

    The AI worked in the demo, then stopped at risk review because nobody could show what it did.

For insurers and MGAsEvery day of sorting adds handling cost to every claim, and keeps a customer waiting.
For TPAsEvery day of sorting puts client SLAs at risk.

What changes

From an inbox you work through to a record you can work from

  • Someone opens every email to work out what it is

    Every email and attachment is recognised, checked and linked to the right client, policy and claim

  • Missing documents turn up when the handler opens the file

    Gaps are spotted first, with a request for what's missing ready for a person to send

  • Claims detail lives in inboxes and PDFs

    Every value is captured as data and linked to the page it came from

  • Nobody can show who checked what

    A full history of who checked or changed each value, and when

  • A storm hits and the backlog takes weeks to clear

    The surge runs on the team you have

What you'll see live

A working demo, not a slide tour

Four parts, in the order a claims email actually moves. Then open Q&A with the people who build and run it.

  1. The front door, handled

    Claims emails and attachments recognised, checked for completeness, prioritised and created as a ready task in the system your handlers already use. The hard documents (scans, photos, large packs) are read and come back clean.

  2. The record behind every value New in 2026.2

    Every extracted value stays linked to the page it came from, with a full history of who checked or changed it, and when. Reviewers correct, a second person signs off, and every version is kept.

  3. Under your control

    You decide where people review. Agents can never see or do more than the person using them. The record runs in your own cloud, with your own model.

  4. Where the line sits

    Your claims handler decides cover. The agents do the admin, so handlers work from a complete file they can defend.

Bring your most awkward claims email to the Q&A. We'll also share where we're heading next and ask what you'd like to see first.

Why it works

Automation should make you more resilient, not harder to explain

Most claims leaders already know AI can read their inbox. What stops them is that they can't see what it did, or the data would have to leave their environment to find out. So someone re-checks the output, or the project never gets past review.

Paperbox does the reading itself, so the link between each value and its source page is captured at that moment, not pieced together later. That link stays with the file for as long as the claim decision has to stand.

  • Linked to the source page
  • Full review history
  • Your people decide

If the regulator or your own audit team asked your AI to show its work tomorrow, could it?

Who it's for

Built for the people who own the claims file

  • Measured on customer outcomes

    Claims leaders at UK insurers

    See claims email reach the right handler without anyone sorting it, and claims data you can finally put to work.

  • Measured on SLAs

    Claims operations at TPAs

    See intake run on its own, so you can take on the next programme without hiring for it.

  • Measured on growth

    Underwriting and operations at MGAs

    See how the same front door handles submissions and policy changes, landing each one on the right account as a ready task.

  • Measured on resilience

    AI, data, risk and compliance leads

    See every value linked to its source page, the sign-off trail, how agent permissions work and how the record runs in your own cloud.

  • Customers and partners

    Already working with Paperbox?

    See what's new in 2026.2 and what it means for the work you already run with us.

Your hosts

Hear it from the people who build it

Save your seat
  • Frederic Stallaert

    Frederic Stallaert

    President & General Manager of Insurance, Paperbox, an Adlib Company

    Frederic co-founded Paperbox to automate insurance mailroom work, so teams spend their time on clients instead of admin. Based in Ghent, he brings a background in enterprise sales, data engineering and solution engineering to practical AI for claims, policies and customer communications.

    LinkedIn
  • Maarten Callaert

    Maarten Callaert

    Co-founder and Head of Sales, Europe, Paperbox, an Adlib Company

    Maarten co-founded Paperbox after working with leading insurers on their data and AI use cases at ML6, the AI services firm Paperbox was spun out of. A business engineer by training from Ghent University, he now leads sales for Paperbox across Europe.

    LinkedIn

Before you register

Questions we hear first

Is this a sales pitch?

No, it's a live product demo. You'll see the 2026.2 release working on claims email, then you can ask the team anything you like.

Can't make it live?

Register anyway and we'll send you the recording.

Do we have to replace our core system?

No. Paperbox creates ready tasks in the systems your handlers already use. How it connects depends on your environment, and we scope that with you up front.

Does the AI decide cover?

No. Your claims handler decides cover. Paperbox handles the admin before that decision: reading, matching, checking and routing the email.

Where does our data sit?

The record behind every value can be deployed in your own cloud, with your own model, so it stays inside your own security boundary. We'll cover the deployment options in the Q&A.

What does "a file you can defend" mean?

Every value Paperbox extracts is linked to the page it came from, with a full history of who checked or changed it, and when. A reviewer can see where a figure came from without re-reading the whole document.

How do Paperbox and Adlib fit together?

Paperbox is the insurance solution from Adlib. It brings together Paperbox intake with Adlib Transform, which reads the hard documents, and Adlib Trace, which keeps the record behind every value.

Is this only for claims?

This session focuses on claims email. Paperbox also handles submissions and policy changes for underwriting and policy admin teams.

See it live, then decide.

A live demo of the front door to your claims operation, and the record behind every value.

Save your seat Can't make it live? Register and we'll send you the recording.

Cut insurance admin time by 80% with Paperbox.

© 2026 Paperbox. All rights reserved.

Privacy PolicyTerms and ConditionsWebsite by Studio Neat