ContiRoute | Pilot Operations FAQ
Operational Framework

How it works in a live operation

Everything you need to know about integrating ContiRoute into your existing dispatch workflow during our pilot phase.

Pilot FAQs (Operations)

Advisory mode (recommended routes)

During the pilot, ContiRoute provides recommended routes, stop order and ETAs. Your dispatch team remains in control — nothing is auto-dispatched without approval.

Overrides

Coordinators can override stop order, vehicle assignment and timings at any point. We log the decision context (“why this route”) for auditability.

Setup time

If jobs are shared via CSV/Excel/Google Sheet, first outputs can be generated the same day. After the first template is confirmed, typical setup is 15–45 minutes.

Integrations

Pilot runs via CSV/Excel/Google Sheets import/export. API/webhook integration can be added after value is proven.

Last-minute changes

New urgent jobs or delays can trigger a re-optimisation and we return an updated recommended plan with minimal disruption (a “delta plan”).

Vehicle types and stop times

We model vehicle type and key constraints, plus service/stop times. Parking/wait time can be set as a configurable allowance and refined with your feedback.

Mixed fleets

Mixed fleets (van/car/bike) can be planned, with allocation based on suitability and constraints.

Customer updates

We can output clean ETA/status updates for your customer comms process. Full messaging is optional and not required for the pilot.

Responsibility

ContiRoute is decision-support. Your operations team remains responsible for final decisions during the pilot.

Pilot agreement

The pilot LOI is non-binding and for evaluation only.

Ready to see it in action?

Request a demo or start your same-day pilot setup.

Scroll to Top