Better routes for your Onfleet deliveries.

OnDeckD reads your unassigned Onfleet tasks, splits them across the drivers on shift, orders each route around delivery windows and writes the assignments back to Onfleet. Drivers get a short text when their route is ready. Your customer notifications stay in Onfleet, untouched.

Request access How it works
The route planner, shown with sample data.

How it works

OnDeckD sits next to Onfleet. Your team keeps dispatching and tracking in Onfleet. OnDeckD only handles the planning.

  1. 01

    Connect Onfleet

    Paste an Onfleet API key. OnDeckD pulls in your teams, drivers and today's unassigned tasks, including addresses, time windows and pickup and dropoff pairs.

  2. 02

    Plan

    Pick who's driving and when they start. OnDeckD groups nearby stops, keeps pickups ahead of their dropoffs, fits stops inside their windows and evens out the workload between drivers.

  3. 03

    Send to Onfleet

    Review the plan, drag stops between routes if you want, then send it. Each task is assigned to its driver in Onfleet in the planned order.

  4. 04

    Drivers get a text

    Drivers who opted in get one text when their route is ready, and another if a stop is added or moved during the day.

What it handles

Delivery windows
Stops with a "complete after" or "complete before" time in Onfleet are scheduled inside that window.
Pickup and dropoff
Linked tasks stay on the same route, with the pickup first.
Shift times
Each driver's start time and location are used, and routes aren't planned past the end of a shift.
Even workload
Stops are spread so one driver isn't finishing at noon while another runs late.
Mid-day changes
New tasks can be added to an active route without re-planning the whole day.
Service time
Set how long a typical stop takes, so arrival estimates are realistic.

What OnDeckD can access in Onfleet

OnDeckD uses your organization's Onfleet API key and only calls the endpoints below. You can revoke the key in Onfleet at any time.

GET/teamsList teams and their hubs
GET/workersDrivers, their schedules and start locations
GET/tasks/allToday's tasks, addresses and time windows
PUT/containers/workers/:idAssign tasks to a driver in route order

OnDeckD never changes recipient details, notification settings or completed tasks, and never contacts your customers.

Driver texts

Route texts are operational messages for drivers and dispatchers. OnDeckD doesn't text your customers and doesn't send marketing.

Who gets themDrivers and dispatchers on teams that use OnDeckD, after they opt in
How they opt inWhen a dispatcher adds a driver's number, the driver gets one invitation text. Route texts start only after they reply YES.
What they sayRoute ready, stop added or moved, route cancelled
How oftenUsually 1 to 5 per shift
CostFree from us. Message and data rates may apply.
StoppingReply STOP any time. Reply HELP for help.

Full SMS Terms

Questions

Do we have to stop using Onfleet's own tools?

No. Dispatch, the driver app, live tracking and customer notifications all stay in Onfleet. OnDeckD plans the routes and hands them back.

Does OnDeckD text our customers?

No. The only texts OnDeckD sends are route texts to drivers and dispatchers who opted in, and account messages to people who asked for them on our contact form. Customer notifications are sent by Onfleet, under your Onfleet settings.

Is OnDeckD made by Onfleet?

No. OnDeckD is an independent product that connects to Onfleet through its public API. Onfleet is a trademark of Onfleet, Inc. OnDeckD is an independent product and is not affiliated with or endorsed by Onfleet.

What happens to our data?

Task and driver data is used to plan routes and is never sold or used for advertising. Our Privacy Policy covers the details.

What does it cost?

Pricing is per driver per month. Request access and we'll send a quote for your team size.

Try it on a day of your own deliveries.

Request access