Case study · Insurance · Follow-Up
Insurance Follow-Up: Days → On schedule
The whole build: 3 ai agents, 5 tools, and the before-and-after on metrics the team already tracked.
Time to Second Touch
A insurance contact went quiet — handle the follow-up.
3 AI agents · 5 tools connected · live in half a day · no code
- Company
- Insurtech company
- Team size
- 20-100 employees
- Industry
- Insurance
- Time to live
- Half a day
- Agents deployed
- 3 AI agents
- Tools connected
- 5 integrations
The context
Why Follow-Up is hard in insurance.
Nothing about follow-up is complicated on a single instance. What makes it expensive in insurance is volume arriving through submissions, ACORD forms, carrier portals, claims notices, and renewal lists, against the renewal date and the claims service standard. Miss the window and the cost is not the minutes — it is a renewal that lapses because a form sat in someone’s inbox.
Constraints the build had to hold
Forms are structured, and messy
Extraction is checked against each form type’s expected schema. Failures escalate rather than get guessed at.
Carrier rules differ
Each carrier gets its own branch inside one pipeline, rather than a pipeline nobody maintains.
Coverage decisions stay licensed
Anything constituting advice or a coverage determination is prepared for a licensed producer, never issued.
The change
Same job. Two chains.
Every handoff in the left-hand chain is somewhere Follow-Up used to wait. The right-hand chain has the same steps and none of the waiting.
By hand
- A promise is made on a callwritten in a notebook
- Nothing queries the notebookso nothing surfaces it
- Reminder set, then snoozedevery day for a week
- Thread goes cold
nobody notices which
With agents
- Work arrives on any channelpicked up in seconds
- Commitment agenthanded straight on
- Cadence agenthanded straight on
- Close-out agent
logged, and reviewable
When the work can happen
Before and after
What Follow-Up cost them, and what replaced it.
The challenge
This insurtech company had no systematic second touch, and it was costing them more than any single lost deal made obvious. Roughly a quarter of open insurance opportunities had gone more than two weeks without contact at any given moment, and the ones that had gone quiet were rarely the ones anyone chose to chase — they were simply the ones nobody remembered.
The full background
The root cause was that commitments lived in prose. They were in email threads, meeting notes, and chat messages, not in a field anything could query. Their 20-100 employees team had a CRM, but keeping it accurate required exactly the discipline that a busy week removes. So the list of who was owed a reply existed only in individual heads, and it decayed at the speed those heads filled up with the next thing.
What they built
The team used DeskFerry to make persistence structural instead of personal. Applied Epic and Gmail were connected on day one, and within an afternoon every open insurance commitment across the team was in one list with its age attached.
How it was wired
That list is the whole product of the project. Nothing is chased because someone remembered; things are chased because they crossed a threshold. Drafts arrive in the owner's voice with the history attached, which is why they get sent rather than rewritten. Replies close the loop automatically. The result is that the pipeline stopped having a quiet quarter of itself at any given moment, and the follow-ups that used to happen at day eleven now happen at day three.
The impact
What changed, measured the same way on both sides.
Before and after across the metrics that matter for insurance Follow-Up.
Time to Second Touch
Never missed
Open Commitments Tracked
Full visibility
Untouched Pipeline
Major reduction
Follow-Up Coverage
Full coverage
Revenue Left on the Table
Meaningful impact
How these were measured
- Baseline
- The "before" column is the team’s own measurement of their manual follow-up process, taken over the four weeks before anything was connected.
- Comparison
- The "after" column is the same measurement repeated on the same process once the agents were live, so both sides count the same things in the same way.
- Why no percentages
- These are composite scenarios built from patterns across many deployments, not one audited customer’s books. Directional language is the honest way to report that — your own numbers will depend on your volume, your process, and your starting point.
A day, either side
The same day, before and after.
What Follow-Up actually looked like for this insurance team — the version they described in the first call, and the version they run now.
Before DeskFerry
9:00
Try to remember who is owed a reply. Search the inbox for clues.
11:00
Find a proposal sent eleven days ago with no follow-up.
14:00
Set three calendar reminders. Snooze all of them tomorrow.
16:00
A deal goes cold because the second touch never happened.
Friday
Half the insurance pipeline has not been touched this week.
After DeskFerry
9:00
A single list: every open commitment, with the age of each one.
9:10
Drafts are ready for the ones due today, in your voice, with the thread attached.
11:00
Nothing is eleven days old — the cadence chased it at day three and day seven.
16:00
Replies reopen the thread and pause the sequence automatically.
Friday
Nothing in the pipeline went a week without a touch.
The build
The 3 agents that run it.
One job each, with an explicit handoff between them. Splitting Follow-Up this way is what makes a failure legible — you can see which step it went wrong at instead of debugging one agent that does everything.
- 01
Commitment agent
Trigger
An email, meeting note, or CRM update mentions a promise
Extracts who owes what to whom by when, across Gmail and Applied Epic, and keeps one list of open loops.
Agent 1 of 3 in the Insurance workflow.
- Feeds the open-loop list to the cadence agent.
- 02
Cadence agent
Trigger
A commitment ages past its threshold
Drafts the follow-up with the original thread attached, in the owner's voice, at the intervals the insurance team agreed.
Agent 2 of 3 in the Insurance workflow.
- Queues for one-tap send, or sends on approved cadences.
- 03
Close-out agent
Trigger
A reply arrives, or a commitment is met
Closes the loop, pauses the sequence, and updates the record so nothing chases a person who already answered.
Agent 3 of 3 in the Insurance workflow.
How they did it
From nothing to production in half a day.
No code, no IT ticket, no vendor implementation team. These are the steps in the order this team took them.
Step 01
Mapped the current workflow
Every step of the manual follow-up process, including exceptions — and which of them a person should keep.
Step 02
Built it in DeskFerry
Applied Epic and DocuSign as sources, insurance decision logic, automated actions and alerts.
Step 03
Ran it in parallel
One week alongside the manual process. Edge cases flagged for review rather than actioned.
The stack
Nothing was replaced. Everything was connected.
The insurance team kept the tools they already ran — DeskFerry sits between them.
Applied Epic
Policy, submission, and renewal state
Salesforce
System of record for accounts and pipeline; every write is scoped to owned fields
DocuSign
Signature events that start the workflow the moment a deal is real
Gmail
Where the work arrives, and where drafted replies go back out
Google Sheets
The lightweight ledger the team already reads, kept current automatically
Follow-Up handled end to end · on schedule, every time
What stayed human
The parts they deliberately did not automate.
Automating Follow-Up end to end was never the goal. Removing the volume so the judgement calls got proper attention was.
The tone of a chase
Drafts arrive in the owner’s voice, and the owner reads them. A follow-up that lands wrong costs more than one that lands late.
When to stop
The cadence has a hard end. Deciding whether an unanswered thread is worth reopening is a judgement call, and it stays one.
The claims processing speed question
Asked first by every insurance team. Agents run on the access the staff account already had, every action is logged, and any step can be stopped without unwinding what ran.
Takeaways
What transfers to your team.
The parts of this that are not specific to one company's tooling or volume.
- 01
Connecting the existing insurance stack beat replacing it.
- 02
Backlogs went away because the work no longer waits for office hours.
- 03
Quality stopped varying by whoever picked the task up.
- 04
Starting from a template and tightening the rules weekly beat designing it upfront.
In their words
“The ROI came quickly. Our follow-up throughput increased significantly while our error rate dropped dramatically. For a insurance business of our size, that translates directly to the bottom line.”
Composite — written from what teams running this workflow report, not a single named customer.
FAQ
Questions people ask about this build.
Automating Follow-Up in insurance — what it takes, and where it stops.
How long does it take to set up follow-up automation for a insurance business?
This team was live in half a day. Pre-built insurance templates cover the wiring, so most of that time goes on your business rules rather than on connecting things. No code.
How many AI agents does follow-up automation actually need?
3 here: commitment agent, cadence agent, close-out agent. The split matters more than the count — one job and one handoff each means a failure tells you which step broke. One agent doing everything does not.
What results can a insurance business expect?
The figures here are directional, not audited — composite scenarios, not one customer's books. What transfers is the shape: routine volume stops needing a person, exceptions surface instead of sinking, and nothing waits for office hours. Your numbers depend on your volume and starting point.
How does DeskFerry handle insurance data and access?
Agents run on the same access the staff account already had — throughput widens, permissions do not. Every action is logged with what it read and changed, and any step can be stopped without unwinding what ran. DeskFerry holds no formal insurance certification, so scope it as you would any other system in your control environment.
What still needs a person?
More than most automation pages admit. Anything outside the rules stops and goes to a named owner with context attached, rather than being guessed at. The rules themselves are changed by people — agents never widen their own tolerances. The carve-outs this team kept are named above.
What tools does this connect to?
1,500+ integrations. This build used Applied Epic, Salesforce, DocuSign, Gmail and Google Sheets; most insurance stacks are a variation on that. CRM, email, chat, databases, and industry-specific software all connect without code.
Run this in your own stack.
Describe how Follow-Up should work at your insurance business, in a sentence. DeskFerry builds the agents, wires your tools, and takes the routine volume from there. Start free — no credit card.
Or start from a template — Follow-Up agent for Insurance.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Insurance case studies
Follow-Up in other industries
Composite scenario — built from patterns across many insurance Follow-Up deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.