Answers for planners, dispatch, drivers & partners

HelloRoute is a last-mile operations platform: plan delivery days on a map, optimize routes with time windows and constraints, run dispatch (board, timeslots, drivers), equip drivers with mobile workflows, share recipient tracking links, and review performance in the dashboard and Insights.

Most teams start with Planner and dispatch workflows, then enable drivers and tracking. Calendar depends on how clean your address and time-window data is, how many routes you run, and whether you use spreadsheet import or API — we usually stage a pilot week on a subset of depots or days before full cutover.

Yes. Planners can upload delivery tasks from spreadsheet files in the product (same logical columns as your planners already validate). For automated feeds, use the JSON push API with your OMS or ERP — see Integrations for payloads and authentication.

Yes. Partner systems can push delivery tasks, cancel or delete stops, reschedule windows, and export raw rows for KPIs using a shared API key. Public tracking endpoints let you build custom recipient experiences with the tracking token. Start from the Integrations page and then use the single setup guide for technical endpoints.

Current integration routes include Shopify, WooCommerce, Zapier, Google Sheets, CSV-based pipelines, API push, and webhook events. These are managed from one integrations surface so operations can start quickly without jumping across many docs pages.

Yes. We provide customized integrations for apps not listed on the page, including internal systems and region-specific tools. Teams usually start with the standard integration routes, then extend into custom connectors as needed.

Drivers work from ordered routes, clear stop statuses, and familiar phone-friendly screens. Teams that already navigate with Maps-style apps typically need a short session on status updates (arrive, deliver, fail) and scanning or messaging flows — not a multi-day program.

No multitenant roulette. Each engagement we carry is delivered on a dedicated environment with its own maintained codebase line and release train. Your traffic, storage, and telemetry stay logically cordoned from everyone else’s fleets — so confidentiality reviews and compliance questionnaires get crisp answers instead of “trust us, partitions exist.”

Yes — that is precisely why we carry separate repositories per client relationship. Material differences in SLAs, integrations, UI language, or geography can ship on your schedule rather than waiting for a pooled roadmap vote. We collaborate on what belongs in product core versus what should stay bespoke so you still inherit platform upgrades without forking into oblivion.

Isolation tightens blast radius: breaches, noisy neighbors, or sloppy experiments from unrelated brands do not traverse into your dataset. Auditors and insurers like legible boundaries — when your contract points at a dedicated footprint, the story is shorter than explaining complex row-level controls on a giant shared cluster.

You pick a delivery date from the Planner calendar and work on that day's universe of stops — on the map and in panels for assigned vs unassigned work. Filters help slice by cities, delivery areas, and timeslots so you focus on what you need to clear next.

Yes. You can assign tasks to routes, reorder stops, and move work between routes when reality changes. The product surfaces when a route may need reoptimization after manual edits so ETAs stay trustworthy.

Yes. Stops carry service windows and geographic context (cities, recipient areas) so optimization and dispatch respect the same rules operations already negotiates with customers.

You can enforce maximum route duration so shifts stay realistic. When a route would exceed allowed hours, the workflow guides you through trimming or splitting so drivers are not handed impossible plans.

Yes. Route history helps with audits, customer disputes, and understanding what actually ran on a given day — without digging through scattered exports.

HelloRoute uses VROOM for route sequencing with road distances and times from OSRM, so plans respect delivery windows, capacity, and your fleet settings. You can optimize many unassigned stops in bulk or reoptimize a single route after edits.

Yes. Large optimization jobs can run asynchronously with status tracking so planners can keep working while the solver finishes. If something interrupts, recovery paths help you resume without losing context.

Timing can incorporate traffic multipliers, congestion zones, and speed profiles so plans and ETAs reflect busier periods — not just free-flow drive times. Live views and recalculation help when the day diverges from the morning plan.

You can reoptimize or smart-optimize affected routes when new stops appear, cancellations land, or windows shift. In-progress routes may trigger smart reoptimization so remaining work stays coherent without forcing a full rebalance every time.

Dispatch (sometimes called Last Mile Pulse) is the operations hub: a dispatch board for what is moving now, a timeslots view for slot-level health, a drivers view for who is active, and a priority list for when the board is crowded — built for admin and customer service roles.

Yes. Dispatch supports pickup scanning (QR, Code 128, and other barcodes) so you can confirm boxes or AWBs as they leave the hub — tightening accountability before drivers roll.

