Skip to content

NEMT Dispatch Planner · Healthcare & NEMT

Tomorrow's NEMT run sheets, drafted for your dispatcher to approve

Reads your trip sheet and driver roster each afternoon, matches trips to the right vehicle and shift, orders stops around appointments and flags what won't fit.

Available now $149 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Runs on a schedule
  • 1 AI step
  • A person approves before it acts
  • About 30 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Building tomorrow's run sheets takes our dispatcher the whole afternoon.”
  • “We find out a wheelchair trip has no WAV available the morning of.”
  • “Drivers get schedules in five different formats and text us for clarification.”

What you get with the agent

  • Each trip matched to an available driver whose vehicle fits the rider: ambulatory, wheelchair (WAV) or stretcher, within shift hours and capacity
  • Drivers marked Off or On hold in the roster skipped automatically
  • Stops ordered so riders arrive before appointments with your buffer, nearby trips grouped and will-call returns listed separately
  • Every trip it couldn't place listed with the reason, plus tight timings flagged
  • Dispatcher review and edits, then approved run sheets posted to your drivers' Slack channel and emailed to your dispatch list

Before

The dispatcher sorts tomorrow's trips by hand, checks which vans are wheelchair-accessible and discovers at 6pm that two dialysis trips can't be covered.

After

By mid-afternoon there's a draft plan with the uncovered trips already listed. The dispatcher adjusts, approves, and drivers get one clear run sheet.

How it works

The whole workflow, step by step.

Every afternoon the agent reads your trip-request sheet and your driver roster in Google Sheets, and AI plans the next service day: it matches each trip to an available driver (drivers marked Off or On hold in the roster get no trips) whose vehicle fits the rider (ambulatory, wheelchair/WAV or stretcher), within shift hours and capacity, orders each driver's stops so riders arrive before their appointments, groups nearby trips and lists every trip it couldn't place with the reason. A dispatcher reviews and edits the plan; once approved, the run sheets are posted to your drivers' Slack channel and emailed to your dispatch list. Travel times are estimates from your sheet or the addresses: there is no live GPS, traffic or broker-portal connection.

  1. TriggerEvery afternoon at 3 pm
  2. App callRead the trip sheet
  3. App callRead the driver roster
  4. LogicPick tomorrow's trips
  5. AI stepBuild tomorrow's run sheets
  6. Human approvalDispatcher approves the run sheets
    • Approved:Post run sheets to drivers in Slack
    • Approved:Email run sheets to your dispatch list
    • Rejected:Dispatched by hand
  7. App callPost run sheets to drivers in Slack
  8. OutputEmail run sheets to your dispatch list
  9. OutputDispatched by hand

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1Every afternoon at 3 pmRuns each afternoon to plan the next service day. Change the time and time zone on the trigger.
  2. Step 2Read the trip sheetReads every row of your trip-request sheet in Google Sheets (one row per trip leg, with a header row).
  3. Step 3Read the driver rosterReads your driver roster tab: each driver's vehicle and type, seats, shift, base, certifications and status (e.g. Off or On hold), so the plan uses who is really available.
  4. Step 4Pick tomorrow's tripsIn code, not AI: keeps only the trip rows dated tomorrow in the trigger's time zone (America/New_York unless you change it). Rows for other days, or with a date the check can't read, are left out. Change the day here (within.min / within.max: 1 = tomorrow).
  5. Step 5Build tomorrow's run sheetsAI matches each of tomorrow's trips (picked in code) to an available driver whose vehicle fits, orders each driver's stops around appointment times and lists anything it couldn't assign.
  6. Step 6Dispatcher approves the run sheetsA dispatcher checks the plan in Reviews, fixes any assignment or time (edit manifest_text), then approves it to send to drivers, or rejects it to dispatch by hand.
  7. Step 7Post run sheets to drivers in SlackPosts the approved run sheets to your drivers' Slack channel.
  8. Step 8Email run sheets to your dispatch listEmails the same run sheets to your drivers' or dispatch distribution address, with replies going to your dispatch office.
  9. Step 9Dispatched by handRejected plans stay in the run history only; nothing is sent.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

