The Trip You Haven't Booked Yet
Why the messiest part of NEMT dispatch deserves its own feature.
Ask any NEMT dispatcher about their worst moment with software, and you'll hear some version of the same story. They're halfway through booking a trip. The phone rings. Now they're losing their place, making the new caller wait, or scribbling details on a sticky note they'll probably lose by the end of the shift.
It's a small moment. It also happens a dozen times a day, and it's exactly the kind of thing most dispatch software pretends doesn't exist.
Real dispatch isn't a straight line
Most software is built around a tidy path. A rider inquires, you book the trip, you collect payment, you dispatch. Clean. Linear. Done.
Anyone who has actually run a NEMT phone line knows it never works that way. Riders call to shop prices before they commit to anyone. Calls interrupt other calls. Half the trip details show up long before a rider is ready to pay. The job is messy, and the tools rarely match the mess.
That gap is the whole reason Duet built Reservations. It's one of the platform's most-used features, and it exists to hold the part of the job that doesn't fit into a clean booking flow.
Scenario one: the price shopper
A rider calls and gives you everything. Name, pickup, drop-off, mobility type, appointment time. But they're calling three other providers too, so they're not booking yet. They're shopping.
Without somewhere to put that information, you're stuck. You write it on a sticky note. You try to remember it. Or you lose it, and when the rider calls back ready to commit, you're starting from scratch and looking slower than the competitor who already had their details ready.
With Duet, you save it as a Reservation. Every detail is captured and held, with no trip committed and no payment taken. When the rider calls back, everything is already there. You confirm, collect payment, and turn it into a real booking in seconds. You look organized because you are.
Scenario two: the mid-booking interruption
You're halfway through building a trip when the phone rings again. It's a different rider who needs a ride. In a lot of systems, you either abandon your progress or make the second caller wait while you finish the first.
With Duet, you don't have to choose. You open a new Reservation, handle the second call, then come right back to the booking you left. Nothing gets dropped, and nobody gets put on hold while you scramble.
So what is a Reservation, really?
Think of it as an incomplete booking. It's a place to hold all the details of a trip before payment and confirmation, so the information lives in your system instead of on a notepad or in someone's memory.
Reservations can't be dispatched on their own. That's the point. They sit in their own space until a rider is ready, and then they convert into a booking with one step. Duet automatically clears out reservations older than 30 days, so the list stays current instead of turning into clutter.
Why most software gets this wrong
Tools that only understand confirmed trips force dispatchers to work around them. The sticky notes, the second monitor with a half-finished form, the rider who has to repeat everything because the first call went nowhere in the system. None of that shows up in a demo, but all of it shows up in a real shift.
Good software should match how the work actually gets done. Booking management isn't just about the trips you've confirmed. It's about the ones still in motion, and the ability to pick any of them back up without losing a beat. That's the difference between a tool you fight and a tool your team can't work without.
See it in action
Reservations is built specifically for NEMT, and it's one of the features Duet customers point to most when they talk about why the platform fits their day. If you want to see how it handles your real booking flow, the fastest way is to watch it work.