The timeslots view aggregates how each customer-facing window is performing so you can spot overloaded slots, late clusters, or uneven driver load before phones start ringing.

When many stops need attention, the priority list surfaces the highest-impact work so coordinators know what to tackle first — and you can export it when leadership wants a spreadsheet snapshot.

Drivers sign in through the same HelloRoute frontend with layouts tuned for phones: a routes hub, an active route with ordered stops, a dispatch-style inbox, and stop detail flows for POD, messaging, and status progression.

Planners and dispatch coordinate assignments in the admin experience; drivers then see assigned work in their hub. Roles prevent drivers from seeing planner-only tooling.

Stops progress through operational states such as queued, picked up, in transit, arrived, delivered, failed, skipped, cancelled, returned — aligning dispatch boards, ETAs, and customer messaging. Exact labels follow your configured workflows.

The platform records location updates for live maps and ETA explanations while routes are active — subject to your policies and driver consent. Live tracking pages help operations see progress without calling every driver.

Flows exist to open WhatsApp (or equivalent) compose from a stop with auditing for compliance-conscious teams — alongside template management for centrally approved wording.

You generate tracking links tied to stops. Recipients open a lightweight page that shows route context, ETA when available, and status — without creating an account. Tokens expire for privacy; inactive links return predictable HTTP errors for integrators.

Public survey endpoints let you attach feedback collection to the tracking journey when surveys are enabled for your tenant — helpful for QA and SLA reporting.

A single snapshot of delivery mix, ETA performance, active routes, unassigned workload, and distance or duration rollups for the window you select — so stand-ups start with shared facts.

Insights provides filterable drill-down charts (drivers, slots, efficiency, ETA accuracy — including original vs revised ETAs where applicable) and export paths when you need to push numbers into spreadsheets or BI tools.

A dedicated heat-style congestion view planners use to sanity-check plans against real-world slowdowns — aligning route decisions with geography, not just stop counts.

Common roles include admin (full operations), customer service (dispatch workspace and supportive tools), and driver (field experience). Exact permissions follow your deployment configuration.

Administrators manage user accounts from Settings so new planners, CS agents, or drivers receive the right experience on first login — without shipping custom builds.

Yes. Shifts and driver-related settings live in product settings so operations can tune hours and policies as the network grows.

Templates are maintained inside HelloRoute so legal and marketing approve wording once, operations triggers messages with confidence, and you avoid scattering copy in spreadsheets.

Yes. Teams can search and maintain customer records for repeat delivery programs and quicker resolution when CS researches an order.

Async optimization and caching mean planners are not blocked on every click. Mobile flows are designed around intermittent connectivity typical in vans. For enterprise expectations, pair this product posture with your own SLO review during procurement.

Your stops, routes, proof photos, and exports remain your data. Use standard export and API paths for backups and BI; detailed terms appear in your agreement and privacy materials.

The public anchor is from AED 2,000 per month (up to 2,000 monthly stops) for a dedicated HelloRoute deployment. We do not charge per user, per driver, or per optimization run inside your agreed volume envelope — users, drivers, stops, and optimizations are unlimited at that operational scale. Your monthly subscription scales primarily with confirmed monthly delivery volume (see the estimator on the Pricing page) and only with materially deeper customization if you need it. We do not charge setup fees or bill integrations as separate projects — those are folded into onboarding and your agreed subscription. Final numbers are confirmed in writing after discovery.

No. Commercial packaging is built around operational scale (your monthly delivery volume band) and your dedicated environment, not per-seat SaaS math. That keeps planner, dispatch, and leadership access economical as your team grows.

No. Standard onboarding — discovery, environment setup, import alignment, training, and agreed integration work — is included at no separate setup charge. If you need unusual bespoke development beyond a typical rollout, we discuss that transparently and may reflect it in your subscription tier, not as an integration invoice.

We do not publish separate integration project fees. CSV/XLSX flows and agreed API or system connections are scoped during onboarding as part of the relationship. Pricing stays centered on your monthly operational subscription and volume band.

Route operations teams usually pair in-app escalation paths with designated success contacts agreed in onboarding. Severity and response commitments are spelled out contractually for larger deployments.

Marketing includes a changelog for notable releases; authenticated users benefit from tighter release notes supplied during rollout when features touch planner or driver workflows.

Yes — open Book a demo to pick a day (calendar), time window, and your details for a live walkthrough. You can also use Contact us for a shorter message. We cover Planner, Dispatch, Drivers, Insights, and API scenarios with sample data resembling your geography and SLA.