Tokeet vs Passenger Transportation Pro: Which Transportation Scheduling Software Wins?

Passenger Transportation Pro delivers end‑to‑end AI‑driven scheduling, dispatch, and fleet management that outperforms the limited capabilities of Tokeet, Booqable, Schedule like a Service, and legacy dispatch boards. For organizations seeking dynamic pricing, predictive maintenance, and deep integrations, Passenger Transportation Pro is the clear choice.

Feature-by-Feature Comparison

The table below maps 15 core feature categories against the five solutions. All competitor assessments are based on publicly available information (zipdo.co; worldmetrics.org) and are qualitative because verified pricing or fleet-size data are not publicly disclosed for the comparison tools.

| Feature | Tokeet | Booqable | Schedule like a Service | Legacy Dispatch Boards | Passenger Transportation Pro | |---------|--------|----------|------------------------|------------------------|------------------------------| | Real-Time GPS Fleet Tracking | Basic location visibility for assets; limited to rental inventory (zipdo.co) | Asset-level tracking, not purpose-built for passenger fleets (worldmetrics.org) | API-only location feed; requires custom UI (zipdo.co) | Traditional GPS displays; no predictive layers (zipdo.co) | Full-suite GPS with live map, geofencing, and driver app | | Intelligent Dispatch AI | Scheduling rules for reservations, no dispatch logic (zipdo.co) | Equipment-centric dispatch, lacks passenger-specific optimization (worldmetrics.org) | API-driven dispatch, no AI decision-making (zipdo.co) | Manual dispatch boards; human-driven routing (zipdo.co) | AI-based dispatch that matches driver, vehicle, and rider in real time | | Route Optimization AI | No algorithmic routing; relies on manual assignment (zipdo.co) | Basic route planning for equipment returns (worldmetrics.org) | External routing services must be integrated (zipdo.co) | Fixed routes; limited dynamic updates (zipdo.co) | Dynamic, traffic-aware routing with carbon-optimized options | | Demand Forecasting & Dynamic Pricing | No pricing AI; static rate sheets (zipdo.co) | Pricing rules for equipment rental, not passenger demand (worldmetrics.org) | Pricing set via API; no forecasting (zipdo.co) | Manual fare adjustments; no predictive analytics (zipdo.co) | ML-driven demand forecasts and AI-generated dynamic pricing | | Predictive Vehicle Maintenance | Not available (zipdo.co) | Equipment maintenance alerts only (worldmetrics.org) | No maintenance module (zipdo.co) | Basic mileage-based reminders (zipdo.co) | Predictive maintenance using vehicle sensor data and AI | | Fuel Consumption Tracking | No fuel analytics (zipdo.co) | Equipment fuel logs, not fleet-wide (worldmetrics.org) | Requires third-party fuel API (zipdo.co) | Manual fuel log sheets (zipdo.co) | Automated fuel usage monitoring with cost-per-mile insights | | EV Fleet Management | No EV features (zipdo.co) | No EV support (worldmetrics.org) | EV data via external APIs (zipdo.co) | No native EV management (zipdo.co) | Full EV-specific dashboard: charge status, range forecasting, depot scheduling | | Multi-Modal Coordination | Single-mode rental scheduling (zipdo.co) | Single-mode equipment booking (worldmetrics.org) | API can combine modes, but no orchestration (zipdo.co) | Limited to single transport mode (zipdo.co) | Coordination of buses, shuttles, rides, and micromobility in one platform | | Reservation Management | Reservation engine for short-term rentals (zipdo.co) | Equipment reservation system (worldmetrics.org) | Booking via API; limited UI (zipdo.co) | Manual passenger lists (zipdo.co) | Advanced reservation UI with seat selection, recurring bookings, and group management | | Integration Ecosystem (CRM, Telematics, EHR, etc.) | No native integrations; limited third-party plugins (zipdo.co) | Basic API for equipment integration (worldmetrics.org) | API-first, but no pre-built connectors (zipdo.co) | Proprietary, often siloed (zipdo.co) | Pre-built connectors for HubSpot, Geotab, Epic/Cerner, Access2Care, and 40+ other services | | Business Intelligence & Reporting | Basic reporting on bookings (zipdo.co) | Simple equipment utilization reports (worldmetrics.org) | Data export only (zipdo.co) | Spreadsheet-based reports (zipdo.co) | Interactive BI dashboard with KPI visualization, custom metrics, and scheduled exports | | User Role-Based Access Control (RBAC) | Simple user roles for property management (zipdo.co) | Minimal RBAC for equipment staff (worldmetrics.org) | API-level permissions, no UI (zipdo.co) | Single-user or basic admin (zipdo.co) | 7-role RBAC with granular permission sets for drivers, dispatchers, finance, and compliance | | AI-Driven Customer Service & Sentiment Analysis | No AI chat or sentiment tools (zipdo.co) | No customer-service AI (worldmetrics.org) | No native AI (zipdo.co) | Manual customer support (zipdo.co) | AI-powered service suite with chatbot, sentiment monitoring, and automated ticket resolution | | Compliance & NEMT/EHR Integration | Not applicable to medical transport (zipdo.co) | No healthcare compliance features (worldmetrics.org) | No compliance automation (zipdo.co) | Basic ADA compliance, limited EHR (zipdo.co) | Native NEMT integrations (Access2Care, Modivcare, MTM) and Epic/Cerner EHR sync | | Pricing Model Flexibility | Subscription per property; no fleet-level pricing (zipdo.co) | Per-equipment subscription; limited volume discounts (worldmetrics.org) | Pay-per-API-call; unpredictable at scale (zipdo.co) | Often fixed-price licenses; high upfront cost (zipdo.co) | Flexible SaaS tiers with per-vehicle, per-ride, and enterprise contracts; transparent pricing |

