Salta al contenuto principale

Dispatching overview

The Dispatching section is the board where you follow the work of Leo, the voice AI agent that calls the carriers in your network to assign your loads. You don't start anything here: dispatch begins from the Loads page, when you run the «DISPATCH» action on a draft. From this page you watch every running session — who was called, who answered, at what price — and you step in with just two levers: updating the offered price or cancelling the session.

Forwarder

Where the section lives

From the left-hand menu of the platform, under the «AI Agents - Leo & Sara» group, click the «Dispatching» item (robot icon). The direct URL of the page is /company/{companyId}/dispatching.

The title at the top is «AI Dispatch», with the subtitle «Monitor dispatch sessions and market feedback» and a small real-time refresh indicator: the board updates itself as Leo works through the calls, with no need to reload the page.

The five tabs

At the top of the board there are five tabs. The first four filter the session table by status; the fifth opens a statistics dashboard.

  • Active — dispatch sessions in progress: Leo is still calling carriers or waiting for the next call in the queue.
  • Completed — sessions that closed with a carrier accepting the load. From that moment the load is «Assigned» and becomes a transport mandate.
  • Cancelled — sessions you interrupted manually before any carrier accepted.
  • Exhausted — sessions where Leo contacted every compatible carrier without anyone accepting. The load still needs handling (see below).
  • Statistics — not a session list, but a dashboard with aggregate numbers for the last 30 days (see below).

The session table

In the Active, Completed, Cancelled and Exhausted tabs you see the «Dispatch sessions» table, one row per session. Every row is clickable and opens the detail drawer.

The columns are:

  • Reference — the code of the load the session refers to, in the LD-XXXXXXXX format (e.g. LD-RLZ3R7B6). It is a sortable column.
  • Stops — the synthetic route origin ▸ destination (e.g. Bologna ▸ Roma).
  • Pickup — the load's planned pickup date.
  • Offered price — the price you proposed for the transport (e.g. 1.500,00 €). It is a sortable column.
  • Status — the session status badge: «In progress», «Completed», «Cancelled», «Exhausted» or «Paused».
  • Contacted — how many carriers Leo has called so far.
  • Responses — how many carriers answered, out of those contacted (e.g. 1 / 2).
  • Feedback — a quick summary of the market response: the range of counter-offers received and the count of contacted carriers.
  • Actions — the last column, with the «Actions» button that opens the quick-actions menu.

When a tab has no sessions, an empty state appears instead of the table: for example, on the Active tab, «No active dispatch sessions — Publish a load to start automatic dispatching».

Actions on a session

The «Actions» button at the end of each row opens a menu with three items:

  1. «Detail» — opens the session detail drawer (the same one that opens by clicking the row).
  2. «UPDATE PRICE» — opens the «Update offered price» dialog. The «New offered price (€)» field is pre-filled with the current price; enter the new value and click «UPDATE PRICE». As the dialog reminds you, «The new price will be used in Leo's next calls».
  3. «CANCEL DISPATCH» — opens the «Cancel dispatch» dialog, with an optional «Reason» field. Confirming with «CANCEL DISPATCH», «The dispatch session will be cancelled. The load will be available again for a new dispatch».

The session detail drawer

Clicking a table row opens, on the right side of the screen, the session detail drawer. At the top you find the load code and the status badge.

The drawer is organised in blocks, from top to bottom:

Summary

The load's summary data — Stops, Pickup date, Offered price, Started on (the session start date) and, when available, the Vehicle type — followed by a row of five counters: Contacted, Responses, Accepted, Rejected and No answer.

Leo savings

The «Leo savings» panel compares, for this session, the cost of a «Manual operator» who would have made the same calls with the cost of «Leo (voice AI)», and shows the resulting «Saving» in euros and phone minutes. The «Calculation method» link points to the public pricing page, where it is explained how these values are estimated.

Market feedback

The «Market feedback» section gathers what the carriers told Leo during the calls: how many carriers answered, whether anyone flagged the price as below market, the average price suggested by the market with its range, the number of counter-offers received and the breakdown of «Rejection reasons» by category (Price too low, Not available, Route not suitable, Timing issue, Vehicle mismatch, Other reason).

Call timeline

The «Call timeline» lists the calls Leo placed, one by one: the call number, the outcome (Accepted, Rejected, No answer, In progress, Pending) and, when available, the rejection reason, any counter-offer and the call duration.

When no carrier is compatible

If no carrier in your network covers the load's route or goods type, an amber notice «No carrier with matching preferences» appears at the top of the drawer: Leo still contacts the available carriers by priority, and the notice offers the «Invite more carriers» shortcut to the Carriers page so you can expand your network.

The actions at the bottom of the drawer

On «In progress» sessions, at the bottom of the drawer you find the same two buttons as the «Actions» menu: «UPDATE PRICE» and «CANCEL DISPATCH». On closed sessions these buttons do not appear.

How a session is born and what Leo does

Understanding the life cycle of a session helps you read the board.

  1. Start. From the Loads page you run the «DISPATCH» action on a load in «Draft». The load moves to the «Dispatching» status and an «In progress» session is born here.
  2. Leo's calls. Leo identifies the compatible carriers in your network, queues them by priority and calls them one at a time, spacing the calls out. With each call it updates the counters and the timeline you see in the drawer.
  3. Positive outcome. As soon as a carrier accepts, the session moves to «Completed», the load becomes «Assigned» and a transport mandate is created. You receive the load-assigned notification.
  1. Counter-offers. If carriers reply with price counter-offers instead of accepting, you find them in «Market feedback» and you receive a dedicated notification.
  1. Exhausted outcome. If Leo contacts every compatible carrier and nobody accepts, the session moves to «Exhausted» and you receive a notification: the load needs to be picked up again — for example by adjusting the price and re-launching the dispatch, or by assigning a carrier manually.

The Statistics tab

The «Statistics» tab doesn't show a session list, but a dashboard with the aggregate dispatch numbers for your company over the last 30 days.

The dashboard is made of three blocks:

  • Leo savings — the overall «Estimated saving» in euros and the «Phone minutes saved» over the period, compared with an operator who would have made the same calls by hand.
  • The four KPI cards — «Success rate» (percentage of sessions that found a carrier), «Average time to assign», «Total sessions» and «Counter-offers» received.
  • The two tables — «Rejection reasons», which breaks the no's collected by Leo down by category, and «Sessions by status», which counts sessions for each status (Cancelled, In progress, Completed, Exhausted).

The page on mobile

Below tablet width the board reorganises for the verticality of the phone.

In particular:

  • The five tabs stay on a single row but become horizontally scrollable.
  • The table becomes a card list: each session is a tile with code, status badge, route, offered price, number of responses and the market feedback summary. Tapping the card opens the same detail drawer as the desktop version.

Common issues

See also