Fixed quote after a free call

First notice of loss automation for insurance agencies

When a client has a loss, the agency's job is to capture the facts accurately, get the notice to the carrier fast and keep the client informed. We build a workflow with a structured loss report on web or text, a policy check against the AMS, a notice prepared in each carrier's format for staff to send, document and photo chasers and scheduled update reminders for the claims handler. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why claim intake is slow at agencies

Losses arrive at the worst times: a storm on a weekend, a car accident in the evening, a water leak during a holiday. Clients call, email photos or text the producer they know, and details are written on whatever is to hand.

Speed matters. In California, every licensee who receives notice of a claim must immediately transmit it to the insurer, and the same expectation runs through most markets. After that, clients want to know what is happening, and the agency sits in the middle relaying updates from carrier portals by hand.

What we build

What our first notice of loss automation includes

Structured loss report

A short web or text form for date, location, what happened, injuries, other parties and photos, in plain language.

Policy check

The report matched to the client and active policies in the AMS so staff see the right carrier and policy number.

Carrier-ready notice

The loss details formatted for each carrier's portal or claims email, ready for a CSR to send the same day.

Document and photo chasers

Reminders to the client for photos, estimates, police reports or receipts the adjuster asks for.

Update reminders

Scheduled prompts for the claims handler to check the carrier and send the client an update.

Out-of-hours path

After-hours reports are acknowledged with the carrier's claims line and emergency steps, and queued for the morning.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Loss reported

    The client reports a loss by web form, text or call logged by staff.

  2. 02 Automated

    Policy matched

    The report is matched to the client's active policies in the AMS.

  3. 03 Automated

    Notice prepared

    Details are formatted for the carrier and a task goes to the CSR.

  4. 04 CSR or account manager review

    Staff send and follow up

    The CSR sends the notice the same day and works the update reminders.

  5. 05 Licensed agent or principal decides

    Coverage questions

    Whether a loss is covered is answered by the carrier and a licensed agent, never by automation.

How it behaves

How claim intake behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the client sees

  • A short, clear form or text conversation to report the loss
  • The carrier's claims line and next steps straight away
  • Regular updates from the agency until the claim closes

What CSRs see

  • A structured report matched to the policy
  • A carrier-ready notice and a send task
  • Chasers and update reminders on a schedule

What the automation does

  • Collects facts and photos consistently
  • Formats notices per carrier
  • Never comments on coverage or liability

Edge cases and fallbacks

Client has no matching policy
Flagged to staff to check before anything else happens.
Injury or emergency mentioned
The client gets emergency instructions and staff are alerted at once.
Several policies could apply
All are listed for the CSR to decide which carrier to notify.
Workflow or AMS down
The form still collects reports and emails them to the claims inbox.

Architecture

First notice of loss for an agency at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Client Web form or text n8n workflow Intake rules AMS lookup Policy and carrier Carrier notice Formatted report CSR Sends, follows up Chasers Docs and updates
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 The client reports a loss through a short web form or text conversation.
  2. 2 n8n matches the client and active policies in the AMS.
  3. 3 A carrier-ready notice is prepared and the CSR gets a task to send it the same day.
  4. 4 Document chasers and update reminders run until the claim closes.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

First notice of loss intake & claim updates project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current claim intake, carriers and their reporting routes, AMS access and after-hours process.

  2. 02

    Design

    2 to 3 days

    Loss form per line, notice formats, chaser timing and update rules.

  3. 03

    Build

    1 to 2 weeks

    Form or text intake, AMS match, notice formatting, tasks and chasers.

  4. 04

    Shadow run

    About 1 week

    Staff log real claims both ways and compare the prepared notices.

  5. 05

    Launch

    1 to 2 days

    Publish the claim form and train CSRs.

  6. 06

    Support

    Ongoing

    New carriers, formats and form changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Secure web form or Twilio SMS AMS API, SDK or export Carrier portals and claims email routes Slack or Microsoft Teams tasks Claude or OpenAI for loss summaries

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Forms per line, carrier formats and chaser rules.

    $200 – $400

  • Build

    Intake, matching, notice formatting and chasers.

    $500 – $1,300

  • Integrations

    AMS, messaging and task channels.

    $150 – $400

  • Testing and shadow run

    Real claims logged both ways and compared.

    $100 – $250

  • Launch and training

    Form launch and CSR walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Staff submit notices through carrier portals or agreed email routes unless a carrier offers a documented intake API. Software is billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing).
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Billed by the provider per use; loss summaries are short.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

California: transmit notice immediately

Under 10 CCR 2695.5(d), every licensee or claims agent who receives notice of a claim must immediately transmit it to the insurer.

Source: www.law.cornell.edu

US: AI in claims is governed

The NAIC adopted a model bulletin on insurers' use of AI in December 2023, so the workflow keeps AI to summarising and never assesses claims.

Source: content.naic.org

EU and UK: injury details are health data

Injury information is special category data under Article 9 GDPR and UK GDPR, so the form collects only what the carrier needs.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

First notice of loss intake & claim updates questions, answered.

It captures the facts of a loss in a consistent format, matches the policy, prepares the notice for the carrier and chases documents, so the agency reports claims faster and keeps clients informed.

Usually staff send the prepared notice through the carrier's portal or claims email. Where a carrier offers a documented intake route your agency is permitted to use, we can connect it.

Never. Coverage is decided by the carrier, and questions about it go to a licensed agent.

Yes. A guided text conversation collects the key facts and photos, and staff see the same structured report.

The client gets the carrier's claims line and emergency steps right away, and the report waits for staff in the morning.

Time from report to carrier notice, missing-document chases, update intervals and client complaints about claim communication.

Free 20-minute call

Want this for your insurance broker?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call