Logistics & dispatch
Every shipment tracked, every exception escalated.
Booking intake, carrier coordination and exception handling run on agents; dispatchers handle only the calls that need a human voice.
Two ways to start: provision a ready-made solution and connect your own keys, or build it yourself from the template. Free during beta — see pricing.
A carrier reports a two-hour delay at the border. The exceptions agent recalculates the delivery window, drafts the customer notice, and proposes re-slotting tomorrow’s unload — the dispatcher approves with one word and moves to the next call.
The team
Positions in the org — each filled by an agent, a person, or both.
How everyone works together
People and triggers reach the agents, which act on your services and escalate to a human.
How it works
- 1
A transport request arrives; the booking agent captures the load details and confirms.
- 2
The tracking agent watches every active shipment and answers "where is it?" instantly.
- 3
Delays and issues become exceptions with a proposed fix — the dispatcher decides.
- 4
PODs and paperwork are collected and filed per shipment.
Set it up with prompts
Three ways to build this — pick a variant and type the prompts in order. Each step says which agent to address. A working Logistics & dispatch workspace in minutes.
"Where is it?" answered instantly, exceptions surfaced with a proposed fix.
- 1Build the desk→ Onboarding box
New workspace → "Describe your company" → Build my company
Set up dispatch support: a Tracking agent that keeps the active-shipments register (I will define the columns), answers customer "where is my shipment?" emails from it instantly, and an Exceptions agent that watches for trouble signals (carrier delay emails, missed milestones) and brings me each exception WITH a proposed fix — reslot, reroute, or notify-and-wait. Dispatcher seat for me.
Status questions stop consuming the desk; exceptions arrive pre-thought.
- 2Connect the apps→ You (UI)
Apps → Connect
Connect Gmail and Google Sheets with your keys/OAuth. Agents only pull real numbers from connected apps — do this before asking for reports.
- 3Rehearse an exception→ Exceptions agent
Inbox → Exceptions agent
Test: carrier emails that trailer 4512 (Milan → Munich, unload tomorrow 8:00) is delayed 3 hours at Brenner. Handle it: impact, customer notice draft, proposed reslot.
You see the exception pattern — impact, notice, proposal — before live freight depends on it.
- Severity ladder: "Cold-chain and ADR shipments: any delay pings me immediately, not in digest."
- Customer tiers: "Key accounts get proactive notices at every milestone, not just exceptions."
What you get
“Where is my shipment?” answered instantly
Exceptions surface with a proposed fix
Paperwork collected and filed per shipment
What it connects to
Available today via Google, HTTP and MCP sources. Items marked soon are on the connector roadmap.
Set this up for your Logistics & dispatch
Provision a ready-made solution, or build it yourself — start with one agent in one role and grow into the full team.