Case study · Logistics · Resume Screening
Logistics Resume Screening: Over a week → Hours
The whole build: 3 ai agents, 5 tools, and the before-and-after on metrics the team already tracked.
Time to First Screen
New candidate just applied — screen them.
Sam Okafor
Applicant · Logistics · role rubric
ICP fit
3 AI agents · 5 tools connected · live in 90 minutes · no code
- Company
- Regional freight company
- Team size
- 20-100 employees
- Industry
- Logistics
- Time to live
- 90 minutes
- Agents deployed
- 3 AI agents
- Tools connected
- 5 integrations
The context
Why Resume Screening is hard in logistics.
Nothing about resume screening is complicated on a single instance. What makes it expensive in logistics is volume arriving through tender requests, carrier APIs, EDI feeds, driver messages, and exception alerts, against the pickup window and the delivery appointment. Miss the window and the cost is not the minutes — it is an exception nobody saw until the customer called about it.
Constraints the build had to hold
Events arrive out of order
Reconciled on shipment identity rather than arrival order — which is what stopped the false exception alerts.
Exceptions beat status updates
Anything on plan stays silent. Attention goes only to shipments that have gone sideways.
Customer promises are explicit
Notifications repeat only commitments already in the system of record. Nothing is promised for operations.
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 freight company was losing good logistics 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 20-100 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 logistics 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 logistics 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 logistics 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 logistics 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 Logistics workflow.
- Passes a structured profile to scoring.
- 02
Scoring agent
Trigger
A profile is parsed
Scores against the role rubric the logistics hiring manager signed off, and cites the evidence behind every sub-score.
Agent 2 of 3 in the Logistics 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 Logistics 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
ShipStation and UPS API as sources, logistics 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 logistics team kept the tools they already ran — DeskFerry sits between them.
ShipStation
Fulfilment and carrier events that drive proactive notifications
FedEx API
Carrier scans and exception events
UPS API
Carrier scans and exception events
Google Sheets
The lightweight ledger the team already reads, kept current automatically
Slack
Where the team is told, and where approvals happen in one tap
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 delivery time accuracy question
Asked first by every logistics 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 logistics 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
“What impressed me most was the setup speed. I expected a months-long implementation, but we had AI agents handling our logistics resume screening workflow within a single afternoon. The no-code approach meant our team could configure everything themselves without waiting on IT.”
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 logistics — what it takes, and where it stops.
How long does it take to set up resume screening automation for a logistics business?
This team was live in 90 minutes. Pre-built logistics 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 logistics 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 logistics 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 logistics 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 ShipStation, FedEx API, UPS API, Google Sheets and Slack; most logistics 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 logistics 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 Logistics.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Logistics case studies
Resume Screening in other industries
Composite scenario — built from patterns across many logistics Resume Screening deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.