Quick Answer
There are four options and they solve different problems. Software organizes the work but still needs somebody to do it. An in-house dispatcher works until they take leave. An answering service takes messages but does not dispatch. A full outsourced desk does the work and costs roughly $4,000-9,000 a month for a 50-trip-a-day fleet against $15,000-25,000 in-house. Below about 50 trips a day, outsourcing usually wins on both cost and coverage.
Every NEMT owner eventually hits the same wall: the operation has outgrown one person answering the phone, and none of the obvious fixes are obviously right. This is a comparison of the four real options rather than a recommendation dressed as one.
Option 1: software
Dispatch software organizes trips, optimizes routes, handles billing exports and gives drivers an app. It is genuinely useful and most fleets past twenty trips a day should have some.
What it does not do is answer the phone, call a facility back, chase a will-call, or decide what to do when a driver breaks down at 4:50pm. Software makes a dispatcher faster; it does not replace one, and buying it expecting otherwise is the most common disappointment in this category.
Pricing starts around $125 a month for small fleets and rises with vehicles and features. Treat it as infrastructure rather than as a solution to a staffing problem. There is a fuller comparison in software versus outsourced dispatching.
Option 2: an in-house dispatcher
One good dispatcher who knows your drivers, your riders and your facilities is hard to beat on quality. The problem is never quality. It is coverage.
One person covers roughly 40 hours of a 168-hour week. Covering the rest means an on-call rota, a second hire, or the owner carrying the phone. Covering 24/7 properly needs about 4.5 full-time staff for one seated position once leave, sickness and weekends are accounted for.
And a single dispatcher is a single point of failure. When they resign, the institutional knowledge leaves with them, and the handover is usually two weeks of somebody writing notes nobody reads.
Want NEMT-trained agents answering in your company name?Free operations audit — a written plan within 1 business day.
Get My Free AuditOption 3: a generic answering service
Cheap, fast to start, and a poor fit for transport. A general answering service takes a message and passes it on. That is fine for a plumber and close to useless for a fleet.
A will-call rider who is ready does not need a message taken. They need a vehicle assigned. By the time the message reaches your dispatcher, the useful window has passed and the rider has waited in a lobby for forty minutes.
If the service cannot see your schedule and cannot assign, it is a receptionist, not a dispatch solution.
Option 4: an outsourced dispatch desk
This is a staffed desk working inside your systems, doing the dispatching rather than routing calls to somebody who will.
For a fleet at 50 trips a day, the documented comparison is roughly $15,000-25,000 a month in-house against $4,000-9,000 outsourced, which is where the commonly quoted 30-50% reduction in total dispatch cost comes from.
The structural difference matters more than the saving. Outsourced dispatch is a variable cost that scales with trips; a salaried dispatcher does not shrink in a slow month and does not stretch in a busy one.
Which fits at what volume
| Trips per day | Usually the right answer | Why |
|---|---|---|
| Under 20 | Owner or office staff plus software | Volume does not justify a dedicated seat |
| 20-50 | Outsourced desk, or one dispatcher plus outsourced nights | Coverage breaks before cost does |
| 50-150 | Outsourced desk, or in-house day plus outsourced nights | Cost gap is largest here |
| 150+ | In-house team plus outsourced overflow and overnight | Scale justifies the fixed cost, nights still do not |
The question that decides it
Not "what does it cost". Ask what happens on a Tuesday in February when your dispatcher calls in sick and two drivers are late.
If the honest answer is that the owner drops everything and works the board, the constraint is coverage rather than cost, and the options that fix coverage are the shortlist. Everything else is a preference between them.
What to check before signing anything
- Does the provider work inside your existing software, or do they want you to migrate?
- Is the desk staffed or on-call? Staffed means answered; on-call means returned.
- Who writes the escalation rules? It should be you.
- What happens at handover each morning — a written summary, or voicemails?
- Can they show answer times and escalation accuracy from accounts like yours?
Frequently asked questions
Below roughly 50 trips a day, outsourcing usually wins on both economics and coverage. Above that it becomes a mix, with an in-house day team and outsourced nights and overflow. The break tends to come from coverage rather than cost.
They should. Any provider asking you to migrate systems as a condition of dispatching is adding a risky project to a risky handover. We work in whatever you already run.
For messages, yes. For dispatch, no. A will-call rider who is ready needs a vehicle assigned, not a message passed on, and a service that cannot see your schedule cannot do that.
From around $125 a month for small fleets, rising with vehicles and features. Budget it as infrastructure. It makes a dispatcher faster and does not replace one.
Typically a week or two. Most of that is documenting your rules — vehicle types, coverage areas, escalation thresholds, who may be called and when — rather than technical setup.
That is the most common starting point and the easiest to justify, because it is exactly the shift where in-house staffing economics stop working.
Keep reading: software vs outsourced dispatching, what outsourced dispatching costs, and our NEMT dispatch service.
