Failed drops at the end of the day
Tom Reilly, dispatch manager at BigCo, asked which deliveries failed today. Memtro listed the failed tasks with driver, team and the failure reason, and showed most had come from one route.
Which deliveries failed today, and why?
Onfleet connects Memtro to your last-mile delivery. It reads tasks by state, each with its delivery window, assigned driver and team, delay, and whether it succeeded or why it failed, plus drivers on and off duty with their teams and current task, teams and hubs. When asked, and once an administrator has granted the action by name, it can create a delivery or pickup task, which texts the recipient unless told not to, change a task, force-complete or delete one, and add a driver. Recipients' names, phones and addresses, and drivers' phones and locations, are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Onfleet tool, reads what it needs, and answers with the source cited.
These tools change something in Onfleet. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Onfleet, choosing the same kinds; the tab shows Onfleet's own steps. Each event can start a job, with the event as its input. Onfleet signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Onfleet is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which deliveries failed today, and why?
Which drivers are on duty right now?
Which tasks are running late this afternoon?
How many tasks does the North team have?
Reassign task 7f3a2b to Sam on the North team
Tom Reilly, dispatch manager at BigCo, asked which deliveries failed today. Memtro listed the failed tasks with driver, team and the failure reason, and showed most had come from one route.
Sarah Chen, operations lead at Northwind, asked Memtro to give a late task to another driver on the same team. Memtro changed the assignment in Onfleet, and the new driver saw the task in their app at once.
The teams that lean on Onfleet most, a question each of them asks, and what they connect beside it.
A record in Onfleet is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Onfleet dashboard, open Settings → API & Webhooks. Only an administrator can create API keys.
Create an API key named Memtro and copy it. A key limited to tasks it creates sees only the tasks Memtro made, and cannot read drivers or teams.
In Memtro, open Connections → Onfleet and paste it into API key.
Ask your first question: which deliveries failed today?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Onfleet tools are the same everywhere.
Only when you ask, and only what it has been granted: create a delivery or pickup task (texts the recipient unless notify_recipient is false); change a task's notes, time window, destination or assigned driver or team; force-complete an active task as succeeded or failed (final); delete an unassigned task (permanent); add a driver to one or more teams (gives them access to the driver app). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In the Onfleet dashboard, open Settings → API & Webhooks. Only an administrator can create API keys.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Onfleet, choosing the same kinds; the tab shows Onfleet's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time