Medical ride call center: 75% better call handling, 98% scheduling accuracy

The problem

Ride call centers repeat the same requests all day: Where is my ride? Can I book? Can I cancel? Most riders still call. A chatbot that cannot change the actual schedule does not help when someone is waiting for pickup.

Adding more agents was the only way to keep up. Different operators also used different dispatch tools, so a one-off phone script would not travel from one client to the next.

• Staff spent hours on ride status, booking, and cancellation calls
• The live schedule lived in a dispatch system (TripMaster) that the phone team could not update quickly
• A wrong time or a missed cancel could mean a missed medical appointment
• The phone line was not connected to the dispatch system staff already trusted
• Only a person could book, cancel, or change a trip
• Leaders could not see how often calls led to a correct schedule

What we changed

We built a phone helper that talks with the rider, then updates the dispatch system they already run. The schedule engine stayed. People stayed in the loop for anything that should not go out alone.

• Natural phone conversations for ride questions and booking
• Book, cancel, check arrival time, and send reminders without a second login
• Connects to TripMaster and other dispatch tools operators already use
• Checks before a change is saved, with a fallback if the system is down

What changed in the numbers

What this means for you

• A phone helper only works if it can change the real schedule, not just answer questions
• Plan for more than one dispatch vendor if your operators are not all on the same tool
• Track scheduling accuracy and handle time. Model scores do not tell you if Tuesday got easier
• Handing a call to a person is part of the design, not a failure