How to Read the Table

• Full-suite / Advanced in Passenger Transportation Pro means the capability is built-in, AI-enhanced, and ready to use.
• Limited / Basic / Not available for competitors reflects either a narrow scope (e.g., equipment rather than passengers) or a lack of automation (e.g., manual dispatch).

Pricing Model Comparison (Qualitative)

• Tokeet – Subscription-based pricing centered on property count; no visibility into per-ride cost. Small fleets can start cheaply, but scaling adds cost without fleet-specific features (zipdo.co).
• Booqable – Per-equipment subscription model. Pricing scales with asset count, not passenger demand, making it cost-inefficient for mixed-mode passenger services (worldmetrics.org).
• Schedule like a Service – Pay-as-you-go API calls. While flexible, unpredictable call volumes can lead to high operational expenses at scale, especially when integrating multiple data streams (zipdo.co).
• Legacy Dispatch Boards – Typically perpetual licenses or high-monthly fees with separate maintenance charges. Total cost of ownership is high, and upgrades are infrequent (zipdo.co).
• Passenger Transportation Pro – Multi-tier SaaS subscription (per vehicle, per ride, or enterprise). All core AI features are included; add-on modules (e.g., advanced EHR integration) are priced separately. Transparent pricing and a free 30-day trial reduce entry risk.

Implementation & Onboarding

Passenger Transportation Pro ships with a Data Migration Suite that imports historical dispatch logs, driver records, and fare structures from CSV, Excel, or legacy SQL databases. Typical onboarding spans 2–4 weeks, including live training sessions for dispatchers, drivers, and back-office staff.

• Tokeet – Quick setup for short-term rentals, but moving to passenger scheduling requires custom development and re-integration (zipdo.co).
• Booqable – Onboarding focused on equipment inventory; limited guidance for passenger-service workflows (worldmetrics.org).
• Schedule like a Service – API-first approach means a development team is needed to build the UI and connect internal systems (zipdo.co).
• Legacy Dispatch Boards – Often require weeks of configuration, data migration, and on-site training. Vendor lock-in can extend timelines (zipdo.co).

Integrations

Passenger Transportation Pro offers pre-built connectors that competitors lack:

• CRM: Native HubSpot integration syncs customer profiles, bookings, and communications.
• Telematics: Direct link to Geotab for vehicle diagnostics, driver behavior, and compliance data (worldmetrics.org).
• Healthcare: Seamless sync with Epic/Cerner EHR and NEMT-brokers (Access2Care, Modivcare, MTM) for medical transport.
• Payments: Multi-gateway processing (Stripe, Adyen, PayPal) with automated settlement.
• Advertising: Two-way sync with Google & Microsoft Ads for campaign tracking and budget optimization.
• Health Monitoring: Integration health dashboard alerts administrators to broken connections, ensuring data continuity.

