Case study · Healthcare · Resume Screening
How a regional medical group took time to first screen from over a week to hours
A regional medical group of 100-500 employees moved resume screening off a manual queue and onto agents that run it continuously. The build, the numbers, and what stayed human.
Time to First Screen
New candidate just applied — screen them.
Casey Flores
Applicant · Healthcare · role rubric
ICP fit
3 AI agents · 5 tools connected · live in 90 minutes · no code
- Company
- Regional medical group
- Team size
- 100-500 employees
- Industry
- Healthcare
- Time to live
- 90 minutes
- Agents deployed
- 3 AI agents
- Tools connected
- 5 integrations
The context
Why Resume Screening is hard in healthcare.
Nothing about resume screening is complicated on a single instance. What makes it expensive in healthcare is volume arriving through referral faxes, patient portal messages, phone calls, and EHR work queues, against the appointment book and the payer clock. Miss the window and the cost is not the minutes — it is a record touched by the wrong hands, or a detail dropped between a referral and a chart.
Constraints the build had to hold
Protected health information
Agents were scoped to the records the staff account could already see. Throughput widened; access did not.
The EHR is the system of record
Nothing counts as done until it is in the chart. Agent queues are scratch space, never a second truth.
Clinical judgement stays human
Agents move information and prepare decisions. Anything clinical goes to a person with the context attached.
The change
Same job. Two chains.
Every handoff in the left-hand chain is somewhere Resume Screening used to wait. The right-hand chain has the same steps and none of the waiting.
By hand
- Applications stack uphundreds on one opening
- Read in whatever gaps existoften not for days
- Judged against a drifting bardifferently at forty than at four
- Shortlist emailed
everyone else hears nothing
With agents
- Work arrives on any channelpicked up in seconds
- Parsing agenthanded straight on
- Scoring agenthanded straight on
- Coordination agent
logged, and reviewable
When the work can happen
Before and after
What Resume Screening cost them, and what replaced it.
The challenge
This regional medical group was losing good healthcare candidates to slowness, not to competition on package. Time from application to first screen averaged well over a week, and most of that was queue time — applications waiting for a human with the context to assess them.
The full background
Consistency was the second problem. Different reviewers weighed the same background differently, and nobody could reconstruct why a specific candidate had been passed over, which made the process hard to defend and impossible to improve. Scheduling added the rest of the delay: booking a screen took an email thread and two rounds of availability. With 100-500 employees and several roles open at once, the recruiting function spent most of its time on coordination rather than on judgement.
What they built
The team used DeskFerry to make screening consistent first and fast second. The rubric was written down properly — requirements, weights, what evidence counts — and the agents apply it identically to application four hundred and application four.
How it was wired
Speed followed from that. Applications are scored on arrival, so the shortlist exists before a hiring manager sits down, and every applicant hears back the same day. Scheduling stopped being an email thread. Because scoring is explained rather than asserted, the healthcare team can audit its own funnel: which requirements are actually filtering people out, and whether that is what they intended. Hiring managers own the rubric and review it per role, since an agent scoring against a stale rubric is worse than no agent at all.
The impact
What changed, measured the same way on both sides.
Before and after across the metrics that matter for healthcare Resume Screening.
Time to First Screen
Dramatically faster
Applications Reviewed
Full coverage
Scoring Consistency
Significant improvement
Candidates Who Hear Back
Full coverage
Cost per Hire
Major savings
How these were measured
- Baseline
- The "before" column is the team’s own measurement of their manual resume screening 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 Resume Screening actually looked like for this healthcare team — the version they described in the first call, and the version they run now.
Before DeskFerry
8:30
Two hundred applications on an open role. Start at the top.
10:00
Skim forty. Realise the rubric drifted somewhere around fifteen.
13:00
A strong candidate from Tuesday has already taken another offer.
15:00
Schedule screens by email. Four threads, no confirmations.
Friday
The healthcare req is still open and the pipeline is stale.
After DeskFerry
8:30
Applications are scored against the same rubric, every one of them.
8:35
The shortlist has evidence attached: which requirement each answer maps to.
10:00
Every applicant heard back within the day, including the declines.
15:00
Screens are booked from live availability without an email thread.
Friday
Time-to-first-screen is measured in hours instead of weeks.
The build
The 3 agents that run it.
One job each, with an explicit handoff between them. Splitting Resume Screening 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
Parsing agent
Trigger
An application is submitted
Reads the resume whatever its layout, extracts experience and skills as structured evidence, and normalises titles across formats.
Agent 1 of 3 in the Healthcare workflow.
- Passes a structured profile to scoring.
- 02
Scoring agent
Trigger
A profile is parsed
Scores against the role rubric the healthcare hiring manager signed off, and cites the evidence behind every sub-score.
Agent 2 of 3 in the Healthcare workflow.
- Shortlists with reasoning attached; nothing is scored on a hunch.
- 03
Coordination agent
Trigger
A candidate is shortlisted or declined
Books screens from live availability and sends every applicant an outcome, including the ones who did not progress.
Agent 3 of 3 in the Healthcare workflow.
How they did it
From nothing to production in 90 minutes.
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 resume screening process, including exceptions — and which of them a person should keep.
Step 02
Built it in DeskFerry
Epic and Athenahealth as sources, healthcare 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 healthcare team kept the tools they already ran — DeskFerry sits between them.
Epic
The chart — read for context, and written back so it stays the record
Cerner
Second system of record; reconciled against the chart before any write
Athenahealth
Scheduling, billing, and clinical work queues
Kareo
Practice management, scheduling, and claim state
Google Forms
Structured intake so the first agent starts from clean fields
Resume Screening handled end to end · hours, every time
What stayed human
The parts they deliberately did not automate.
Automating Resume Screening end to end was never the goal. Removing the volume so the judgement calls got proper attention was.
Every rejection above the line
The rubric shortlists; a recruiter reviews the band just below the cut, because that is where a good candidate with an unusual background sits.
The rubric
Hiring managers own the criteria and the weights, and review them per role. An agent scoring against a stale rubric is worse than no agent.
The regulatory requirements question
Asked first by every healthcare 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 resume screening 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 difference is night and day. Our healthcare clients used to wait days for resume screening 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 Resume Screening in healthcare — what it takes, and where it stops.
How long does it take to set up resume screening automation for a healthcare business?
This team was live in 90 minutes. Pre-built healthcare 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 resume screening automation actually need?
3 here: parsing agent, scoring agent, coordination 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 healthcare 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 healthcare 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 healthcare 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 Epic, Cerner, Athenahealth, Kareo and Google Forms; most healthcare 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 Resume Screening should work at your healthcare 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 — Resume Screening agent for Healthcare.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Healthcare case studies
Resume Screening in other industries
Composite scenario — built from patterns across many healthcare Resume Screening deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.