Interactive Demo · Logistics & 3PL
A live demo of our Logistics AI agents.
Driver SMS that runs check-calls. Customer Email that runs the front desk. A Copilot that runs alongside your best dispatcher.
Walk through the seven steps a 3PL takes to deploy three agents — two outbound (Driver SMS, Customer Email) and one internal Copilot that augments your human dispatcher with route assignment recommendations from McLeod, Samsara, and Project44.
Agent 01 · Driver SMS
The check-call agent. three hours of dispatcher texting · automated.
Pickup confirmations, mid-route ETAs, delivery confirms, exception escalations. The agent runs the whole driver-comm loop with strict HOS guardrails — never wakes a driver in mandatory rest, never asks data the telematics already has.
Provision the driver SMS line. outbound only · with HOS awareness.
Twilio number connected to McLeod webhooks. The agent reads telematics + HOS before any outbound SMS.
Channel
Twilio + McLeod
Twilio number for driver-facing SMS. The agent runs check-calls, ETA captures, exception reports, and end-of-day confirmations. Replaces 3–4 hours/day of manual dispatcher texting.
Connection status
- Webhook URLAwaiting connection
- Display name—
- Encryption—
- Message routingDirect to your team
Until you flip Go Live in Step 07, no traffic routes through the agent. You can disconnect at any time.
Drop in your driver roster and shipper-specific cadence rules.
Driver certs, cadence policies, exception playbook, shipper-specific requirements (Walmart format, cold-chain temp logs).
Drop brochures, FAQs, price sheets, transcripts
PDF · XLS · DOCX · CSV · click anywhere to simulate
No files yet. Drop one (or click the zone) to see the agent index it.
Verify driver constraints before any check-call fires.
Confirm cert status, language preference, home-time pattern. Flag new hires for tighter cadence.
What the agent now knows
- CDL-A team drivers (8)
- CDL-A solo drivers (52)
- Hazmat endorsement (24)
- Reefer-certified (38)
- New hires (last 30 days, training cadence)
Knowledge coverage
4
Branches
110
Total items
2
Open gaps
0
Approved
Items flagged in amber need your review before the agent uses them. Approve, edit, or remove inline.
HOS comes first. Always. never wake a driver in rest.
Quiet-hours per HOS · skip redundant asks (telematics already has it) · auto-escalate mechanical · never share customer details with drivers.
Guardrails — what the agent will never do
5 activeNever send a check-call SMS during a driver's mandatory 10-hour rest period.
Never request status data the dispatcher already has from telematics.
Never ask a driver to call back during active driving hours (per HOS).
Always escalate exception code 'mechanical' to dispatcher within 60 seconds.
Never share customer details (price, contracts) with drivers.
Never override DOT-compliance requirements under any circumstances.
Hot lead criteria — when the agent escalates to you
Leads with a stated budget at or above this escalate.
Preview
Escalate when budget ≥ $0K and timeline ≤ 1 days.
How a geofence cross becomes a check-call. node by node.
Trigger → driver match → HOS check → telematics pre-check → template → send → parse reply → escalate exceptions.
Decision tree
Walk through three driver scenarios. pickup, mechanical, rest-period.
See exactly how each plays out. HOS guardrails hold quiet-hours messages; mechanical exceptions escalate in under 60 seconds.
Driver SMS thread · Pickup confirmation
Click Run scenario to play the conversation.
Decision tree
Type a rule. Run Shadow Mode. then start auto-pinging.
Shadow Mode shows you every check-call the agent would have sent. Approve, edit, or block until the cadence feels right.
Tune the agent by typing
Or pick a suggested rule
Nodes rewired by this rule
Type a rule or pick a suggestion to see which nodes update.
Shadow mode — review every draft before send
Day
3 / 5
Items reviewed
0 / 2
Agent errors
0
Buyer message
[End-of-day status SMS would have gone to a driver still in his rest period]
Agent draft
Held — driver in mandatory 10h rest. Queued for 5:15 AM next day. No SMS sent.
Buyer message
[Mid-route check-call queued for a driver whose telematics shows him at delivery already]
Agent draft
Skipped — Samsara reports geofence crossing at delivery 4 min ago. Status auto-updated to 'At delivery' without driver SMS. Avoided redundant ask.
Ready to go live · Driver SMS
You’re a click away from production.
When you flip the switch, the Driver SMS agent takes over inbound traffic. Hot leads still escalate to your team; everything else gets handled. The kill switch stays one click away.
- Shadow-mode approval rate: 96%
- Guardrails active: 5
- Workflow nodes audited: 10 / 10
- Escalation routing tested across all personas
Go Live
Agent 02 · Customer Email
The shipper-facing agent. status, exceptions, rate-confirmations.
Shippers email all day asking 'where is my load?'. This agent pulls live status from McLeod, attaches PODs on delivery, and notifies on detention or mechanical exceptions — with strict guardrails on rate quotes and revised-delivery commitments.
OAuth into the customer-service inbox. Gmail or Microsoft 365.
The agent reads inbound, drafts replies with live McLeod data, holds anything outside guardrails for the dispatcher.
Channel
Gmail / Outlook
OAuth into the customer-service inbox. The agent handles load-status inquiries, exception notifications, and rate-confirmation responses. Held drafts queue in the dispatcher inbox.
Connection status
- Webhook URLAwaiting connection
- Display name—
- Encryption—
- Message routingDirect to your team
Until you flip Go Live in Step 07, no traffic routes through the agent. You can disconnect at any time.
Drop in your shipper account terms and exception templates.
Contract terms per shipper (Walmart format, Costco detention schedule), templates, exception library. The agent applies the right one automatically.
Drop brochures, FAQs, price sheets, transcripts
PDF · XLS · DOCX · CSV · click anywhere to simulate
No files yet. Drop one (or click the zone) to see the agent index it.
Verify shipper-specific format rules before any outbound mail.
Walmart strict format, cold-chain temp inclusion, Costco detention pay. Each gets its own response shape.
What the agent now knows
- Tyson Foods — daily volume + contract terms
- Walmart DCs — strict format requirements
- Costco — detention pay schedule
- Cold-chain accounts (12) — temp logging required
Knowledge coverage
3
Branches
61
Total items
1
Open gaps
0
Approved
Items flagged in amber need your review before the agent uses them. Approve, edit, or remove inline.
Rate quotes and revised delivery times are never auto-sent.
Spot rates only from McLeod. POD always attached on delivery confirmation. Detention waivers always go through the controller.
Guardrails — what the agent will never do
5 activeNever quote spot rates without the rate-confirmation generated by McLeod.
Never disclose driver names or telematics specifics without shipper-contract permission.
Never commit to a revised delivery time without dispatcher sign-off.
Always attach the POD when sending delivery confirmation.
Never email Walmart DCs outside their strict format requirements.
Never agree to detention waivers without controller approval.
Hot lead criteria — when the agent escalates to you
Leads with a stated budget at or above this escalate.
Preview
Escalate when budget ≥ $5K and timeline ≤ 1 days.
How an inbound becomes a reply. or a held draft.
Parse → identify load → match shipper rules → pull McLeod status → attach POD if delivery → draft → rate guardrail → send (or hold for dispatcher).
Decision tree
Walk through three shipper interactions. routine, exception, rate-quote.
See exactly when the agent auto-replies (status + live data) vs. holds for human (rate quotes, detention waivers).
Email thread · Shipper asks for status
Click Run scenario to play the conversation.
Decision tree
Type a policy. Run Shadow Mode. then send for real.
7-day Shadow Mode. The agent drafts every reply; you approve, edit, or reject. When approval rate is high, status emails auto-send and only edge cases queue for you.
Tune the agent by typing
Or pick a suggested rule
Nodes rewired by this rule
Type a rule or pick a suggestion to see which nodes update.
Shadow mode — review every draft before send
Day
5 / 7
Items reviewed
0 / 2
Agent errors
0
Buyer message
Shipper asked: 'What's the spot rate on this lane?'
Agent draft
Held — spot rate requested. Rate-quote ticket created in McLeod, dispatcher notified. Customer received: 'We'll send rate confirmation by EOD via McLeod portal.' No verbal quote committed.
Buyer message
Shipper asked: 'Can you waive the detention pay for this load?'
Agent draft
Held — detention waiver request. Routed to controller for approval. Customer received: 'Our controller will review and respond within 1 business day.' No commitment given.
Ready to go live · Customer Email
You’re a click away from production.
When you flip the switch, the Customer Email agent takes over inbound traffic. Hot leads still escalate to your team; everything else gets handled. The kill switch stays one click away.
- Shadow-mode approval rate: 96%
- Guardrails active: 5
- Workflow nodes audited: 10 / 10
- Escalation routing tested across all personas
Go Live
Agent 03 · Dispatcher Copilot
The internal copilot. captures dispatcher knowledge · proposes assignments.
The Copilot is different. It doesn't talk to drivers or shippers — it sits next to your senior dispatcher in McLeod. For every new load, it surfaces the top 3 driver assignments with rationale (deadhead miles, HOS, preferences, override risk). The dispatcher approves with one click — or overrides, and the Copilot learns.
Connect McLeod, Samsara, Project44. read-only · the Copilot proposes, the human approves.
Read-only TMS + telematics + visibility. The Copilot never auto-executes. Every assignment requires dispatcher approval — that's the safety model.
Channel
McLeod + Samsara + Project44
Internal-facing. Read-only access to McLeod (TMS), Samsara (telematics), and Project44 (visibility). The Copilot proposes load assignments; the human dispatcher approves or overrides every one.
Connection status
- Webhook URLAwaiting connection
- Display name—
- Encryption—
- Message routingDirect to your team
Until you flip Go Live in Step 07, no traffic routes through the agent. You can disconnect at any time.
Drop in 18 months of route history and your dispatcher's tribal knowledge.
Historical routes, driver preferences, shipper account priorities, dispatcher decision audit. The Copilot models how your best dispatcher thinks.
Drop brochures, FAQs, price sheets, transcripts
PDF · XLS · DOCX · CSV · click anywhere to simulate
No files yet. Drop one (or click the zone) to see the agent index it.
Verify constraint encoding before any recommendation fires.
Driver certs, home-time prefs, shipper priorities, rate floors. Approve each constraint and flag anything that needs tightening.
What the agent now knows
- CDL endorsements per driver (hazmat, tanker, doubles)
- Home-time preferences (weekly home / over-the-road / regional)
- HOS clocks · live from ELD
- Reefer / dry-van / flatbed certifications
- Newer drivers — lower-mileage preference
Knowledge coverage
4
Branches
4305
Total items
2
Open gaps
0
Approved
Items flagged in amber need your review before the agent uses them. Approve, edit, or remove inline.
The Copilot is always advisory. never auto-executes.
HOS violations are hard-filtered. Cert mismatches are hard-filtered. Rate-floor violations get flagged but not blocked — dispatcher decides. Always shows top 3, not just #1.
Guardrails — what the agent will never do
6 activeNever propose an assignment that violates DOT HOS rules.
Never assign a load to a driver without the required endorsements/certs.
Never propose a rate below the lane floor without dispatcher flag.
Never override a driver's home-time preference more than once per month.
Always show the dispatcher the top 3 alternatives, not just the recommended one.
Never auto-execute any assignment — always require dispatcher approval.
Hot lead criteria — when the agent escalates to you
Leads with a stated budget at or above this escalate.
Preview
Escalate when budget ≥ $3K and timeline ≤ 1 days.
How a new load becomes a recommendation. node by node.
Load → candidate pool → HOS/cert filter → deadhead optimizer → preference scorer → rank top 3 → rate-floor check → recommend to dispatcher → execute on approve.
Decision tree
Walk through three dispatch scenarios. routine, override, rate-flag.
Routine: dispatcher approves #1 in 8 seconds. Override: dispatcher picks #2, Copilot logs the reason and learns. Rate-flag: load below floor held for human decision.
Dispatch event · Routine assignment
Click Run scenario to play the conversation.
Decision tree
Type a rule. Run Shadow Mode for 7 days. then go to copilot mode.
Shadow Mode: Copilot makes recommendations, dispatcher dispatches manually. We compare. When approval rate is 90%+, Copilot moves to live recommend-and-approve mode.
Tune the agent by typing
Or pick a suggested rule
Nodes rewired by this rule
Type a rule or pick a suggestion to see which nodes update.
Shadow mode — review every draft before send
Day
5 / 7
Items reviewed
0 / 2
Agent errors
0
Buyer message
[Load: Birmingham → Nashville · dispatcher made manual assignment]
Agent draft
Copilot would have recommended: P. Singh (28 mi deadhead, HOS clean). Dispatcher manually assigned: K. Lopez (62 mi deadhead). Override logged. Reason input: 'wanted to give P a day off — he ran long last week'. Pattern added to driver-preference scorer.
Buyer message
[Load: Detroit → Chicago · rate 8% above lane floor]
Agent draft
Copilot recommended: top 3 with M. Patel #1 (35 mi deadhead, home-time fits, premium account). Dispatcher approved #1 in 14 seconds. Auto-executed in McLeod.
Ready to go live · Copilot
You’re a click away from production.
When you flip the switch, the Copilot agent takes over inbound traffic. Hot leads still escalate to your team; everything else gets handled. The kill switch stays one click away.
- Shadow-mode approval rate: 96%
- Guardrails active: 5
- Workflow nodes audited: 10 / 10
- Escalation routing tested across all personas
Go Live
Take this agent with you
Download a real, runnable version — the blueprint, an importable n8n workflow, and sample data. Try it in minutes, no strings.
Want this for your fleet?
The console you just walked through is the same one we build for every 3PL we deploy.
Discovery is 60 minutes. Deployment is 6–8 weeks for the Copilot (the longest in our catalog). We'll spend time with your senior dispatcher capturing the rules before we touch a line of code.