Confirmation campaigns
Call every driver before the route. Confirm pickup, capture exceptions, escalate fast.
Logistics
Driver confirmations, ETAs, exception handling — voiced and logged.
Outbound calls to drivers, dispatchers, and customers — on schedule, with the answers written back into your TMS.
Live ETA updates
Outbound calls to customers when ETAs shift. No more "where’s my truck?" calls inbound.
Exception escalation
When the agent hits an exception it can’t resolve, it escalates to a human with the full context.
TMS write-back
Every call result lands as a structured record in your TMS — not a voicemail nobody listens to.
What the pack does today
01
Confirm a dispatch
Route or pickup confirmation with yes/no and constraints — structured, not a voicemail.
02
ETA or shipment status
Capture reference + question or reported ETA. Never invent tracking events.
03
Exception handling
Delay, access, damage, wrong address, breakdown — structured capture and escalation.
04
Hand off to a dispatcher
Safety-critical events, claims, VIP accounts — warm transfer with full context.
Goals the agent measures against
Confirm a dispatch assignment
Success = structured ops record (create_lead) with explicit yes/no confirmation.
Capture ETA or status
Success = create_lead against a verified shipment reference. No invented ETAs.
Log and escalate an exception
Success = create_lead or transfer_to_human with reference, type, details and contact.
Plugins it talks to
Optional
CRM / TMS webhook
Write confirmations and exceptions into your ops system.
SMS / Email / Notification
Customer ETA notices and driver reminders.
Telephony
Warm transfer to a live dispatcher.
Calendar
Optional appointment-style slots for dock bookings.
Dispatch and ops teams ask us.
Can it call drivers to confirm routes before dispatch?
Yes. It runs outbound confirmation campaigns — one call per driver — capturing an explicit yes/no plus any constraints, and writes a structured record back to your TMS instead of leaving a voicemail.
How does it handle exceptions like delays or damage?
It captures the exception type — delay, access problem, damage, wrong address, breakdown — with the shipment reference and details, then escalates safety-critical events to a live dispatcher with the full context.
Does it make up ETAs or tracking events?
Never. It captures a reported ETA or a status question against a verified shipment reference; it does not invent tracking events. Anything it cannot confirm goes to a dispatcher.
Can it call customers with ETA updates?
Yes — outbound ETA-update calls when a slot shifts, so "where is my truck?" calls stop coming inbound. Every result logs back to your ops system.
How does it connect to our TMS?
Through a CRM/TMS webhook plugin: confirmations, ETAs and exceptions land as structured records. SMS/email notifications and warm transfer to a dispatcher are optional add-ons.
Can it run a large confirmation batch?
Upload a contact list and the platform paces the dial-outs for you — 5 calls a minute by default, raised on request — so you do not flood your trunk or the carrier. Batches take up to 100,000 rows.
What triggers a handoff to a human?
Safety-critical events, claims and VIP accounts get a warm transfer to a live dispatcher with the full call context; routine confirmations and status captures it handles end to end.
Stop missing calls. Stop chasing leads. Start shipping.
White-glove onboarding. 30-day pilot. Cancel anytime.