A fictional trip: wheelchair rider, Dayton pickup, dialysis appointment at 9:30, will-call return. Roster shows one WAV van on shift 6:00–14:30.

The agent produces

Trip assigned to the WAV van with pickup timed to arrive before 9:30 with your buffer, return listed as will-call. Two other trips needing a stretcher vehicle are listed as unplaced. Waiting for dispatcher approval.

What you need

Everything it takes to run it.

About 30 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $149 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Google Sheets and Slack, connected in Settings → Integrations.
  • A Google Sheet of trip requests (you can paste or export broker-portal trips into it) and a driver roster tab kept current.

Setup, about 30 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Google Sheets. Connect the Google account that can open your trip sheet (Settings → Integrations → Google Sheets).
  3. Connect Slack. Connect the Slack workspace your drivers use (Settings → Integrations → Slack).
  4. Pick your trip sheet. Open “Read the trip sheet”, pick your Google account, paste the spreadsheet link and pick the tab. Keep one row per trip leg with a header row.
  5. Pick your driver roster. Open “Read the driver roster”, pick your Google account, paste the spreadsheet link and pick the tab with one row per driver (vehicle, type, seats, shift, certifications, status). Keep Status current: drivers marked Off or On hold get no trips.
  6. Write your dispatch rules. Open “Build tomorrow's run sheets” and replace the placeholder with your time zone, arrival buffer and shared-ride rules.
  7. Pick the drivers' Slack channel. Open “Post run sheets to drivers in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
  8. Add your dispatch email addresses. Open “Email run sheets to your dispatch list” and enter the list that gets the run sheets and the dispatch address replies go to.
  9. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  10. Switch the trigger on. Open the trigger, check the time and time zone, and switch the schedule on. Assign the review step to your dispatcher.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • NEMT providers running broker and private-pay trips
  • Dispatchers at small and mid-sized transportation fleets
  • Paratransit and medical transport operators

What it doesn't do

  • It has no live GPS, traffic or routing engine: travel times are estimates from your sheet or the addresses, and a dispatcher checks them.
  • It doesn't connect to broker portals (ModivCare, MTM and others); trips come from your Google Sheet.
  • It doesn't re-dispatch during the day or track drivers in real time.
  • It doesn't text riders or drivers by SMS (Twilio is waiting for approval); run sheets go out by Slack and email.
  • Nothing reaches drivers until a dispatcher approves the plan.

We list the limits up front so you can decide before you buy.

Price

$149 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about NEMT Dispatch Planner.

Does it use live GPS or traffic?

No. Travel times are estimates from your sheet or the addresses, and a dispatcher checks every plan before drivers see it. It doesn't re-dispatch during the day or track drivers.

Can it pull trips from our broker portal?

Not directly. Export or copy broker trips into the Google Sheet and it plans from there. Many portals export CSV.

What about rider privacy?

It works only with what's in your sheet and sends run sheets to the Slack channel and email list you choose. Check that your AI provider agreement covers the data you include, and keep rider details to what drivers need.

What's the setup and is it worth it?

About 30 minutes with Google Sheets and Slack. It's a one-time purchase that never renews, turning hours of manual run-sheet building into a review. Live runs need a paid plan and your own AI key; Dry Run uses simulated rows.

Which trips does it plan?

The rows whose trip date is tomorrow, picked in code in the trigger's time zone (dates like 2026-10-14, 10/14/2026 or October 14, 2026 work). Because it runs every afternoon, Monday's trips are planned on Sunday afternoon. Rows with a date it can't read are left out and listed in the run history.

How do I take a driver off tomorrow's plan?

Set their Status in the roster tab to Off or On hold (or edit their shift). The roster is read fresh on every run, so the next plan leaves them out.

Can it pull trips from my broker portal?

Not directly. Export or copy broker trips into the Google Sheet (many portals export CSV), and the agent plans from there.

Is this a subscription?

No. NEMT Dispatch Planner is a one-time purchase of $149 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put NEMT Dispatch Planner to work.

Free account, no credit card. Your Agents page opens with NEMT Dispatch Planner ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works