Case study · Insurance · Appointment Scheduling
How a multi-line insurance firm took time to offer a slot from hours to seconds
A multi-line insurance firm of 30-150 employees moved appointment scheduling off a manual queue and onto agents that run it continuously. The build, the numbers, and what stayed human.
Time to Offer a Slot
Book the insurance appointment that just came in.
Invite + reminder sent · routed to the right insurance rep automatically.
3 AI agents · 5 tools connected · live in 3 hours · no code
- Company
- Multi-line insurance firm
- Team size
- 30-150 employees
- Industry
- Insurance
- Time to live
- 3 hours
- Agents deployed
- 3 AI agents
- Tools connected
- 5 integrations
The context
Why Appointment Scheduling is hard in insurance.
Appointment Scheduling is not hard in the abstract. It is hard in insurance, where the work arrives as submissions, ACORD forms, carrier portals, claims notices, and renewal lists — every channel a different shape, none of them waiting their turn. The team runs against the renewal date and the claims service standard, so the real cost of a slow appointment scheduling step is never the step. 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 Appointment Scheduling used to wait. The right-hand chain has the same steps and none of the waiting.
By hand
- Request arrives on some channelwaits for office hours
- Coordinator checks availabilityin a separate system
- Times offered by replythree or four messages
- Booked, reminder by hand
or forgotten
With agents
- Work arrives on any channelpicked up in seconds
- Intake agenthanded straight on
- Booking agenthanded straight on
- Reminder agent
logged, and reviewable
When the work can happen
Before and after
What Appointment Scheduling cost them, and what replaced it.
The challenge
Scheduling was eating this multi-line insurance firm's front desk alive. Requests came in by phone, email, web form, and text, and each one started the same conversation: what do you have, does Tuesday work, actually can we move it. With 30-150 employees, the coordination team was spending most of the day inside that loop instead of on the work the appointments were for.
The full background
The cost showed up in two places. Empty slots, because a cancellation took hours to notice and longer to backfill, and no-shows, because reminders were sent by hand and only when someone remembered. Their insurance calendar looked full on paper and ran at meaningfully less than capacity in practice. Meanwhile requests that came in outside office hours simply waited — and a good proportion of those people had booked somewhere else by morning.
What they built
DeskFerry replaced the booking loop rather than speeding it up. The team connected Applied Epic, Gmail, and their calendar, then configured agents that read real availability — including the insurance constraints a generic booking link cannot see — and offer live slots in whichever channel the request arrived through.
How it was wired
The intake agent identifies the requester and works out what kind of appointment is actually needed before offering anything, which is what stopped the bookings that used to be manually unpicked. The booking agent writes the appointment, sends the invite with any preparation instructions, and holds the buffer the team asked for. The reminder agent covers the last mile: reminders at 24 hours and 2 hours with a reschedule link that works, and a cancelled slot offered straight to the waitlist rather than sitting empty. Requests that arrive at 11pm get answered at 11pm.
The impact
What changed, measured the same way on both sides.
Before and after across the metrics that matter for insurance Appointment Scheduling.
Time to Offer a Slot
Near-instant
Messages per Booking
Loop removed
Calendar Utilisation
Meaningful lift
No-Show Rate
Major reduction
After-Hours Requests
Always on
How these were measured
- Baseline
- The "before" column is the team’s own measurement of their manual appointment scheduling 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 Appointment Scheduling actually looked like for this insurance team — the version they described in the first call, and the version they run now.
Before DeskFerry
8:30
Six voicemails and nine emails asking for a slot. Start calling back.
10:00
Four rounds of "does Tuesday work?" for one appointment.
12:00
Double-book two people. Spend twenty minutes untangling it.
15:00
Send reminders manually for tomorrow. Miss two.
17:30
Tomorrow’s insurance book has three gaps and two no-shows waiting to happen.
After DeskFerry
8:30
Requests from every channel are already in one queue with real availability attached.
8:31
Each one got offered live slots within a minute of asking.
10:00
Confirmed bookings write straight to the calendar. No back-and-forth thread.
15:00
Reminders go out on their own, with rescheduling links that work.
17:30
Tomorrow is full, cancellations were backfilled from the waitlist.
The build
The 3 agents that run it.
One job each, with an explicit handoff between them. Splitting Appointment Scheduling 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
Intake agent
Trigger
A booking request arrives by form, email, or phone transcript
Identifies the requester, works out what kind of insurance appointment is needed, and reads live availability from the team calendar.
Agent 1 of 3 in the Insurance workflow.
- Offers real slots in the channel the request came from.
- 02
Booking agent
Trigger
A requester picks a slot
Writes the booking, sends the invite, adds any preparation instructions, and blocks the buffer the team asked for.
Agent 2 of 3 in the Insurance workflow.
- Hands a confirmed appointment to the reminder agent.
- 03
Reminder agent
Trigger
An appointment is 24 hours and then 2 hours out
Sends reminders with a working reschedule link, and offers a cancelled slot to the waitlist automatically.
Agent 3 of 3 in the Insurance workflow.
How they did it
From nothing to production in 3 hours.
No code, no IT ticket, no vendor implementation team. These are the steps in the order this team took them.
Step 01
Connected the insurance stack
Applied Epic, Salesforce, and DocuSign via pre-built connectors. No API keys, no custom code.
Step 02
Wrote the business rules
Scoring, routing, escalation thresholds, and exception handling for insurance appointment scheduling — in the visual builder.
Step 03
Tested on real history
Replayed a week of past appointment scheduling to check accuracy and surface edge cases, then adjusted the weights.
Step 04
Launched and watched
Live with close oversight for 48 hours, then down to a weekly review.
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
Appointment Scheduling handled end to end · seconds, every time
What stayed human
The parts they deliberately did not automate.
Automating Appointment Scheduling end to end was never the goal. Removing the volume so the judgement calls got proper attention was.
Complex or sensitive bookings
Anything needing multiple attendees, an interpreter, or special preparation is offered to a coordinator with the availability already worked out rather than booked automatically.
Repeat cancellations
A third cancellation on the same requester escalates to a person, because at that point the problem is not the calendar.
The fraud prevention 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
The routine appointment scheduling volume stopped needing a person. The judgement calls still get one.
- 02
Live in under a day — no IT queue, no development cycle.
- 03
Errors fell because validation runs before the write, not after.
- 04
It paid for itself on saved hours, not on a headcount cut.
In their words
“The ROI came quickly. Our appointment scheduling 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 Appointment Scheduling in insurance — what it takes, and where it stops.
How long does it take to set up appointment scheduling automation for a insurance business?
This team was live in 3 hours. 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 appointment scheduling automation actually need?
3 here: intake agent, booking agent, reminder 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 Appointment Scheduling 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 — Appointment Scheduling agent for Insurance.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Insurance case studies
Appointment Scheduling in other industries
Composite scenario — built from patterns across many insurance Appointment Scheduling deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.