Case study · Insurance · Social Media
How a independent insurance agency took comment response time from days to same day
A independent insurance agency of 30-150 employees moved social media off a manual queue and onto agents that run it continuously. The build, the numbers, and what stayed human.
Posting Consistency
Draft this week's insurance social post.
Riley Nguyen · 1st
Independent insurance agency
Draft · today ·
How our Insurance team stopped doing social media by hand:
We handed it to an AI agent. Same tools, no new headcount — and it runs around the clock.
Here’s how it works →
3 AI agents · 5 tools connected · live in 2 hours · no code
- Company
- Independent insurance agency
- Team size
- 30-150 employees
- Industry
- Insurance
- Time to live
- 2 hours
- Agents deployed
- 3 AI agents
- Tools connected
- 5 integrations
The context
Why Social Media is hard in insurance.
Social Media 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 social media 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 Social Media used to wait. The right-hand chain has the same steps and none of the waiting.
By hand
- Empty calendar on Mondaythe slot competes with everything
- Post written oncethen rewritten per platform
- Published manuallyone channel at a time
- Comments pile up
nobody owns the inbox
With agents
- Work arrives on any channelpicked up in seconds
- Ideation agenthanded straight on
- Drafting agenthanded straight on
- Engagement agent
logged, and reviewable
When the work can happen
Before and after
What Social Media cost them, and what replaced it.
The challenge
Social was the first thing to slip every week at this independent insurance agency. With 30-150 employees and no dedicated social hire, it belonged to whoever had an hour spare, which in practice meant it belonged to nobody. Posts went out in bursts and then not at all for a fortnight.
The full background
The work itself was more repetitive than creative. Finding something worth saying, writing it, then rewriting it three times for three platforms with different lengths and conventions. Comments and DMs piled up in channels nobody owned, so genuine insurance enquiries sat unanswered next to spam. And because nothing was measured consistently, there was no way to tell which of the posts that did go out had been worth the hour — which made it very easy to justify skipping it again next week.
What they built
The team used DeskFerry to remove the overhead rather than the writing. Connected to Applied Epic, Gmail, and their social accounts, the agents pull material worth posting from real insurance product updates, support themes, and customer wins — not from a topic generator — then draft against the brand voice guide and produce the per-platform variants in the same pass.
How it was wired
Publishing stayed a human action on purpose. What went away was the two hours around it: the research, the reformatting, the resizing, the scheduling in four places. An engagement agent watches comments, mentions, and DMs, sorts them by intent, drafts replies, and routes anything that is really a support or sales conversation to the team that owns it — so genuine enquiries stopped sitting next to spam for three days.
The impact
What changed, measured the same way on both sides.
Before and after across the metrics that matter for insurance Social Media.
Posting Consistency
Plan actually executed
Time per Post
Overhead removed
Comment Response Time
Dramatically faster
Channels Covered
Full coverage
Cost per Published Piece
Major savings
How these were measured
- Baseline
- The "before" column is the team’s own measurement of their manual social media 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 Social Media actually looked like for this insurance team — the version they described in the first call, and the version they run now.
Before DeskFerry
9:30
Stare at an empty content calendar for the week.
11:00
Write three posts. Two are variations of last month’s.
14:00
Post manually, one platform at a time, resizing as you go.
16:00
Comments went unanswered for two days. Nobody owns the inbox.
Friday
No idea which insurance post did anything.
After DeskFerry
9:30
A week of drafts is waiting, built from real product and customer material.
9:50
Edit and approve. Platform variants were generated with the post.
14:00
Publishing runs on schedule across every channel.
16:00
Comments and DMs land in one queue, with drafted replies attached.
Friday
A performance summary arrives without anyone exporting anything.
The build
The 3 agents that run it.
One job each, with an explicit handoff between them. Splitting Social Media 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
Ideation agent
Trigger
The weekly content slot comes round
Pulls material worth posting from insurance product updates, support themes, and customer wins — not from a topic generator.
Agent 1 of 3 in the Insurance workflow.
- Proposes a week of angles for approval.
- 02
Drafting agent
Trigger
An angle is approved
Writes the post against the brand voice guide, then produces the per-platform variants with the right length and format for each.
Agent 2 of 3 in the Insurance workflow.
- Queues drafts for a human edit.
- 03
Engagement agent
Trigger
A comment, mention, or DM arrives
Sorts it by intent, drafts a reply, and routes anything that is really a support or sales conversation to the right team.
Agent 3 of 3 in the Insurance workflow.
How they did it
From nothing to production in 2 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 social media — in the visual builder.
Step 03
Tested on real history
Replayed a week of past social media 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
Social Media handled end to end · every planned slot, every time
What stayed human
The parts they deliberately did not automate.
Automating Social Media end to end was never the goal. Removing the volume so the judgement calls got proper attention was.
Publishing
Drafts are generated; a human presses publish. The time saved is in the drafting and the resizing, not in removing the last read-through.
Anything sensitive
Complaints, press, and anything touching a live incident are routed to a person rather than answered. The agent flags them fast, which is the useful part.
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 social media 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
“We went from spending half our day on social media to having it just happen automatically. The AI agents handle the routine work perfectly, and our insurance team can focus on the strategic decisions that actually move the needle. I wish we had done this a year ago.”
Composite — written from what teams running this workflow report, not a single named customer.
FAQ
Questions people ask about this build.
Automating Social Media in insurance — what it takes, and where it stops.
How long does it take to set up social media automation for a insurance business?
This team was live in 2 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 social media automation actually need?
3 here: ideation agent, drafting agent, engagement 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 Social Media 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 — Social Media agent for Insurance.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Insurance case studies
Social Media in other industries
Composite scenario — built from patterns across many insurance Social Media deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.