Claims lifecycle · Stage 01 of 08 · FNOL & intake
FNOL automation software: AI claims intake from any channel
The claim arrives complete, in your system, with severity flagged, however it was reported.
In short
Hesper AI is an AI claims resolution platform for P&C carriers, TPAs, and MGAs. Its intake agents capture first notice of loss from portals, email, phone, and agents; extract the facts from ACORD loss notices, emails, and photos; create the claim in your core system; and flag severity at intake, so the claim reaches the right desk with a complete file instead of a re-keying task.
Why does first notice of loss still slow claims down?
Most losses are still reported in ways a claims system can't read directly: an agent's email with a PDF loss notice attached, a broker's spreadsheet, a policyholder's photos, a phone call summarized in notes. Someone has to re-key it, chase what's missing, and decide where it goes.
Every day a claim spends in that state is a day before anyone investigates, reserves, or contacts the claimant, and a slow first contact sets the tone for the rest of the claim. NCCI's research on workers' comp found that claims reported later cost more and were more likely to involve an attorney. NCCI is careful to call that a correlation, not proof of cause, but it is a consistent one.
What does Hesper do at first notice of loss?
- Captures the notice from the channel it arrives on: portal, email, phone, or agent and broker submissions.
- Extracts the facts from ACORD loss notices, emails, attachments, and photos: parties, policy, date and location of loss, description, injuries, and damage.
- Creates the claim in your core system with the extracted data, so no one re-keys it.
- Flags severity at intake, along with early signals such as injuries, attorney involvement, or a possible liable third party.
- Hands the claim to triage with a complete file and the reasons behind each flag.
Does it replace our FNOL portal or chatbot?
No. If you already use a portal, a conversational FNOL tool, or a call center, Hesper works behind them. Front-door tools are good at collecting the report; Hesper turns whatever they collect, plus the attachments that come with it, into a complete claim file in your system of record.
That matters most for carriers, TPAs, and MGAs whose notices arrive through many channels at once, including agents, brokers, and client programs with their own formats.
How does intake connect to the rest of the claim?
Intake is the first of eight stages Hesper runs. The file built here carries through triage, coverage, investigation, settlement, and subrogation and recovery, so a liable third party noticed in the first report is not forgotten by the time the claim closes.
Hesper connects to Guidewire, Duck Creek, Majesco, and other claims systems through its API. See all eight stages on the claims lifecycle overview.
What does Hesper do, and what does your team decide?
| Hesper's agents | Your team |
|---|---|
| Captures notices from every channel | Owns the customer and agent relationship |
| Extracts the facts from forms, emails, and photos | Handles exceptions the agent routes to a person |
| Creates the claim in your core system | Sets the fields and rules your system requires |
| Flags severity and early signals | Decides on reserves and next steps |
What does the output look like?
- Source
- Broker email with an ACORD automobile loss notice and six photos
- Extracted
- Named insured, policy number, driver, vehicle, date, time and location of loss, police report number
- Created
- New claim in the core system with the extracted fields and attachments indexed
- Severity
- Elevated: claimant vehicle occupant transported to hospital
- Early signals
- Other driver cited per the notice: possible subrogation
Evidence cited
- Photo metadata matches the reported date and location
- Driver on the notice is a listed driver on the policy
- Police report number captured for retrieval
Recommended next action: Route to triage with injury and subrogation flags, and request the police report.
Frequently asked questions
What is FNOL automation?
FNOL automation captures and processes the first notice of loss without manual re-keying: reading the report and attachments, creating the claim in the claims system, and deciding where it goes next. Hesper does this across channels and flags severity at intake.
Which loss notice formats can Hesper read?
ACORD loss notices, such as the ACORD 1 property loss notice, ACORD 2 automobile loss notice, ACORD 3 liability notice of occurrence or claim, and ACORD 4 workers' compensation first report of injury, plus free-text emails, PDFs, spreadsheets from brokers or client programs, and photos. The agent extracts the same core facts regardless of format and records where each fact came from.
Does Hesper create the claim in Guidewire or Duck Creek?
Yes. Hesper connects to your claims system of record through its API and creates the claim with the extracted data and indexed attachments. It works with Guidewire, Duck Creek, Majesco, and other systems.
Can automated intake handle catastrophe surges?
Automated intake scales with volume, which matters most when a catastrophe multiplies the number of notices overnight. Claims still reach triage complete and flagged, so your adjusters spend the surge on the claims that need them.
How is Hesper priced?
Pricing is scoped to your book: lines of business, claim volume, and which agents you deploy. Book a demo and we'll walk through the economics for your claims operation and give you a real number.
Other stages of the claim
Book a demo of Hesper's intake agents
A 30-minute walkthrough on your claim types: from the first report to a complete claim in your system.
Book a demo