Routite Copilot · Dispatch copilot

Ask the plan why, then decide

Copilot is how dispatchers talk to Routite. It explains each re-plan, answers questions about the day, runs what-ifs, and executes approved changes inside your permissions.

A typical exchange

  1. AskWhy did this stop move?
  2. AnswerReasons from the solver
  3. What-ifTry another option
  4. ActApprove and send

Copilot conversation · Zone 4

Example

Dispatcher Why did stop 214 move off van 2?

Van 2 picked up 8 late orders after 10:30. Keeping stop 214 would have pushed three later stops past their windows. Van 4 passes 600 m away at 13:05 and has room, so it now serves 214 at 13:08, inside the 12:00–14:00 window.

Dispatcher What if van 5 also leaves at 14:00 for the clinic run?

What-if: van 5 off at 14:00 · 4 stops move · 1 window at risk1 late
Example Conversation and figures are illustrative. Copilot answers from the plan and its reasons; it does not invent stops.

Stop 01 · Capabilities

What Copilot does

Explain

Plain-language reasons

Every moved stop is explained from the solver's own reasons, not guessed.

Ask

Questions about the day

Which vans are behind? Who can take a 30-minute job near the depot?

What-if

Try before you send

Change a cut-off, add a van, hold an order, and compare plans.

Approve

One place to decide

Approve, edit or reject each proposed change.

Guardrails

Acts within your role

Copilot cannot do what the person using it is not allowed to do.

Record

Decisions are logged

Each approval stores who, what, when and why.

Stop 02 · How it works

How Copilot works

  1. askquestion

    Dispatcher asks

    A question or a request in plain language.

    Model NeMo
  2. look uptools

    Copilot checks

    It queries the plan, Twin and Optimize through the same API as the console.

    Guardrails Role checks
  3. answerreview

    Dispatcher decides

    An answer with sources, or a proposed change waiting for approval.

    Logged Yes

Stop 03 · Specification

Specification

Draft specification. Figures are design targets, not measured results.
ItemDetailStatus
ModelNVIDIA NeMo, tool-using agentIn build
GuardrailsNeMo Guardrails, role-scoped actionsIn build
LanguagesEnglish firstOthers planned
ExecutionOnly after approval by defaultIn build

Stop 04 · Place in the loop

Where Copilot sits

Copilot sits between Optimize and Edge: nothing reaches a driver until a person, or a rule they set, approves it.

Return leg Edge sends real arrival and service times back to Twin. ETA and demand models retrain on them, so tomorrow's first plan starts closer to reality.

Stop 05 · Questions

Questions dispatch teams ask

Can Copilot make things up?

It answers from the plan, the twin and the solver's reasons, and links each answer to them. If it does not know, it says so.

Can it act on its own?

Only inside rules you set, such as swaps within one route. Everything else waits for approval.

Does it replace dispatchers?

No. It removes the lookups and phone calls so dispatchers can decide faster.

Stop 06 · Destination

Next step

See Copilot on your own data

A replay of one past day shows what this product would have done, with every assumption written down.