Fortell can support the conversations around community transportation—from service questions and ride requests to changes and cancellations—so dispatchers can focus on the decisions that keep the service moving.
Your team needs to distinguish the appointment time from the requested pickup time. They may need a return journey, a mobility accommodation, an accompanying person, or a trip that crosses a service boundary. Meanwhile, the phone keeps ringing with cancellations and questions about existing bookings.
Collecting the right information is essential. So is knowing when a request needs a dispatcher—and being clear with the rider about whether the trip is requested or confirmed.
Program workflow
Access
A rider should not need to install an app to ask how to book. Voice access can help people begin a request in a familiar way, while text can provide a useful confirmation or reminder where appropriate. The operator still controls service availability, scheduling, and vehicle allocation.
Questions to discuss
Fortell supports the conversation and information collection around the service. Scheduling, vehicle availability, and operational decisions remain with your existing systems and team.
Integration depends on the platform, available access, and the intended workflow. Confirm the specific read and write capabilities during scoping.
Only when an approved live-data connection supports that answer. Otherwise route the question to dispatch without inventing an arrival time.
Implementation
These are proposed measures for implementation—not existing Fortell results.
Sources reviewed September 20, 2026. Historical statistics are identified by their original data or publication dates.
Walk us through routine questions, booking requests, changes, and the points where dispatch judgment is essential.
Request a demo