Dispatcher and driver communication in NEMT: calls, chat, and updates that stick

Call or message: one rule for the whole office

Message by default and call when the driver has to act within minutes. That single rule settles most of the back-and-forth between dispatch and the road.

A message is better for anything that can wait until the driver’s next stop. It leaves a record tied to the trip, any dispatcher can see it, and the driver can read it safely when parked. A call is better when a message might sit unread while the problem gets worse: a rider waiting at the curb right now, a road closure ahead, or a safety issue.

The no-show row is written into broker manuals. CareOregon’s provider manual bars a driver from pulling away from a no-show pickup until dispatch has been told, and the provider then reports each no-show to the brokerage. MTM’s Virginia handbook expects the driver to try phoning or texting the member before departing. Both only work if the driver can reach dispatch quickly and dispatch answers. For the full late-pickup routine, see the running-late playbook, and for breakdowns, the van breakdown plan.

One channel for every trip change

Pick one place where trip changes live and send every change there. When changes arrive by personal text, a hallway conversation, and a phone call, drivers miss the one that mattered and nobody can prove what was said.

A single channel does four things:

• It keeps the record. When a broker asks why a pickup was late, the message thread shows when dispatch knew and what the driver was told.
• It survives shift changes. The evening dispatcher can read what the morning dispatcher promised. Conversations on one person’s phone disappear when that person goes home.
• It sits next to the schedule. A change sent inside the same app that holds the driver’s trips is read in context. A change sent by personal text has to be matched to a trip by memory.
• It keeps the company in control. When a driver leaves, the history stays and access ends.

Brokers set a floor for the equipment. Georgia’s NEMT manual (July 1, 2026) calls for two-way communication between every vehicle and the provider’s main place of business, rules out pagers, and takes any vehicle with a dead system off the road until the system is repaired or replaced. Under the MTM provider agreement posted by Pennsylvania, each driver must use two-way voice communication that connects every vehicle to the provider’s place of business. Modivcare’s Mississippi manual accepts cell phones or two-way radios. MTM’s Virginia handbook says drivers need a working phone or other device during service hours, so they can reach dispatch and MTM in real time about delays, no-shows, safety concerns, and trip problems.

Phones meet those rules for most companies, but the phone is only the device. The channel is the discipline of putting every change in one place.

What a good trip-change message contains

Write every change so the driver can act on it after one read:

1. Which trip. Rider first name and pickup time, or the trip number, never just “your 2 o’clock”.
2. What changed. “Pickup moved to 2:45” or “Return is ready now at the main entrance”.
3. What to do. “Go there after your current drop-off” or “Skip the 3:10, reassigned”.
4. A reply request. “Reply OK when you see this.”

One change per message. Two changes in one message get half-read. Spell out times with AM or PM, and avoid private shorthand a new dispatcher or driver would not know.

Read receipts and confirmations

A read receipt tells you a message was opened. It does not tell you the driver understood it or can do it. Use receipts to decide when to follow up, and use confirmations to know the change landed.

A workable routine:

• Routine updates: a read receipt is enough.
• Changes to a pickup, a drop-off, or the order of stops: ask for a reply. If there is no reply within a few minutes, call.
• Unread after the driver’s next stop: call. The driver may be in a building helping a rider, in a dead zone, or driving with the phone out of reach, which is where it should be.
• Rules every driver must follow: send an announcement that each driver confirms, and keep the list of who confirmed. It is the proof a broker auditor or insurer asks for after an incident.

Dispatchers should also tell riders about changes they did not ask for. When a pickup time moves and the member has not heard about it, MTM’s Rhode Island handbook says to call the member. The rider notifications guide covers that side of the conversation.

Response times and escalation

Write down how fast each side answers and who steps in when nobody does. An example policy: dispatch answers a driver’s message within five minutes during service hours, a driver who hears nothing in that time calls, and an unanswered call goes to the on-duty supervisor. Drivers answer trip changes at their next safe stop. Post the supervisor’s number in every van, because a driver often needs it when dispatch is busiest.

Status taps instead of check-in calls

Most “where are you” calls stop once drivers log every arrival, pickup, and drop-off with a tap and dispatch follows along on the board. Those taps also build the trip record brokers want: MTM’s Virginia handbook requires vehicle location technology to stay on from the driver’s arrival through the drop-off. Save calls for the exceptions, such as a rider who is not there, a delay that will break a later pickup, or a problem in the van.

