cooriroo.ai, capabilities
How does an AI agent plan a day of deliveries?
You pool the day's deliveries. The agent proposes how to split them into runs, checks each run against drivers, vehicles and driving hours, and turns the plan you approve into trips.
What the agent does
Splits the pool into runs
A pool is a bag of destinations with a deadline. The agent groups them by area with a cap on stops per run, and shows the split on a map before anything is saved.
Checks before it assigns
Driver and vehicle overlaps, maintenance windows and hours-of-service are checked before a trip is assigned, so the clash is found the evening before.
Turns the plan into trips
Each run gets a driver and a vehicle and becomes a trip in one step, with its stops, time windows and required proofs.
Repeats what repeats
Recurring runs are generated from templates on a schedule, so the agent only plans what is new today.
One request, start to finish
Example session. Names and numbers are illustrative; the tool calls are the platform's real tools.
What a person still decides
- The split. The agent proposes. Nothing becomes a trip until you accept the groups.
- Who drives. You can change any driver or vehicle before the pool is resolved.
- The exceptions. A clash the agent cannot solve is shown to you with its reason.
What it does not do
- It does not hold your orders. Orders stay in your ERP, which sends them in by API.
- It does not promise a saving. We quote no percentage; you see each plan before you accept it.
Questions people ask
What is a delivery pool?
A one-time set of destinations with a deadline. It is the day's work before it has been divided into runs.
Can our ERP send the orders?
Yes, through the API, the MCP server or webhooks. The agent plans from what arrives.
What happens when a driver calls in sick?
The no-show is raised as an exception and the agent proposes a re-assignment that passes the same checks.
See it on your own operation
Forty-five minutes with an engineer, on one real problem from your day.