Review planned routes, late stops, driver exceptions, delivery windows, and schedule questions before operational changes reach the road.
Strawberry reads the OptimoRoute account you have open and turns the visible plan into a reviewable dispatch brief.
01
Start the day with the route exceptions, not the entire map.
Dispatchers do not need another overview of every stop.
They need the handful of routes where timing, capacity, location, or customer constraints could break the plan. Extract those exceptions from the visible OptimoRoute schedule into a decisive morning brief.
02
Bring customer constraints into route review.
A route can look efficient on a map while ignoring a gate code, service note, delivery window, or agreed contact arrangement. Check the route plan against the customer context already open in the browser before preparing an exception.
03
Make driver handovers specific enough to act on.
The driver needs to know which stops differ from the plan and why, not receive a generic daily recap. Convert the current OptimoRoute view into a handover with the exact route, stop, instruction, and unresolved question.
04
Check the plan before drivers start committing to it.
A 06:30 weekday pass is early enough to fix unassigned work or delivery-window conflicts before the first routes lock in. Preserve the OptimoRoute exception criteria as a skill and have a routine prepare the dispatch report every morning.
Yes. It can use the OptimoRoute browser context you provide to inspect the live page, prepare a review, and work alongside the related tabs or files you select.
It can prepare OptimoRoute work in the browser, but an action that changes records, communication, access, routing, or spend should stay subject to your approval.
Yes. Capture the OptimoRoute-specific checks in a skill and have a routine prepare the review at the cadence that fits the operational decision.
No. OptimoRoute is handled through its browser tab on this page, not through a Strawberry integration in Settings.
Confirm the relevant OptimoRoute context, the evidence behind the recommendation, and the downstream effect of the proposed action before proceeding.