Claim Intake (First Notice of Loss) · Insurance Agencies
Turn every claim report into an organized, carrier-ready FNOL
Each claim form becomes a prioritized HubSpot ticket, the insured gets your approved acknowledgement, and injuries or large losses alert your team right away.
Free account to start. Buying and running live need a paid plan.
- Starts when your form or app sends it something
- 1 AI step
- About 20 min to set up
Sound familiar?
The job, before and after this agent.
What it feels like today
- “Claim reports come in at night and nobody sees them until morning.”
- “We go back to the insured three times for details the carrier needs.”
- “An injury claim sitting in the inbox is the last thing we want.”
What you get with the agent
- Each report organized into a first notice of loss: insured, policy, loss, what happened, injuries, other parties and damage as stated
- Missing information the carrier will ask for and documents to gather, listed up front
- Injuries, large losses, ongoing damage and third-party claims posted to your Slack claims channel straight away
- A HubSpot ticket prioritized by severity, laid out to copy into the carrier's FNOL form and linked to the insured
- Your own approved acknowledgement wording emailed with a reference number, ending with a clear statement that it isn't a coverage decision
Before
A claim email arrives Saturday night. Monday morning someone reads it, calls the insured for the policy number and retypes everything into the carrier portal.
After
The insured got an acknowledgement and document list that evening. Monday, claims staff open a prioritized ticket ready to copy into the carrier's form, and any injury was already flagged in Slack.
How it works
The whole workflow, step by step.
When your report-a-claim form posts a submission, AI organises it into a first notice of loss: insured, policy, loss, what happened, injuries, other parties, reports and damage as stated. It lists the missing information a carrier will ask for and the documents to gather, and rates severity. Injuries, large losses (your amount), ongoing damage and third-party claims alert your Slack claims channel straight away. Every claim becomes a HubSpot ticket, prioritised by severity, laid out to copy into the carrier's FNOL form and linked to the insured's contact. The insured gets your own approved acknowledgement wording with their reference number and the documents to gather. It ends by saying it isn't a coverage decision. The agent drafts and organises for claims staff, who review every ticket. It makes no coverage or liability decision, never tells the insured whether they're covered and doesn't file with the carrier.
- TriggerClaim report from your form
- AI stepOrganise the claim report
- LogicClaim, urgent claim or not a claim?
- Not a claim:Not a claim
- Urgent:Alert claims staff in Slack
- Claim:Create the claim ticket in HubSpot
- OutputNot a claim
- App callAlert claims staff in Slack
- App callCreate the claim ticket in HubSpot
- App callFind or add the insured in HubSpot
- App callLink the ticket to the insured
- OutputSend your acknowledgement
- OutputClaim logged
This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.
- Step 1Claim report from your formYour website's report-a-claim form posts each submission to the workflow's webhook URL.
- Step 2Organise the claim reportAI turns the form into a clean first notice of loss: who, what, when and where, injuries, other parties, missing information, the documents to gather and a severity rating. It makes no coverage or liability judgement.
- Step 3Claim, urgent claim or not a claim?Submissions that aren't loss reports are kept aside; injuries, large losses and ongoing damage alert claims staff in Slack first; every claim becomes a HubSpot ticket.
- Step 4Not a claimThe run history keeps the submission and why it isn't treated as a claim; no ticket or email.
- Step 5Alert claims staff in SlackPosts the injury or large-loss summary to your claims channel straight away, before the ticket is created.
- Step 6Create the claim ticket in HubSpotCreates a HubSpot ticket with the organised FNOL, priority set from the severity, in the pipeline and stage claims staff work from.
- Step 7Find or add the insured in HubSpotCreates the insured's HubSpot contact, or updates the one with the same email.
- Step 8Link the ticket to the insuredLinks the claim ticket to the insured's contact so staff see the whole history in one place.
- Step 9Send your acknowledgementEmails the insured your approved acknowledgement wording with their reference number, what they reported and the documents to gather. It always ends by saying it isn't a coverage decision.
- Step 10Claim loggedThe run history keeps the organised claim, the ticket id and the acknowledgement sent.
Example run
What goes in, and what comes out.
Example with fictional data
Comes in
A fictional auto claim: rear-ended at a red light, bumper and trunk crushed, passenger taken to hospital to be checked, other driver says his brakes failed.
The agent produces
FNOL organized with the injury and third party noted, high severity. Slack alert posted. HubSpot ticket created and linked. The insured receives your acknowledgement with a reference number and a list including the police report and photos.
What you need
Everything it takes to run it.
About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.
Plan
Included in Enterprise; on other paid plans it's $129 once. Agents run live on paid plans, from Basic ($39/mo).
Your AI key
Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.
Checklist
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- HubSpot (with a ticket pipeline) and Slack, connected in Settings → Integrations.
- A claim form on your site that posts to the webhook and requires an email address, plus your approved acknowledgement wording.
Setup, about 20 minutes
- Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
- Connect HubSpot. Connect the HubSpot account where claims staff work tickets (Settings → Integrations → HubSpot).
- Connect Slack. Connect the Slack workspace your claims team uses (Settings → Integrations → Slack).
- Describe your claim setup. Open “Organise the claim report” and replace the placeholder with your agency name, lines and large-loss amount.
- Pick the claims alert channel. Open “Alert claims staff in Slack”, pick your Slack workspace and the channel for urgent claims.
- Pick the ticket pipeline. Open the three HubSpot steps, pick your HubSpot account in each, and choose the ticket pipeline and starting stage.
- Paste your approved acknowledgement. Open “Send your acknowledgement”, replace the placeholder with your approved wording and enter your claims inbox for replies.
- Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
- Switch the trigger on. Open the trigger, copy the webhook URL and signing secret into your claim form, and switch it on. Make the form's email field required.
Is it a fit?
Who it's for, and what it won't do.
Built for
- Independent insurance agencies handling claims for insureds
- Agency claims staff and customer service reps
- MGAs and small brokers with a report-a-claim form
What it doesn't do
- It drafts and organises for licensed claims staff. It makes no coverage, liability or fault decision, and the acknowledgement never tells the insured whether they're covered.
- It doesn't report the claim to the carrier or open a claim in a carrier portal: claims staff review every ticket and do that.
- The acknowledgement promises nothing beyond your own wording and ends by saying it isn't a coverage decision.
- It doesn't collect photos or files: the insured replies to your claims inbox with them.
- Severity and urgency come from what the insured wrote, so staff should still read every ticket.
We list the limits up front so you can decide before you buy.
Price
$129 one-time
Per workspace. It never renews.
- Included at no extra cost on Enterprise.
- Buying and running it live need a paid plan, from Basic ($39/mo).
- Dry Run costs nothing: simulated AI and app calls, nothing sent.
- AI usage is billed by your own provider, at cost. No AI credits to buy from us.
One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy
FAQ
Questions about Claim Intake (First Notice of Loss).
Will it tell the insured whether they're covered?
Never. It drafts and organizes for licensed claims staff, makes no coverage, liability or fault decision, and the acknowledgement uses only your approved wording and ends by saying it isn't a coverage decision.
Does it report the claim to the carrier?
No. Claims staff review every ticket and report it to the carrier. Severity comes from what the insured wrote, so staff should still read each ticket.
What do we need?
HubSpot with a ticket pipeline, Slack and a claim form that posts to the webhook and asks for an email. Setup takes about 20 minutes. It doesn't collect photos; the insured replies to your claims inbox with them.
Is it worth the price?
It's a one-time purchase that never renews, and it means every report is acknowledged and organized even when the office is closed. Live runs need a paid plan and your own AI key; Dry Run is free.
What does the insured receive?
Your own approved acknowledgement wording, their reference number, a short repeat of what they reported and a list of documents to gather. It ends with: “This email confirms we received your report. It is not a decision about coverage.”
Which forms work?
Your own website form, or any form tool that can post JSON to the workflow's webhook URL with its signature header. The form must ask for an email address so the acknowledgement can be sent.
Is this a subscription?
No. Claim Intake (First Notice of Loss) is a one-time purchase of $129 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.
Can I test it before it touches real data?
Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.
Put Claim Intake (First Notice of Loss) to work.
Free account, no credit card. Your Agents page opens with Claim Intake (First Notice of Loss) ready to buy and set up, then Dry Run it before it goes live.