Voice notes, hands-free rules, and the phone in the mount

Drivers should read and write messages only when stopped in a safe place, and dispatch should not expect replies from a moving van. Federal rules, state laws, and broker manuals all point the same way, and the strictest rule you work under decides your policy.

Federal rules for commercial vehicles

FMCSA bans texting while driving (49 CFR 392.80) and using a hand-held mobile phone while driving (49 CFR 392.82) in commercial motor vehicles. For a passenger carrier crossing state lines, that covers a vehicle built or used to carry nine or more people for pay, counting the driver, and any vehicle with a weight rating of 10,001 pounds or more. Two details matter for dispatch:

• The ban reaches the company. Both rules also say no motor carrier shall allow or require its drivers to do it, and FMCSA’s definition of motor carrier includes employees responsible for dispatching drivers. A dispatcher who expects instant text replies from a driver on the road is on the wrong side of the rule.
• Some actions are allowed. Using a navigation system does not count as texting, and neither does a one-button tap to answer or hang up a call. A vehicle pulled off the road and stopped where it can safely stay is not being driven.

Many NEMT vans fall under both thresholds or never leave the state, so these rules often do not apply directly. They still describe a sensible standard.

State hands-free laws

State law covers every driver, whatever the vehicle. Georgia’s hands-free law is a clear example. Drivers may not hold or support a phone with any part of the body, and may not write, send, or read text-based messages, even with a hands-free device. Voice-based messages that the phone converts to text are allowed, as is navigation. The first conviction costs up to $50 and one point on the license. Repeat convictions inside a 24-month window climb to $100 with two points, then $150 with three.

Broker rules are often stricter

Voice notes are useful because a driver can listen and answer without typing. Treat them as a stopped-vehicle tool unless your state and all of your brokers allow hands-free use, and even then keep the phone mounted and out of the driver’s hands. The federal rules treat a driver waiting at a red light as still driving, and Georgia’s law makes an exception only for a lawfully parked vehicle.

Write the policy down, cover it in training, and keep each driver’s signed copy. The driver training guide covers where it fits in onboarding.

Privacy on the dispatch channel

Send drivers what they need to run the trip and nothing more. HIPAA’s minimum necessary standard asks covered entities and business associates to make reasonable efforts to limit protected health information to what the purpose requires (45 CFR 164.502(b)), and the safeguards rule requires reasonable steps against incidental disclosures (45 CFR 164.530(c)).

In practice that means:

• Trip facts, not medical facts. Name, pickup, drop-off, mobility needs, and entrance notes. A diagnosis rarely changes how the driver does the job, and when it does, describe the need (“needs help with the step”) rather than the condition.
• Mind who can hear. CareOregon’s manual asks drivers to keep member details out of earshot of other people on calls and radio, to keep paperwork and screens with member information out of view, and to share appointment or diagnosis details only with the member’s care team. MTM’s Rhode Island handbook says member information must not be visible to other passengers. A dispatcher reading a rider’s details over a speakerphone with another rider aboard breaks both.
• Keep it off lock screens. A notification that shows a rider’s name and clinic on a phone lying on the dashboard is an incidental disclosure waiting to happen.
• Control the devices. The Security Rule’s device and media controls call for policies on hardware that holds electronic health information (45 CFR 164.310(d)). Require screen locks, and end access the day a driver or dispatcher leaves.
• Check who is calling. CareOregon’s manual asks dispatchers to confirm a caller’s identity before sharing member or trip details, and to limit those details to the member, a caregiver or representative, or the member’s health care provider.
• Route rider contact. Under MTM’s Rhode Island handbook, a driver may contact a member only as far as the assigned trip requires. Calls from a company line or through dispatch keep drivers’ personal numbers private and keep rider contact within the rules.

New York adds a notice rule for monitoring. An employer there that watches employees’ calls, email, or internet activity must, under Civil Rights Law section 52-c, hand out a written notice at hiring, get a signed or electronic acknowledgment from each person monitored, and post a copy where those workers can easily see it. If you review drivers’ messages there, make that notice part of onboarding. The HIPAA texting guide goes deeper on messaging rules.

Built-in messaging in HealthRide

HealthRide includes team chat between dispatch and drivers, with read receipts, voice notes, and announcements that each driver can be required to confirm. Every conversation stays with the company rather than on personal phones, push notifications never show passenger details, and dispatchers can message a driver straight from the board or the live map. See team chat for how it works.