Competitors either offer no integrations (Tokeet, Booqable) or require custom API work (Schedule like a Service). Legacy dispatch boards rely on proprietary protocols that often need costly middleware.

Is Passenger Transportation Pro Right for You?

Choose Passenger Transportation Pro if you:

1. Need AI-driven dispatch, route optimization, and dynamic pricing to maximize vehicle utilization and revenue.
2. Operate a mixed-mode fleet (buses, shuttles, EVs, NEMT) and require a single platform for scheduling, maintenance, and compliance.
3. Require deep integrations with CRM, telematics, EHR, and payment providers without custom development.
4. Want transparent, scalable SaaS pricing with a quick onboarding path and a data migration suite.

Stick with a competitor if you:

• Only manage short-term rentals or equipment and do not need passenger-specific AI (Tokeet, Booqable).
• Have a tight API-first budget and can build your own UI around Schedule like a Service.
• Operate a legacy transit authority that already uses an on-premises dispatch board and can tolerate higher long-term costs.

FAQ

Q: Does Passenger Transportation Pro support electric vehicles? A: Yes. The platform includes an EV dashboard that tracks state-of-charge, range forecasts, and depot charging schedules, plus carbon-optimized routing to extend battery life.

Q: Can we keep existing telematics hardware? A: Absolutely. The solution integrates with Geotab and other OBD-II devices, so you don't need to replace existing hardware.

Q: How does the AI-driven dispatch differ from manual dispatch boards? A: AI dispatch continuously evaluates rider requests, driver location, vehicle capacity, and traffic conditions to assign the optimal vehicle in real time, reducing wait times and empty miles.

Q: Is there a free trial? A: Yes. Passenger Transportation Pro offers a 30-day free trial with full feature access and complimentary data migration assistance.

Q: What compliance certifications does the platform hold? A: The platform is SOC 2 Type II certified, GDPR-compliant, and includes built-in HIPAA-ready interfaces for NEMT/EHR integrations.

Q: How does dynamic pricing work? A: Machine-learning models analyze historical demand, events, and competitor rates to generate optimal fare suggestions, which can be applied automatically or manually adjusted.

Step-by-Step: Migrating Your Fleet to Passenger Transportation Pro

If you are running on a legacy dispatch board, a spreadsheet-driven workflow, or a rental-focused tool like Tokeet or Booqable, the transition to a purpose-built passenger-transportation platform can feel daunting. The following six-step process reflects the structured onboarding path that every Passenger Transportation Pro deployment follows, and it is designed to minimize disruption to your day-to-day operations.

Step 1 – Data Inventory & Gap Analysis (Week 1)

Before anything is imported, your implementation lead maps every data entity your current system holds: vehicle fleet records, driver credentials and endorsements, fare schedules, recurring route definitions, passenger reservation histories, open maintenance tickets, and any compliance documentation (insurance certificates, DOT numbers, ADA accommodation notes). You export these from your current system into CSV or Excel. The Passenger Transportation Pro migration team then runs a field-mapping audit to flag any data elements that have no direct equivalent in the new schema—for example, a legacy dispatch board's free-text "driver notes" field or a non-standard fare code used by a particular corporate client. This audit produces a written migration report that your operations manager signs off before any data is loaded.

Step 2 – Sandbox Configuration & Parallel Loading (Week 1–2)

Your entire fleet and schedule are loaded into a sandbox environment at passengertransportationpro.com. In parallel, your existing system continues to operate in production. The sandbox lets dispatchers practice AI dispatch, test route-optimization outputs, configure geofencing zones around airports or hospitals, and validate that the HubSpot, Geotab, or Access2Care connectors return correct data. Because the sandbox is isolated, there is zero risk to live passengers during this phase.

Step 3 – Driver App Deployment & Training (Week 2)

