Every claim checked for completeness the moment it arrives
When a claim arrives from your intake form or portal, the flow pulls out the policy number, claimant, date and place of loss, description, estimated value and third-party involvement. A claim with no policy number waits for your claims team to chase.
Operations · Insurance · Something arrives from another system · 5 stepsA person is asked at “Ask for the rest”
policy_number: HP-449120
claimant_name: Alex Example
date_of_loss: 2026-09-02
location: Kitchen of a ground-floor flat
description: Water leaking from the flat above has stained the kitchen ceiling and lifted the laminate floor.
estimated_value: (blank)
third_party_involved: The upstairs neighbour; their details are not yet provided
Why teams run it
Claims arrive incomplete, and the gap is usually found by an adjuster days later, after the file has been assigned and opened. Every one of those round trips adds days to settlement and another call from a claimant who has already told you what happened.
How it is governed
- Only a correctly signed webhook call can start a run.
- Absent details are left blank, never filled in by guesswork.
- An incomplete claim waits for a person; the flow assigns nothing itself.
- Every submission and decision is kept in the run history.
- Who runs it
- Claims operations managers; Claims handlers; Intake and first notification teams.
- What you supply
- Your intake requirements as a knowledge source.
From template to a live agent
The same builder, tests and release review apply to a template as to anything built from scratch.
- Open it as a working flow
- Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
- Prove it before it ships
- An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
- Keep a person on the decisions
- A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
- Publish where people work
- A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.
- What teams usually change
- Choose which details must be present before a claim passes; Add fields your lines of business need, such as vehicle or property; Name the claims queue that chases incomplete submissions.
Questions buyers ask
- Does it decide anything about the claim?
- No. It reads what was submitted and checks it for completeness; there is no step that assesses liability, values a claim or makes a payment. Those decisions stay with your handlers.
- Can it ask the claimant for what’s missing?
- Not in this template. It pauses once and asks your claims team to chase, and their decision closes the run, so contact with the claimant stays with a person.
- What counts as an incomplete claim?
- By default a submission with no policy number stops for a person, and any other absent detail comes back blank. You can change the check in the builder so any field you choose must be present.
Related templates
All 60 templates- Process safety assistantAnswers process-safety questions from standards and guidance, citing the book and page.OperationsSomeone asks4 steps
- Incident report writerWrites an incident report in your house format, then a second agent checks it against the regulations.OperationsSomeone asks5 steps
- Field service assistantAnswers an engineer on site from the manuals, and can raise a work order once someone approves it.OperationsSomeone asks6 stepsa person approves
- Form processorTurns a scanned or photographed form into fields, reading the picture rather than expecting typed text.OperationsA document or recording is attached4 steps
See it run on your own data
We open it in the builder, point it at a sample of your documents and systems, and run it with you.