Case Study

Case Study: Insurance Agency Renewal & Service Automation

We built a connected set of automations for an independent insurance agency writing personal and commercial lines: a CRM pipeline linked to the AMS, a renewal pipeline with early information requests, first notice of loss intake, certificate of insurance requests and an AI service assistant. CSRs now work from structured requests instead of a shared inbox, and licensed agents spend their time on advice and the market.

Agency type
Independent agency, personal and commercial lines
Team involved
Principal, producers, account managers and CSRs
Systems connected
Agency management system, CRM, website, email, Twilio, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Quote requests arrived by phone, email and web form and were tracked in AMS notes. Producers followed up when they remembered, and nobody could say which sources produced bound policies.

Commercial renewal information requests went out late, so account managers often renewed as-is rather than remarketing.

Claims were reported by phone and email in whatever format the client chose, and CSRs relayed carrier updates by hand.

Certificate requests and routine service questions filled the shared inbox, pushing renewal and claims work into the evening.

Goals

What the project had to change

  • Every quote request lands in one pipeline with an owner and a next step.
  • Renewals open at a set lead time per line, with information back before marketing starts.
  • Claims are captured in a consistent format and passed to the carrier the same day.
  • Certificate requests arrive structured and checked against the policy.
  • Routine service questions are answered from approved wording, with coverage questions going to licensed staff.

What we built

What we built, as one connected system.

01

CRM pipeline

We connected web forms, calls, email and referrals to one CRM pipeline linked to the AMS, with approved first replies, producer tasks, a cross-sell list and a weekly report by source and line.

Service details
02

Renewal pipeline

Renewals now open at lead times set per line, clients receive prefilled information requests with reminders, and account managers get a change summary against last year.

Service details
03

First notice of loss

Clients report losses through a short form or text conversation, matched to their policies, with a carrier-ready notice and send task for CSRs, plus document chasers.

Service details
04

Certificate requests

A COI request form and email parsing feed a policy check, flags for special wording, drafts for CSR approval and a holder list for reissue at renewal.

Service details
05

AI service assistant

Website chat and a text line answer routine questions from approved wording, collect change and certificate requests and hand coverage questions to licensed staff.

Service details

Architecture

How the agency's workflows connect

Website and chat Forms, assistant Email and texts Requests, claims AMS Policies, expiries n8n Five workflows AI drafting Parse, summarise CRM pipeline Leads, tasks Client messages Email and SMS CSRs Requests, notices Licensed agents Advice, renewals Log and reports Weekly summary
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Website forms, the assistant, email, texts and AMS data feed one n8n instance.
  2. 2 Five workflows update the CRM, send client messages and use an AI step to parse requests and summarise changes.
  3. 3 CSRs handle structured requests and carrier notices; licensed agents advise and market renewals.
  4. 4 Every step is logged, and a weekly summary shows the measures the agency agreed to track.

How it behaves

How the system behaves day to day

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

What clients see

  • A quick reply after any quote request
  • Early renewal requests with last year's answers prefilled
  • A simple way to report a claim at any hour
  • Fast certificate turnaround
  • An assistant that answers routine questions and hands over the rest

What staff see

  • One pipeline and one renewal board
  • Structured claims, certificate and change requests
  • Flags for anything needing judgement
  • A weekly report by source and line

What the automation does

  • Captures, sorts, reminds and chases on schedule
  • Applies consent and opt-outs across workflows
  • Never advises on coverage, comments on a claim or issues a certificate without a person

Edge cases and fallbacks

A client asks whether a loss is covered
No automated answer; a licensed agent and the carrier respond.
A certificate asks for additional insured status
Flagged for the account manager to confirm an endorsement with the carrier.
The AMS is unreachable overnight
Renewal runs are skipped and retried rather than sent from stale data.
A client opts out in one workflow
One shared opt-out list stops texts from every workflow.
Twilio or n8n has an outage
Forms still email the agency inbox and the principal gets an alert.

Integrations

What we connected

All integrations

NowCerts

Agency management system

Insureds, policies and endorsements for service and renewal workflows.

NowCerts REST API and webhooks.

AgencyZoom

Agency CRM

Leads, opportunities, pipelines and policies for sales and service.

AgencyZoom API (OpenAPI spec), with keys from its Integrations page.

DocuSign

E-signature

Signed applications, renewal forms and authorisations.

DocuSign eSignature REST API and Connect webhooks.

Twilio

SMS and voice

Reminders, claim intake by text and opt-out handling.

Twilio Programmable Messaging and Voice APIs.

Microsoft 365 and Gmail

Email

Carrier correspondence, requests and staff alerts.

Microsoft Graph and Google APIs.

Slack and Microsoft Teams