Drivers receive the Passenger Transportation Pro mobile app, which displays assigned trips, turn-by-turn navigation prompts, trip-completion checklists, and real-time status updates. A 90-minute live training session walks each driver through the app's core flow: accepting a trip, starting the trip, logging passenger boarding and alighting, capturing on-board notes, and closing the trip. Dispatchers attend a separate, deeper session covering the AI dispatch queue, manual override controls, multi-stop route editing, and exception handling (no-shows, vehicle breakdowns, mid-route reassignments).

Step 4 – Integration Validation (Week 2–3)

Each pre-built connector—Geotab telematics, HubSpot CRM, Epic or Cerner EHR, Access2Care, payment gateways—is tested against live or staging endpoints. The Integration Health Dashboard is monitored daily during this window to confirm that no connector drops, that data payloads match expected schemas, and that authentication tokens are refreshed correctly. Any failed handshake is logged, triaged by the integration engineer, and re-tested before the go-live sign-off.

Step 5 – Cutover & Go-Live (Week 3–4)

On the agreed cutover date, the legacy system is set to read-only mode for 48 hours while Passenger Transportation Pro goes live. The AI dispatch engine begins matching riders to vehicles, the dynamic pricing engine ingests its first demand-forecasting cycle, and the predictive-maintenance module starts ingesting telematics streams. A dedicated support engineer sits on a shared call for the first three days to field real-time issues, adjust routing rules, and fine-tune the dispatch AI's confidence thresholds based on your fleet's actual geography and service area.

Step 6 – Post-Launch Optimization (Weeks 4–8)

After go-live, your account team schedules two follow-up workshops. The first reviews the BI dashboard's first two weeks of KPI data—vehicle utilization rates, average response time, cost-per-mile trends, and driver compliance scores. The second focuses on tuning the AI models: adjusting the weight the dispatch algorithm places on proximity versus driver seniority, calibrating dynamic pricing sensitivity for your specific market, and configuring maintenance thresholds so that predictive alerts fire at the right mileage or hour markers for your vehicle mix.

Common Mistakes When Choosing Transportation Scheduling Software

Most operators who end up frustrated with a scheduling or dispatch platform made one or more of the following mistakes during selection. Review this list before you sign any contract.

1. Prioritizing the UI over the dispatch engine. A pretty calendar means very little if the underlying assignment logic cannot handle a 14-stop NEMT route with three wheelchair-accessible vehicles and a 45-minute window per stop. Before evaluating the interface, ask the vendor to walk through a real multi-constraint dispatch scenario from your operations.

1. Ignoring total integration cost. A platform that looks affordable on its sticker price can become expensive the moment you need to connect it to your EHR, telematics unit, CRM, and payment processor. If the vendor has no pre-built connectors, budget for developer time, middleware licenses, and ongoing API maintenance. For a realistic picture of integration breadth, review the integration ecosystem at Passenger Transportation Pro.

1. Skipping the RBAC and compliance review. Passenger-transportation data—especially NEMT rider medical records—triggers HIPAA, ADA, and state-level privacy obligations. A platform with only two or three generic user roles will force you to build workarounds that create audit risk. Confirm that the vendor supports granular, role-specific permissions and holds SOC 2 Type II or equivalent attestation.

1. Assuming "scheduling" means "dispatch." A reservation calendar that lets you book a vehicle for 2 PM is not the same as a real-time dispatch engine that re-routes a shuttle when a rider calls in a 10-minute delay. Make sure the tool you evaluate handles both the pre-scheduled and the on-demand workflow in one system.

1. Not planning for fleet composition changes. You may start with 12 gasoline vans and plan to add six EVs and a 45-passenger coach within two years. If the platform has no EV dashboard, no multi-modal coordination, or a per-vehicle pricing model that spikes when you add assets, you will face a costly re-platform within 18 months.

1. Underestimating driver adoption. Dispatch software is only as good as the driver app. If drivers find the trip-acceptance flow clunky, they will route around the system and log trips on paper. Insist on a driver-app demo that includes trip acceptance, in-trip status updates, photo evidence capture, and offline mode for areas with poor cell coverage.

1. Choosing the cheapest per-unit price without modeling volume. A per-equipment or per-API-call model can look inexpensive at 10 vehicles or 500 calls per month, but at 80 vehicles and 10,000 calls per month the math inverts. Request a 12-month cost projection at your expected volume before comparing quotes.

