How many orders can Lyro change in one call?

Up to 500. Create or Update Orders, Delete Orders, and Update Drivers Parameters all cap a single request at 500 records, so a bulk import or a mass reschedule is chunked into batches rather than sent as one call. Create or Update Orders also skips geocoding, which is what makes the bulk path fast.

Does changing a driver's hours disturb routes that are already planned?

Yes, and this catches people out. Update Driver Parameters and Update Drivers Parameters both unschedule the existing routes for those drivers on the dates you touch. Lyro re-runs Start Planning afterwards so the day ends up with a valid plan rather than a set of orphaned stops.

How destructive is Delete All Orders?

Very. With a date it removes every order and planned route for that date, and with no date at all it deletes orders system-wide. Lyro uses Delete Order for a single cancellation and Delete Orders for a specific batch, so the blanket action is reserved for a deliberate reset.

Can Lyro optimise a route before the orders exist?

No. Start Planning requires the orders to be created first, which is why the booking and planning steps are separate. Get Planning Status reports progress on a running job by its ID, and Stop Planning halts one that was started against the wrong date.

Optimoroute MCP integration

Finds an order, reports its scheduled window and proof of delivery, books new stops, and runs the day's route optimisation.

Connect Optimoroute See all integrations

17actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create order
Lyro creates a new delivery order in OptimoRoute. Dispatchers add jobs without platform access.
Get order completion details
Lyro retrieves proof of delivery and completion data for orders. Support confirms deliveries without checking the planning system.
Delete order
Lyro removes a single order from OptimoRoute. Teams cancel jobs instantly without manual deletion.

See all 17 actions

How businesses use Optimoroute + Lyro

Each card is one request a support team gets, and the Optimoroute actions Lyro runs to close it.

Answer where a delivery is
Lyro finds the order by number or date range, reports whether it is scheduled and which driver and time slot it sits in, and returns the completion record with its proof of delivery once the stop is done.
Search OrdersGet Order Scheduling InfoGet Order Completion Details
Book a delivery or pickup from the conversation
Lyro creates the order with its address, time window, and constraints, or pushes a whole import of up to 500 at once, then reads the stored record back to confirm what was booked.
Create OrderCreate or Update OrdersGet Orders
Run the plan for a date
Lyro starts optimisation for a date or date range, reports how far the planning job has got, and returns the resulting routes including their stops and any orders left unassigned.
Start PlanningGet Planning StatusGet Planned Routes
React to what happens in the field
Lyro reads the mobile events drivers generate - completions, failures, on and off duty - checks the current driver list, and adjusts a driver's hours or vehicle when the day changes.
Get Mobile EventsGet DriversUpdate Driver Parameters

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Optimoroute actions it has and picks the ones a request needs.

01
Connect Optimoroute
Authorize the Optimoroute account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Optimoroute actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Optimoroute · Lyro

Everything else about Optimoroute

Setup, permissions, and the limits of what Lyro can do inside Optimoroute.

Up to 500. Create or Update Orders, Delete Orders, and Update Drivers Parameters all cap a single request at 500 records, so a bulk import or a mass reschedule is chunked into batches rather than sent as one call. Create or Update Orders also skips geocoding, which is what makes the bulk path fast.

Every action available in Optimoroute

All 17 actions your agent can call on Optimoroute, straight from the live MCP connection.

Create order
Create a new order or update an existing order in OptimoRoute.
Create or update orders
Bulk create, update, or replace multiple orders at once without geocoding.
Delete all orders
Remove all orders and planned routes for a specified date.
Delete order
Remove a single order from the OptimoRoute system.
Delete orders
Delete one or more orders from the system in bulk (max 500 per request).
Get order completion details
Retrieve completion details for one or more orders including proof of delivery data.
Get drivers
Retrieve all drivers in the system.
Get mobile events
Retrieve mobile events from drivers' field operations.
Get orders
Retrieve one or more orders from OptimoRoute.
Get planning status
Retrieve the status of an active planning/optimization process.
Get planned routes
Retrieve all planned routes for a given date.
Get order scheduling info
Retrieve scheduling information for a specific order.
Search orders
Search for orders in OptimoRoute based on criteria.
Start planning
Start the planning/optimization process for a specified date or date range.
Stop planning
Stop an active planning/optimization process.
Update driver parameters
Update driver parameters for a specific date including work times, vehicle assignment, and start/end locations.
Update drivers parameters
Update parameters of multiple drivers for specified dates in bulk (max 500 per request).