Case study · Insurance · Ticket Routing
Insurance Ticket Routing: Minutes → Seconds
The whole build: 3 ai agents, 5 tools, and the before-and-after on metrics the team already tracked.
Average Routing Time
A insurance customer just opened a ticket — handle it.
Customer
“Hi — I need help with my insurance account, it's been a few days with no update. What's going on?”
Agent draft · in your tone
Hi Alex — sorry for the wait! I've pulled up your account, resolved the issue on our side, and you're all set. I've also added a note so this is handled automatically next time.
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 Ticket Routing is hard in insurance.
Nothing about ticket routing 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 Ticket Routing used to wait. The right-hand chain has the same steps and none of the waiting.
By hand
- Tickets land unassignedone queue, no order
- Senior agent triagesthe most expensive hour of the day
- Category and priority guessedfrom the subject line
- Assigned, often wrongly
bounces for days
With agents
- Work arrives on any channelpicked up in seconds
- Classification agenthanded straight on
- Priority agenthanded straight on
- Routing agent
logged, and reviewable
When the work can happen
Before and after
What Ticket Routing cost them, and what replaced it.
The challenge
Support at this insurtech company was drowning in a problem that had nothing to do with support quality. Their agents were good; the tickets just kept arriving at the wrong ones. Categorisation was manual and subjective, priority was mostly guesswork, and the SLA clock started running long before anyone had read the ticket.
The full background
The insurance customer base spanned wildly different contract tiers, and none of that context reached the person picking up the ticket. A key account's outage looked identical in the queue to a routine question from a free trial. With 20-100 employees across the support function, the team was absorbing the cost of that blindness in overtime and in escalations that should never have escalated.
What they built
Rather than replacing their helpdesk, this insurance team connected Applied Epic and the team channel to DeskFerry and let agents own the first ninety seconds of every ticket's life.
How it was wired
The change that mattered most was that context now travels with the ticket. When an agent opens it, the account, the contract tier, the recent history, and the reason for the assigned priority are already attached — so the customer stops repeating themselves and the agent stops hunting through three systems before replying. Re-routes are handled by the same agent that assigned it, using the outcome as a signal, which is what stopped tickets ping-ponging between teams for days. The SLA clock starts on arrival rather than on first read.
The impact
What changed, measured the same way on both sides.
Before and after across the metrics that matter for insurance Ticket Routing.
Average Routing Time
Near-instant
First-Contact Resolution
Significant improvement
Misrouted Tickets
Major reduction
Customer Satisfaction
Notable increase
Support Cost per Ticket
Significant savings
How these were measured
- Baseline
- The "before" column is the team’s own measurement of their manual ticket routing 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 Ticket Routing actually looked like for this insurance team — the version they described in the first call, and the version they run now.
Before DeskFerry
8:00
Ninety tickets overnight, all sitting in one unassigned queue.
8:45
Triage by hand. Read, categorise, guess at priority, assign.
10:30
Three tickets have bounced between two teams since yesterday.
13:00
A P1 that arrived at 06:12 is only now being looked at.
17:00
First-contact resolution on insurance tickets is down again.
After DeskFerry
8:00
The queue is already categorised, prioritised, and assigned.
8:02
The 06:12 P1 was routed and acknowledged within seconds of arriving.
8:45
Agents start on tickets, not on sorting tickets.
13:00
Misroutes are rare enough to be worth investigating individually.
17:00
Every ticket has an owner and the SLA clock was never blind.
The build
The 3 agents that run it.
One job each, with an explicit handoff between them. Splitting Ticket Routing 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
Classification agent
Trigger
A ticket is created in any channel
Reads the whole ticket, categorises it against the insurance taxonomy, and detects the language and the real question underneath the subject line.
Agent 1 of 3 in the Insurance workflow.
- Passes a classified ticket to prioritisation.
- 02
Priority agent
Trigger
A ticket is classified
Weighs customer tier, contract SLA, sentiment, and blast radius to set a priority that means something, then starts the right clock.
Agent 2 of 3 in the Insurance workflow.
- Hands priority and reasoning to routing.
- 03
Routing agent
Trigger
A ticket has a priority
Assigns to the queue or person with the right skill and capacity, attaches account history, and posts urgent items to the team channel.
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 ticket routing 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
Ticket Routing handled end to end · seconds, every time
What stayed human
The parts they deliberately did not automate.
Automating Ticket Routing end to end was never the goal. Removing the volume so the judgement calls got proper attention was.
The resolution
Routing is automated; solving the ticket is not. The gain is that agents open a ticket that is already categorised, prioritised, and carrying its account history.
Ambiguous tickets
Low-confidence classifications go to a triage queue rather than being assigned confidently to the wrong team, which is the failure mode that costs the most time.
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 difference is night and day. Our insurance clients used to wait days for ticket routing to be completed. Now it happens in minutes, and the quality is consistently higher than what we achieved manually. Customer satisfaction scores went through the roof.”
Composite — written from what teams running this workflow report, not a single named customer.
FAQ
Questions people ask about this build.
Automating Ticket Routing in insurance — what it takes, and where it stops.
How long does it take to set up ticket routing 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 ticket routing automation actually need?
3 here: classification agent, priority agent, routing 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 Ticket Routing 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 — Ticket Routing agent for Insurance.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Insurance case studies
Ticket Routing in other industries
Composite scenario — built from patterns across many insurance Ticket Routing deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.