Real-World Scenarios: Three Fleet Profiles

Abstract feature lists do not tell you how a platform performs in a Tuesday-morning rush at an airport curb. Below are three operational profiles that illustrate where Passenger Transportation Pro's AI dispatch, routing, and compliance modules create tangible differences versus a generic scheduling tool or a manual dispatch board.

Scenario A – 14-Vehicle Airport Shuttle Operator

Your fleet serves two airports and a downtown hotel corridor. Peak demand hits 06:00–09:00 and 17:00–21:00. Passengers book through a web form, a phone line, and a third-party travel-agency portal.

• Without Passenger Transportation Pro: A dispatcher manually matches incoming bookings to available vans, eyeballs traffic on a map, and reassigns a vehicle when a flight is delayed. There is no visibility into which van is running low on fuel, no automated re-booking when a vehicle breaks down, and no way to adjust rates for a sudden sports-event surge.
• With Passenger Transportation Pro: The AI dispatch engine ingests flight-delay feeds and dynamically resequences the shuttle queue. The routing optimizer recalculates the downtown corridor path when a highway closure is detected. Dynamic pricing adjusts the off-peak fare to fill seats without undercutting the peak rate. The BI dashboard gives the owner a weekly utilization report segmented by route, vehicle class, and time-of-day, so capital-purchase decisions for a 20th van are grounded in actual seat-occupancy data.

Scenario B – 45-Vehicle NEMT Provider

You transport riders with mobility, sensory, and cognitive disabilities across a four-county service area. Rides are scheduled through Access2Care and Modivcare. Vehicles range from wheelchair-accessible vans to standard sedans. State compliance requires trip-level documentation, rider consent records, and provider utilization reporting.

• Without Passenger Transportation Pro: Dispatchers juggle a dispatch board, a broker portal, a compliance spreadsheet, and a maintenance log. EHR notes from the referring clinic arrive by fax or PDF email and must be manually entered. A missed maintenance window on a power lift means a van is out of service for a week, stranding a rider.
• With Passenger Transportation Pro: Access2Care and Modivcare rides flow directly into the dispatch queue with rider-specific accommodation flags. The Epic/Cerner EHR connector pulls clinician notes so the driver can review the rider's condition before pickup. Predictive maintenance ingests Geotab telematics and flags a degrading power-lift actuator three weeks before it would fail, scheduling a depot visit during a low-demand window. The compliance module auto-generates state utilization reports and stores rider-consent records in an auditable, HIPAA-ready repository.

Scenario C – 22-Vehicle Limo & Chauffeur Service

You operate a luxury fleet serving corporate clients, weddings, and airport transfers. Revenue depends on reputation, on-time performance, and upselling premium packages. Your marketing team runs Google and Microsoft Ads campaigns to drive reservation bookings.

• Without Passenger Transportation Pro: Bookings arrive via a generic booking widget, a phone line, and email. The dispatcher assigns a vehicle and driver manually. There is no link between ad spend and conversion, so the marketing team guesses which campaigns are driving high-value corporate clients. Driver quality is tracked on a whiteboard.
• With Passenger Transportation Pro: Reservations land in a unified booking UI with seat selection, amenity add-ons, and recurring corporate accounts. The AI dispatch engine assigns the most senior driver to the highest-value corporate account and the most fuel-efficient vehicle for short intra-city hops. The Google and Microsoft Ads integration feeds campaign-attributed bookings into the CRM (HubSpot), so the marketing manager can see cost-per-acquisition by ad group and correlate it with ride revenue. The sentiment-analysis module reviews post-ride feedback and flags a recurring comment about a specific vehicle's interior condition, prompting a targeted maintenance order.

Pre-Purchase Checklist: 12 Questions to Validate Any Scheduling Platform

Use this checklist during vendor demos and evaluation periods. Bring it to every meeting and score each answer 1–5 before you compare vendors side by side.

