Carriers, 3PL & last mile
The delivery window, confirmed by phone, at scale.
Freight runs on confirmations - is someone at the dock, is the address right, can the driver get in. Each one is a thirty-second call that nobody has time to make, so exceptions are discovered on arrival instead.
An illustrative reference architecture, not a customer
case study. No organisation is named and no deployment is described - this is
what the layers look like for a logistics & freight organisation,
so you can map it onto your own estate.
Channelswhere the conversation starts
Inbound numberspublished lines
SIP / contact centreexisting estate
Outboundcampaigns and callbacks
In-appbrowser WebRTC
▼
VoiceKernelthe agentic voice layer
Conversationagent, voice, turn taking
Knowledge groundinganswers with citations
Tool callsreads and writes back
Transferto a human, with context
Tenant isolationownership registry
Audit and erasureper call, per mutation
▼
Integrationyour boundary, your rules
REST + typed SDKscoped API keys
Signed webhooksretried, replayable
Live event streamSSE
▼
Logistics & Freightyour systems of record
TMSloads, routes, ETAs
WMSdock and slot booking
Track & tracecarrier events
Driver appcheck-in and PoD
CRMshipper accounts
Only the bottom layer is specific to logistics & freight. The
three above it are identical in every deployment, which is the point: the
voice layer does not need to know what industry it is in, only which systems
it is allowed to reach and what it may say.
What it changes
Mechanisms, not projections. Each of these follows from something structural
about the work, so you can check whether it holds for your own queues.
Exceptions surface before the truck movesA wrong address found the night before costs a phone call; found on arrival it costs a failed delivery and a redelivery.
Redelivery rates fall for a structural reasonMost failures are absence, and absence is knowable in advance by asking.
Drivers stop waiting on holdSlot booking and check-in are answered immediately rather than queued behind shipper enquiries.
Coverage extends past office hoursFreight moves overnight; the confirmation call no longer has to wait for a day shift.
What the agent actually does
Delivery window confirmationOutbound the day before to confirm someone will be there, reschedule in the same call, and write it back to the route.
Failed delivery recoveryCall at the point of failure, find out what went wrong, and rebook before the parcel goes back to the depot.
Dock and slot bookingTake carrier calls for slot times and book them against the warehouse schedule without a person in the loop.
What keeps it deployable
Address data minimisedThe agent confirms and corrects; it does not export the address book.
Driver identity verifiedCheck-in requires the load reference, not a name.
Contact rules respectedConsumer recipients are washed against do-not-call before any outbound run.
A failed delivery costs the second attempt, the depot handling and the customer contact that follows - all of which start with nobody being home.
NextRead the source
Everything above is in the open-source Community edition. Nothing on
this page needs a licence.
NextRun it yourself
Point it at your provider account and put one queue through it before
you talk to anybody.
NextThen buy the guarantees
An Enterprise agreement adds the SLA and the
support contract when it carries real volume.