Failed stops after the run
Sarah Chen, a dispatch lead at Northwind, asked which stops on today's plan had failed. Memtro read the plan's stops and listed the failed ones with their order references, time windows and route, so she could rebook them.
Circuit (Spoke Dispatch) + Memtro
Which deliveries failed today, and has tomorrow's plan gone to the drivers?
Spoke Dispatch (Circuit for Teams) plans your delivery days. Memtro reads plans by date with their drivers and routes, each stop's order references, packages, time windows, ETA and delivery outcome, routes in progress, unassigned stops, depots and optimization results. When asked and granted, it can create, change or delete a plan, add, change or delete stops, optimize a plan and distribute it to its drivers. Spoke can tell Memtro as stops are allocated, attempted or departed, and a job can start on it. Recipients, addresses and proof of delivery are never read back.
In Memtro
What you can do with Circuit (Spoke Dispatch) in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Circuit (Spoke Dispatch) tool, reads what it needs, and answers with the source cited.
What it does
- 01See plans by date with their depot, drivers and routes, and whether each is optimized and distributed.
- 02Read a plan's or a route's stops with order references, packages, time windows, ETA and delivery outcome, counted per outcome.
- 03Check route progress, unassigned stops, depots, drivers by id and the result of an optimization.
- 04When asked and granted, create, rename, re-date or delete a plan, and add, change or delete its stops before it starts.
- 05When asked and granted, optimize a plan and distribute it, which sends each driver their route in the Spoke driver app.
- 06With events on, a stop allocated to a driver, an attempted delivery or a driver leaving a stop can start a job.
Acts when asked
When you ask it to
These tools change something in Circuit (Spoke Dispatch). 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.
- 01Create a plan
- 02Update a plan's title, date, depot or drivers
- 03Delete a plan and its routes
- 04Add a stop to a plan
- 05Update a stop
- 06Delete a stop from a plan
- 07Optimize a plan
- 08Distribute a plan's routes to its drivers
- 09Add an unassigned stop
- 10Delete an unassigned stop
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Circuit (Spoke Dispatch), choosing the same kinds; the tab shows Circuit (Spoke Dispatch)'s own steps. Each event can start a job, with the event as its input. Circuit (Spoke Dispatch) signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01A stop was allocated to a driver (routes sent)
- 02A stop is out for delivery (route started)
- 03A delivery was attempted
- 04A driver left a stop
- 05A stop is next in its route
- 06A stop's tracking link became available
- 07An unassigned stop's tracking link became available
- 08Test event from the settings page
In practice
Ask it like you would a colleague
Once Circuit (Spoke Dispatch) 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.
Circuit (Spoke Dispatch) + MemtroWhich stops on today's plan failed?
Has Tuesday's plan been sent to the drivers?
Which unassigned stops are waiting at the main depot?
Which routes have started but not finished today?
Optimize tomorrow's plan.
Plan sent to drivers
Dan Fletcher, operations manager at Acme Ltd, asked Memtro to optimize Thursday's plan and send it out. Memtro started the optimization, checked the result, then distributed the plan, so each driver saw their route in the Spoke driver app.
Teams
Where it fits
The teams that lean on Circuit (Spoke Dispatch) most, a question each of them asks, and what they connect beside it.
- OperationsMonitors and digests that run themselvesOperations lead, Analyst, Team manager, Administrator“List my jobs”Used alongside Help Scout, Stripe, Xero, Postgres, ShipEngine and 8 more.
- SupportAnswer tickets with the whole company behind youAgent, Team lead, Escalation owner, Head of support“Which VIP conversations have been waiting more than a day?”Used alongside Help Scout, HubSpot, Postgres, Xero, Stripe and 8 more.
- FinanceAsk the ledger questions in plain EnglishFinance lead, Credit control, Management accountant, Founder or CFO“Which invoices over £5k are more than 30 days overdue?”Used alongside Xero, Stripe, Postgres, HubSpot, QuickBooks Online and 10 more.
Better together
Works with
A record in Circuit (Spoke Dispatch) 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.
- Finance and commerceCircuit (Spoke Dispatch) with XeroInvoices, bills, contacts and reports, answered in plain English with figures cited to Xero.
- Finance and commerceCircuit (Spoke Dispatch) with StripeCustomers, charges, invoices and subscriptions through a restricted key.
- Finance and commerceCircuit (Spoke Dispatch) with FellohBookings, payments, refunds, chargebacks, supplier payments and payouts from the travel payments platform.
- SupportCircuit (Spoke Dispatch) with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportCircuit (Spoke Dispatch) with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportCircuit (Spoke Dispatch) with IntercomCustomer conversations and the people behind them, in your company memory.
- Email, calendar and chatCircuit (Spoke Dispatch) with GmailSearch and read mail so the last thread with a customer is one question away, and send the reply when you ask.
- Email, calendar and chatCircuit (Spoke Dispatch) with SlackSearch messages, read channel history and threads, post when you ask, and answer when mentioned.
- Email, calendar and chatCircuit (Spoke Dispatch) with Google CalendarMeetings in a window, event details, and the next two weeks synced into memory, and events it can create, change or cancel when you ask.
Also in Shipping and delivery
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Setup
How to connect
Connect withAPI key
- 1
In Spoke Dispatch, open Settings → Integrations → API and generate a new API key. If the page is missing, Spoke's help says to contact your account manager.
- 2
In Memtro, open Connections → Circuit (Spoke Dispatch) and paste the API key.
- 3
The key is team-wide with no scopes, so an administrator grants the plan, stop and distribute actions to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added under API in Spoke's settings.
- 4
Ask which stops on today's plan failed.
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Circuit (Spoke Dispatch) tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Circuit (Spoke Dispatch)?+
Only when you ask, and only what it has been granted: create a plan; update a plan's title, date, depot or drivers; delete a plan and its routes; add a stop to a plan; update a stop; delete a stop from a plan; optimize a plan; distribute a plan's routes to its drivers; add an unassigned stop; delete an unassigned stop. 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.
Who can use a Circuit (Spoke Dispatch) connection?+
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.
Does Memtro store my Circuit (Spoke Dispatch) data?+
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.
How do I connect Circuit (Spoke Dispatch)?+
API key. In Spoke Dispatch, open Settings → Integrations → API and generate a new API key. If the page is missing, Spoke's help says to contact your account manager.
Can Circuit (Spoke Dispatch) start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Circuit (Spoke Dispatch), choosing the same kinds; the tab shows Circuit (Spoke Dispatch)'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.
Connect Circuit (Spoke Dispatch) in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.