Dispatcher workflow

This section covers day-to-day work in the web application: accepting orders, building routes, dispatching them to drivers, and tracking delivery through the day.

Section in progress

The pages in this section have not been written yet. We publish only instructions verified against the current interface — describing it from memory would produce steps that are not on the screen.

What will appear here:

• accepting and checking orders, and handling unassigned ones;
• building routes and editing them by hand: reordering stops, moving an order;
• dispatching a route to a driver and following its progress;
• common situations: an order without coordinates, a refused delivery, a schedule that has slipped.

What is available now

Some dispatcher questions are already answered in the integration section, which also documents the order and route statuses you see in the interface:

• Order statuses and history — which statuses exist and the order in which they change.
• Why an order was not placed on a route — the list of reasons: insufficient capacity, delivery window cannot be met, no available vehicles.
• Address formatting — why some addresses fail to geocode and how to correct them.

If the answer is not there, use the portal search or contact support.