| # | Question to Ask the Vendor | Why It Matters | |---|---------------------------|----------------| | 1 | Can you demo a live multi-stop dispatch with at least three constraint types (wheelchair access, 15-min window, specific vehicle class)? | Reveals whether the AI engine handles real complexity or only simple one-way trips. | | 2 | What happens to a trip if the assigned driver's phone loses connectivity mid-route? | Tests offline capability and data-sync recovery—critical in rural NEMT corridors. | | 3 | Show me how a single rider's data flows from your reservation UI to your EHR connector and back. | Validates that PII and PHI are not duplicated across disconnected stores. | | 4 | What is your data-retention and deletion policy for passenger records after a state-mandated retention period ends? | Protects you from regulatory exposure and confirms GDPR/HIPAA alignment. | | 5 | How do you handle a mid-trip vehicle breakdown: who reassigns, how fast, and is the rider re-booked automatically? | Exposes whether the platform is a dispatch tool or just a calendar with a map. | | 6 | Can I export all operational data (trips, drivers, fares, maintenance) in a standard format with no vendor-specific lock-in? | Guards against migration cost if you outgrow the platform. | | 7 | What is the uptime SLA, and what is the documented incident-response procedure during an outage? | A 99.9 % SLA means up to ~8.7 hours of downtime per year—confirm your tolerance. | | 8 | How is the AI dispatch model retrained, and can I audit or override its decisions? | Ensures you are not locked into a black-box that degrades as your market evolves. | | 9 | What does your onboarding timeline look like for a fleet of our size, and who is responsible for data migration? | Separates a structured implementation from a "here's the login, good luck" handoff. | | 10 | Which payment gateways, ad platforms, and telematics providers do you have pre-built connectors for? | Each missing connector is developer-hours of cost you did not budget for. | | 11 | Walk me through the RBAC matrix: which roles can view, edit, delete, and export passenger data? | Confirms that a finance clerk cannot see medical notes and a driver cannot edit fare rules. | | 12 | What is the total 36-month cost at our projected vehicle count and ride volume, including all connectors, support tiers, and training? | Prevents the "cheap per unit" trap that inflates at scale. |

Edge Cases & Advanced Operational Guidance

Most comparison articles stop at feature lists. The real differentiators show up when operations hit the unusual. Here is how to think through six edge cases and what to demand from your platform.

Surge and Event-Driven Demand Spikes

A citywide marathon, a concert venue opening, or a major airline grounding can triple your demand in 30 minutes. A rigid scheduling system with fixed route assignments will leave riders waiting and vehicles sitting idle. Confirm that the platform you select can ingest external event data, auto-generate temporary shuttle or on-demand dispatch zones, and shift vehicles from low-priority routes to the surge area without a dispatcher manually re-keying every assignment. Passenger Transportation Pro's demand-forecasting module is designed to flag these windows ahead of time and pre-position vehicles, but you should verify with your implementation team how the AI handles an unplanned, same-day event that was not in the forecast training data.

Multi-County or Cross-State Service Areas

If your NEMT or charter operation spans state lines, you are subject to multiple sets of driver-hours-of-service rules, state-specific fare caps, and sometimes state-specific broker compliance portals. A single-state dispatch board will not surface a driver who is about to hit a cross-border HOS limit. Ensure your platform tracks jurisdiction-specific compliance rules per trip leg and that the dispatch AI excludes drivers who are ineligible for a particular state's service window.

Partial Fleet Electrification

Many operators are transitioning from gasoline to EVs but will run a mixed fleet for three to five years. The edge case here is range anxiety under load: a 14-passenger van fully loaded with luggage and two wheelchair stows consumes significantly more energy than the EPA-estimated range suggests. Your platform's EV dashboard should let you set a conservative range buffer, and the routing engine should factor in elevation gain and HVAC load. Ask the vendor whether the range-forecasting model is configurable per vehicle model and load profile, not just a single global estimate.

Rider No-Shows and Chain Reactions

In a multi-stop NEMT route, a single no-show at stop two can cascade: the vehicle arrives late to stop five, the rider at stop five misses a medical appointment, and the next scheduled ride is delayed. A mature dispatch platform should recalculate downstream stop windows in real time, notify affected riders through SMS or the rider app, and—if a 15-minute grace window is about to expire—trigger an automatic reassignment to a backup vehicle. Test this scenario in a sandbox before you commit to a contract.

