Dispatcher tools, exception management, KPI tracking, customer ETAs — at flat-rate pricing.
An 11–50 vehicle fleet has crossed a structural threshold: the dispatcher is now full-time, the driver pool is large enough to need exception management mid-day, and customer-facing ETAs are now an SLA, not a courtesy. SortDrops Team handles up to 20 drivers at $29.99/month flat; for fleets between 21 and 50 vehicles, we set up custom plans with the same flat-rate philosophy and the same browser-based driver workflow.
At 11–50 vehicles, three things change. First, the dispatcher is now full-time and KPI-accountable — they're tracking on-time rate, stops-per-driver-hour, fuel-per-stop, failure rate. Second, exception management is systematic rather than improvised: vehicle breakdowns, driver call-outs, and customer cancellations happen daily, and the dispatcher needs a tool that surfaces deviations from plan automatically. Third, customer-facing ETAs are now part of the contract — a 2-hour delivery window quoted to a B2B customer is enforceable.
SortDrops at this scale does the heavy lifting on optimization (k-means split, per-driver TSP, real road distances) and surfaces the right dispatcher signals: live driver tracking with ETA calculation, per-driver utilization view, exception flags when a driver is running >20 minutes behind plan, and end-of-day KPI rollup.
Multi-depot routing is the structural upgrade at this scale. Most 20+ vehicle fleets run from 2–4 depots — a main warehouse plus regional satellites. SortDrops Team supports multi-depot dispatch where each driver is assigned a home depot and the optimizer respects depot-to-stop and stop-to-depot legs as part of the total route cost.
A typical 25-driver fleet day across two depots: dispatcher arrives 07:00, exports the day's order roster (300–600 stops), uploads to SortDrops dispatch mode with depot assignments, and sets driver-by-driver counts (e.g., 12 from depot A, 13 from depot B). SortDrops runs depot-aware k-means clustering and TSP optimization across the full fleet. The batch takes 90–180 seconds for 500 stops across 25 drivers.
Dispatcher reviews the proposed splits on the colour-coded map, identifies any stops that should belong to a different depot (clustering is depot-naive on the boundary, occasionally), and re-assigns via drag-and-drop. Once satisfied, drivers go live at 08:00 — each driver receives their personal route-link via WhatsApp.
Mid-morning exception: at 10:30, driver 7 reports vehicle trouble. Dispatcher sees the live-track screen showing driver 7 stationary for 12 minutes (alert threshold). Driver 7 confirms breakdown via the driver-link comment. Dispatcher pulls driver 7's remaining 14 stops and redistributes across nearby drivers using drag-and-drop. SortDrops re-optimizes each affected driver's queue, the route-links update within 5 seconds, and the customer-facing ETAs adjust automatically.
End of day KPI rollup: dispatch session report shows on-time rate (target 95%, achieved 92%), avg stops-per-driver-hour (target 4.0, achieved 3.7), failure rate (target sub-8%, achieved 5%), total kilometres (saved 18% vs naive ordering). Dispatcher reviews the misses, identifies any pattern (e.g., one specific zone consistently under-performs), and adjusts tomorrow's plan.
Multi-depot routing is the most-requested feature at the 20+ vehicle scale. Each driver is assigned a home depot. The optimizer treats depot-to-first-stop and last-stop-to-depot as legitimate route legs (not free transfers). For fleets running 3+ depots, SortDrops minimizes cross-depot driver assignment to avoid drivers ending up far from home base.
KPI tracking on Team produces a per-shift report covering on-time rate, stops-per-driver-hour, failure rate, total kilometres versus naive baseline, and per-driver breakdown. The report is exportable as CSV/PDF for management review. We don't yet offer a dashboard with multi-shift trend charts — that's on the 2026 roadmap — but the per-shift CSV imports cleanly into Power BI / Tableau / Excel.
Customer-facing ETAs are derived from the live driver track: as a driver moves through their route, ETAs to upcoming stops update automatically. SortDrops Team supports broadcasting ETA updates to customers via SMS or email (configurable per stop). The ETA is updated when the upstream stop completes, so the broadcast is accurate within ±5 minutes for 90%+ of stops.
Yes — though above 20 drivers we set up a custom plan. The underlying optimizer scales well past 50 drivers; the gating factor is plan structure, not technical capability. Contact us for a fleet >20 vehicles and we'll size a custom Team plan with the same flat-rate philosophy.
Live driver track shows position updates every 30 seconds. If a driver is stationary >12 minutes mid-route, the dispatcher screen flags it. Combined with driver-side comment-on-stop, this catches breakdowns, missing parking, and customer-side delays within the same shift.
Yes on Team. SMS and email ETA broadcasts can be configured per-stop or globally. SMS uses your own carrier integration (we provide a simple webhook); email goes via standard SMTP. Pricing for the SMS volume is your carrier cost — we don't markup the messaging.
Yes. The dispatch session report covers on-time rate, stops-per-driver-hour, failure rate, total kilometres saved, and per-driver breakdown. Export as CSV/PDF. Multi-shift trend dashboards are on our 2026 roadmap; in the meantime the CSV imports cleanly into Power BI / Tableau / Excel.