For Brokers & MCOs

Route before you assign.

DriveBoss is building the routing brain brokers can't build internally — real intelligence at the moment of assignment, not just "nearest TP" throughput matching. Which TP has real capacity right now. Which driver has a chaining gap. Which assignment minimizes dead miles and hits SLA across your whole network.

Dispatch operations workstations with trip monitoring dashboards

Networks we serve and integrate with

ModivCare Alivi Access2Care MTM
ATMS-Integrated (API)
American Logistics SAFERIDE
Manual Upload (batch)
Private Trips
TP-Entered (direct)

We label broker integrations by what is actually automated. Direct / API (ATMS-integrated) means trips, status, and submission flow over a real-time broker API — currently ModivCare, MTM, Access2Care, and Alivi. Manual upload / batch means file-upload ingestion where the broker does not expose a real-time API — including American Logistics and SAFERIDE. TP-entered / direct covers private-pay and other operator-entered trips that don’t flow through a broker at all.

1,460,000+ trips coordinated
12,623,000+ miles driven
$32,948,000+ in billing processed
10+ years inside NEMT

How we know it works

The engine is already running — inside every DriveBoss-powered TP.

DriveBossIQ Scheduler runs real constraint-aware routing inside every TP's fleet today. It protects standing orders. Adapts pickup and drop-off logic to facility type (dialysis ≠ school ≠ methadone ≠ home). Places wheelchair, stretcher, and tight-window trips before easy ambulatory rides absorb the capacity. Runs a Tabu Search refinement pass to recover unassigned trips.

We're extending that same engine up one level — into the broker-to-TP assignment decision itself. Same routing math, bigger scope: instead of optimizing one fleet, it optimizes the network.

What brokers get:

  • Trips land where they'll actually execute well — not where the first TP clicked "accept"
  • Standing orders and recurring commitments respected at the network level, not rediscovered per TP
  • Most-constrained trips (wheelchair, stretcher, tight windows) placed first so specialty capacity isn't wasted on easy rides
  • Facility-aware rules carry through from broker intake to driver pickup — no lossy handoffs

Internal product name for the broker-side engine: DriveBossIQ Router. Currently in development — partnering with select Medicaid transportation brokers as design partners.

Partnership

Talk to us about becoming a DriveBossIQ broker partner.

We're looking for design partners in Medicaid transportation brokerage. Technical review meetings are 30 minutes: we walk you through the routing architecture, your current pain points, and what a pilot integration looks like.

Schedule Technical Review Download API Overview (PDF)

See DriveBoss in your dispatch — book a demo.

30 minutes. Walk through your broker mix, current pain points, and what DriveBoss would look like on your fleet.

Book a Demo