Staff alerts

Claims, flagged certificates and failure alerts.

Incoming webhooks and APIs.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We shadowed CSRs and account managers, mapped quotes, renewals, claims, certificates and service requests, confirmed AMS access and agreed what stays with licensed staff.

  2. 02

    Design and access

    Week 2

    Message templates approved by the principal, pipeline stages, renewal lead times, consent and opt-out rules, API access and Twilio A2P 10DLC registration.

  3. 03

    Sprint 1: CRM

    Week 3

    Built the pipeline, first replies and producer tasks, run beside the old process.

  4. 04

    Sprint 2: renewals

    Week 4

    The pipeline went live. Built renewal scheduling, information requests and change summaries for one line.

  5. 05

    Sprint 3: claims

    Week 5

    Renewals went live for commercial packages. Built FNOL intake, policy matching and carrier notices.

  6. 06

    Sprint 4: certificates

    Week 6

    Claims intake went live. Built the COI form, email parsing, flags and holder list.

  7. 07

    Sprint 5: assistant

    Week 7

    Certificates went live for key commercial clients. Built the answer library, chat widget, text line and hand-offs.

  8. 08

    UAT and handover

    Week 8

    The team ran user acceptance testing on every workflow, then we switched everything on, handed over the run book and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures quote requests and sends first replies
  • Opens renewals and chases client information
  • Captures loss reports and prepares carrier notices
  • Parses certificate requests and flags special wording
  • Answers routine service questions from approved wording
  • Logs every contact and opt-out

The team does

  • Gather missing details and process change requests
  • Send carrier notices and work claim update reminders
  • Approve and issue every certificate
  • Reply to questions the assistant could not answer

Licensed agent or principal decides

  • Assesses needs and recommends cover
  • Presents risks to insurers and negotiates terms
  • Answers coverage and claims questions
  • Handles complaints and customers in vulnerable circumstances

Compliance handled

Privacy, consent and safety, built in.

No coverage advice by automation

Nothing about coverage, pricing or claims decisions is answered automatically; licensed staff handle it.

Claim notices passed promptly

Carrier notices are prepared for same-day sending, in line with rules such as California's requirement to transmit notice of claim immediately.

Source: www.law.cornell.edu

Information security

Vendors were reviewed against the agency's information security program under state laws based on the NAIC model.

Source: content.naic.org

Texting rules in the US

Promotional texts go only to clients with prior express written consent, and opt-outs are shared across workflows.

Source: www.law.cornell.edu

AI disclosure

The assistant says it is automated and offers a person, in line with Article 50 of the EU AI Act.

Source: artificialintelligenceact.eu

Certificates confer no rights

Requests for additional insured status are flagged because an endorsement is required.

Source: www.dfs.ny.gov

Outcomes

What changed for the practice

  • Every quote request now lands in one pipeline with an owner and a next step.
  • Commercial renewals open months ahead, and account managers see what changed before they market the risk.
  • Claims arrive in a consistent format and carrier notices are ready to send the same day.
  • Certificate requests arrive structured, and special wording is caught before anything is issued.
  • Routine service questions are answered from approved wording, and coverage questions reach licensed staff.

What we track

The measures the practice watches.

Quote follow-up

Time to first reply, quote rate and bind rate by source and line.

Renewals on time

Renewals opened at the lead time and information returned before marketing.

Claim notice speed

Time from loss report to carrier notice.

Certificate turnaround

Time from request to issued certificate and flagged requests.

Assistant resolution

Share of conversations resolved without a hand-off and unanswered questions per week.

Retention

Policies retained at renewal by line.

Cost estimate

What a project like this costs

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

    Process mapping, data flows, wording and the backlog for all five pieces.

    $1,000 – $2,000

  • CRM pipeline module

    Capture, first replies, tasks and reporting.

    $700 – $1,700

  • Renewal module

    Scheduling, information requests, chasers and change summaries.

    $800 – $2,000

  • Claims intake module

    Loss form, policy matching, carrier notices and chasers.

    $800 – $2,000

  • Certificate module

    COI form, parsing, flags and holder list.

    $500 – $1,300

  • Service assistant module

    Answer library, chat widget, text line and hand-offs.

    $700 – $1,600

  • Integrations

    AMS, CRM, Twilio and email connections.

    $200 – $400

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $300 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope, with the assistant kept to a focused service-only setup. Every agency gets its own fixed quote after a free call.

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), plus A2P 10DLC registration fees.
  • n8n: Self-hosted Community edition on the agency's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • CRM and AMS: The vendors' own plans.
  • AI usage: Pay-per-use AI model fees, usually small at agency volumes.

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

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.

Free 20-minute call

Want this built 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