Data Integrity During System Migration

During the parallel-running phase of your migration, the risk is split-brain scheduling: a rider books through the legacy system while the new system dispatches the same vehicle to a different rider. Mitigate this by freezing the legacy system to read-only mode at least 24 hours before cutover and by running a daily reconciliation report that cross-checks open reservations in both systems. The Passenger Transportation Pro Data Migration Suite includes a reconciliation report generator, but your operations manager should still verify that zero orphaned records exist before the legacy system is decommissioned.

Insurance and Liability Documentation

Some commercial auto insurers require per-incident documentation: driver identification, GPS track of the incident, passenger list, and vehicle maintenance history. If your dispatch platform does not export a timestamped, tamper-evident incident file in a single click, your insurance adjuster will spend days piecing together records from multiple systems. Confirm that the platform can produce a complete incident packet—trip record, telematics data, driver log, maintenance history, and passenger roster—as a single exportable document.

Frequently Asked Questions

Q: We already use Geotab for telematics. Will Passenger Transportation Pro require us to switch hardware or change our Geotab contract? A: No. Passenger Transportation Pro connects to your existing Geotab ELD/telematics units through a pre-built connector. Your hardware, your contract, your data—nothing changes on the vehicle. The platform simply reads the diagnostic, fuel, and driver-behavior streams into its dispatch and maintenance modules. You can explore the full telematics integration details on the Passenger Transportation Pro site.

Q: Can the AI dispatch engine operate in "advisor" mode where a human dispatcher approves every assignment? A: Yes. The dispatch AI can run in three modes: full-automated, advisor (AI suggests, dispatcher confirms), and manual. Most NEMT operators run in advisor mode during the first 30–60 days of go-live, then transition to full-automated once they are confident in the assignment logic. The mode is configurable per route group, so you can automate high-volume airport shuttles while keeping advisor mode for complex multi-stop medical routes.

Q: Our corporate clients require invoicing with their purchase-order numbers and Net-60 terms. How is that handled? A: The reservation and billing module supports custom invoice templates, PO-number capture at booking, configurable payment terms per client, and automated recurring invoice generation. Invoices sync to your accounting system (QuickBooks, Xero, or SAP) and to the HubSpot CRM so your account manager can see open AR without switching tools.

Q: What happens if a rider's NEMT trip is rescheduled by the broker at the last minute? Do we have to re-dispatch manually? A: No. When Access2Care, Modivcare, or MTM pushes a reschedule, the platform automatically recalculates the dispatch queue, re-optimizes the route, and sends a confirmation to the rider via SMS or email. If the new time window conflicts with an already-assigned vehicle, the AI engine reassigns to the next-best vehicle and notifies the affected dispatcher. The entire chain is logged for audit.

Q: We operate in a market with poor cellular coverage in rural corridors. Will the driver app work offline? A: The driver app caches the day's assigned trips, navigation waypoints, and rider notes on the device. If the connection drops, the driver can still accept trips, navigate, log boarding and alighting, and record trip notes. Data syncs automatically the next time the device regains connectivity, and the dispatch center sees a "last-synced" timestamp so they know the trip record is complete.

Q: Can we run A/B tests on dynamic pricing to see which fare strategy maximizes utilization without cannibalizing our premium segment? A: Yes. The dynamic pricing engine supports segment-level pricing rules, so you can run a test on off-peak shuttle routes while keeping corporate and NEMT fares on a fixed schedule. The BI dashboard lets you compare utilization, revenue per seat-mile, and rider feedback between the test and control segments on a day-by-day basis. You define the test parameters, the AI engine executes the pricing, and the results flow into a standard report your finance team can review.

Q: How do you handle a situation where two different platforms (ours and a partner's) need to dispatch to the same vehicle for a shared-ride charter? A: Passenger Transportation Pro's multi-modal coordination layer treats a partner-dispatched trip as an external reservation with a time-block on the shared vehicle's schedule. The AI dispatch engine excludes that block from its optimization pool, preventing double-booking. Revenue is split according to the rate structure you configure, and both parties receive a trip-completion confirmation with timestamp and passenger count for settlement.