Help

Find quick answers about dispatch workflows, drivers, the mobile app, account settings, and billing.

• Search 20 questions across five practical categories.
• Expand only the answers you need on one easy-to-scan page.
• Jump directly to related routes, drivers, and settings pages.

Use the FAQ search when you know the problem but are not sure which part of the platform controls it.

Use the dashboard as the operational snapshot for the selected service date.

• Review total routes and total deliveries for the selected date.
• Check active drivers and which drivers are assigned or unassigned.
• Track remaining stop allowance for the current billing period.

Use the service date picker to review past or future operations without changing live routes.

Use Stops as the staging area before addresses become part of a route.

• Import CSV or XLSX stop files with address, delivery window, and recipient columns.
• Filter stops by depot, route, driver, date range, status, or search text.
• Select multiple stops to add them to a route or delete them in bulk.

Set the depot and service date before importing so new stops are linked correctly.

Use Routes to create, optimize, monitor, and review delivery paths.

• Use the summary cards to review route counts, active work, and completed work.
• Create a route by selecting stops, drivers, depot, service date, and start time.
• Filter by route name, status, depot, service date, or archived state.

Routes default to the current service date. Change the date filter to plan ahead or audit completed runs.

Use Drivers to manage the mobile delivery fleet from onboarding through performance review.

• Review total drivers, active drivers, and assigned versus available capacity.
• Inspect each driver's last-seen status, vehicle details, license plate, and depot.
• Invite new drivers by email and resend pending invitations when needed.

The last 7 days success percentage is the fastest signal for driver follow-up.

Administrators and dispatchers can send private messages to drivers and review automatic route scheduling and update alerts.

• Search for drivers, select up to 500 eligible recipients, and write a message of up to 2,000 characters. Inactive drivers cannot be selected.
• Each selected driver receives a private copy. Drivers cannot see other recipients, and replies are not available yet.
• Choose a driver under Conversation history to review sent messages, route changes, read status, and notification attempts. Load older messages when needed.

Read means the driver opened the message in the app. Push accepted means the notification service accepted it; it does not confirm that the device displayed it or the driver read it.

Use Analytics to turn route and stop history into operational reporting.

• Review success rate, average completion time, and total attempted stop volume.
• Compare work route mileage against delivery route mileage.
• Switch between depot and driver views for location-level or person-level analysis.

Use the driver view with a 30-day range for performance reviews or mileage-based pay checks.

Use Settings to configure the account, team access, routing defaults, tracking, depots, and proof of delivery.

• Profile controls organization identity and customer-facing contact details.
• Team controls dashboard access, roles, depot restrictions, and ownership transfer.
• Preferences controls time format, distance unit, currency, and localization defaults.

Use Profile to manage the organization details shown across the platform and customer communications.

• Upload the company logo used in tracking links and exports.
• Set the company name shown in dashboard, driver, and recipient experiences.
• Maintain phone and email contacts used for support, billing, and notifications.

Use Team to control who can access the dashboard and what they are allowed to manage.

• Owners have unrestricted access and can transfer ownership.
• Administrators can manage the platform except for ownership transfer.
• Drivers use the mobile app and can be restricted to their delivery role.

Ownership transfer requires at least one other active administrator.

Use Preferences to set localization defaults for time, distance, and currency displays.

• Time format affects ETA and timestamp displays in the dashboard and driver app.
• Distance unit affects route mileage calculations and analytics exports.
• Currency is used for payment-eligible route calculations and billing references.

Use Routes & Stops to tune how the route optimization engine assigns and orders work.

• Choose whether selected drivers are used or the system uses as few drivers as needed.
• Balance equal workload, similar completion times, or maximum route efficiency.
• Control whether routes can begin before their configured start time.

Use workload balancing when fairness matters; use maximum efficiency when total route time matters most.

Use Tracking to manage recipient SMS notifications and message usage.

• Monitor SMS credit balance, sent messages, delivered messages, failed messages, and segments used.
• Buy SMS credit bundles when balance is low.
• Set an optional SMS label or brand tag for outbound messages.

Use the Available variables panel beside the SMS editor to insert a variable without retyping it.

Use Depots to manage the physical hubs that routes, stops, and drivers are assigned to.

• Review active depots and their full dispatch addresses.
• Add a new depot to support another operating location.
• Edit depot details when a hub address changes.

Removing a depot can unlink associated drivers and stops.

Use Proof of Delivery to configure what drivers must capture when closing a stop.

• Use the master POD toggle to enable or disable proof requirements.
• Set delivery scenarios such as recipient handover, third-party handover, mailbox, pickup point, safe place, or other.
• Make scenarios optional or mandatory depending on operational policy.

Mandatory POD scenarios require drivers to complete the requirement or mark the stop as failed.

Add these variables to any SMS preset. Values are filled from the organization and delivery stop when a message is created.