Skip to main content
VSI Technologies
Menu
Book a strategy call

Dispatch that scales without another dispatcher.

Exception handling, customer communication and dispatch across sites.

Book a free 20-minute logistics & 3pl assessment

Industry overview

Inside a logistics & 3pl operation

Dispatchers spend their day on exceptions and on the phone. Volume grows, the exception rate grows with it, and the only lever anyone has is headcount, which arrives three months after it was needed and leaves when volume dips.

A dispatcher’s day is not planning; it is interruption. The plan is made early and then dismantled by reality, a late arrival, a refused delivery, a driver held at a receiving dock, a customer calling to ask where something is. Each interruption is small and the aggregate is a role where nobody gets an uninterrupted hour, which is why experienced dispatchers burn out and why the knowledge leaves with them.

The exception rate does not scale linearly with volume; it scales worse. More loads means more interactions with more receiving facilities, more carriers, more edge cases, and the exceptions interact with each other. Twice the volume routinely produces more than twice the exception handling, which is why the headcount answer keeps disappointing.

Headcount is also the slowest possible lever. A dispatcher hired in response to a peak arrives after it, takes months to become useful because the knowledge is tacit, and becomes a cost problem when volume dips. Everybody in the sector knows this and does it anyway, because the alternative on offer has usually been a system nobody had time to configure.

Customer communication is where the cost is least visible and most damaging. Status calls are inbound because status updates are not outbound, and each one costs a dispatcher an interruption at exactly the moment they were doing something else. A customer who has to call to find out where their freight is has already formed an opinion about the service.

Underneath it is a data problem that makes everything harder: telemetry, transport management, and customer commitments live in different systems with different notions of the truth, so answering a simple question requires a person to reconcile three screens.

Common challenges

Challenges we see across logistics & 3pl

If three or more are true, the rest of this page is about your operation.

  • Dispatchers get no uninterrupted hour in a working day
  • Status calls are inbound because updates are not outbound
  • A late-arrival exception is discovered when the customer calls
  • Appointment scheduling with receiving facilities is done by phone, repeatedly
  • Accessorial disputes are settled by whoever has the patience for them
  • The answer to a simple freight question requires reconciling three screens

How we help

Five practices, applied to logistics & 3pl

AI, cloud, cybersecurity, hardware and programme delivery, one integrated bench, each practice applied to how logistics & 3pl actually operates.

  1. 01

    AI & Automation

    Agents for the freight desk’s constant chase: track-and-trace across carrier portals, appointment scheduling, document collection, BOLs, PODs, customs paperwork, and exception detection in MercuryGate or your TMS before the customer calls to report it first.

  2. 02

    Cloud & Infrastructure

    Integration architecture for an industry that runs on EDI and APIs in equal measure: reliable carrier connectivity, telematics feeds from Samsara into the systems that dispatch actually uses, and a data layer that gives one answer to "where is the load".

  3. 03

    Cybersecurity

    Hardening for the attack the sector actually gets, fraudulent carrier onboarding and payment redirection: identity verification workflows, segregated payment-change controls, and monitoring on the portals where double-brokering starts.

  4. 04

    Hardware & Lifecycle

    Ruggedised fleets for dock and yard: scanners, mounted terminals, driver tablets, sourced, provisioned to your WMS and ELD stack, spared to keep lanes running, and swapped on a lifecycle instead of on failure.

  5. 05

    Program & Project Management

    Rollouts sequenced by lane and facility so freight never stops: pilot terminal first, playbook written from what it teaches, then the network, with cutover windows set by your volume calendar, not ours.

Where we start

Automation candidates

Deliberately mundane. The impressive-sounding workflow is rarely the one worth doing first.

  • Exception handling: detection, triage and the first customer contact
  • Check calls and status updates, outbound rather than requested
  • Appointment scheduling with receiving facilities
  • Carrier and driver communication across languages and channels
  • Billing exceptions and accessorial disputes

Systems we integrate with here

If you run one of these, this is the conversation.

  • MercuryGate
  • Descartes
  • Manhattan Associates
  • Salesforce
  • Samsara

Our solutions

How we transform logistics & 3pl operations

What happens today, what changes, and what to watch for as each workflow is automated.

Exception handling

Today
An exception surfaces when somebody notices or when a customer calls. The dispatcher then reconstructs what happened before they can act.
After
Detected from telemetry and transport data as it develops rather than after it lands, triaged by impact, and the first customer contact made proactively with what is known and what is being done.
What to watch
Escalation timing matters more than the happy path. An agent that handles routine exceptions well but escalates a serious one late is worse than no agent, and the thresholds have to be set from your data rather than a default.

Check calls and status updates

Today
Customers call to ask. Dispatchers answer, which is an interruption at the worst possible moment and produces no record anyone else can use.
After
Status pushed outbound on the cadence each customer actually wants, on the channel they use, so the inbound call stops being necessary. Exceptions get a call from a person; routine progress does not need one.
What to watch
Over-notification produces the same result as none, people stop reading. Cadence has to be per account and adjustable by the customer.

Appointment scheduling

Today
Phone calls to receiving facilities, held on hold, called back, and the outcome written somewhere that is not the transport system.
After
Appointment requests and confirmations handled across whichever channel the facility uses, with the result written back to the transport management system so the plan reflects it.
What to watch
Facility rules are idiosyncratic and often unwritten. This works where the pattern has been learned from your own history, and it degrades where a facility is new, so new facilities should route to a person until the pattern is known.

Carrier and driver communication

Today
Calls and messages across languages, channels and time zones, handled by whoever is available and understood variably.
After
Handled in the driver’s language, on the channel they actually use, with the substance written back into the record so the next person has the context.
What to watch
A driver is not a customer and the tone has to reflect that. Communication that reads as automated surveillance damages carrier relationships, which are harder to repair than customer ones.

Billing exceptions and accessorials

Today
Disputes settled by whoever has the patience, often by conceding, because the evidence takes longer to assemble than the amount is worth.
After
Evidence assembled automatically, detention timestamps, telemetry, communication history, so the dispute is answered with facts in minutes rather than conceded.
What to watch
This one has a relationship cost if it becomes adversarial. The objective is accuracy, not winning; a customer who feels litigated against on small amounts is a customer you lose on a bid.

The operating picture

Where the agent layer sits in the life of a load

Your operating loop todayThe agent layer we deploy into it
01

Quote and book

Rates, capacity and commitments move faster than the team can type.

Agent layer

Drafts quotes from your rating logic and books the accepted ones straight into the TMS.

02

In transit

Every load generates where-is-it traffic across portals, calls and email.

Agent layer

Polls carrier systems and telematics, updates every shipment’s status, and answers the routine checks automatically.

03

Exception

Detention, missed appointments and rolled loads burn the margin.

Agent layer

Detects the slip as it forms, notifies the customer with the recovery plan, and starts the reschedule.

04

Settle

PODs, accessorials and carrier invoices decide whether the load made money.

Agent layer

Collects the documents, matches invoice to quote to contract, and queues only the mismatches for a person.

Quote to cash, the loop that runs hundreds of times a day: agents carry the tracking, the paperwork and the status traffic, so dispatchers work exceptions instead of refreshing carrier portals.

Platforms and systems

Technology we work with in logistics & 3pl

The systems of record this sector runs on, and why each one matters to a deployment.

MercuryGate
Transport management of record for many brokers and 3PLs. The load and stop model is what any exception logic has to align to.
Descartes
Routing, compliance and network connectivity. Frequently where the external communication actually happens.
Manhattan Associates
Warehouse and supply chain execution, which is where dock and appointment reality lives.
Salesforce
Customer relationship and commitment data. What was promised to whom usually lives here rather than in the transport system.
Samsara
Telematics. The source of the signal that lets an exception be detected as it develops rather than after it lands.

The constraint

What makes this sector harder

Everything here is time-critical and partly outside your control. An agent that handles the routine contact well but escalates late is worse than no agent, so the escalation thresholds matter more than the happy path, and they are set from your data, not from a default.

The defining property of this sector is that the important information arrives from parties you do not control. A receiving facility, a carrier, a driver, a customs broker, none of them run your systems and most of them will not change how they communicate to suit you. Any design that assumes clean structured input from external parties is a design that will work in a demonstration and fail in a yard.

Time criticality changes what a wrong answer costs. In most sectors an agent that handles ninety per cent of cases well and escalates the rest slowly is a clear win. Here, the ten per cent are the ones with a detention clock running, a customer commitment at risk, or a driver waiting, so a late escalation costs more than the ninety per cent saved. Threshold design is the engagement, not a configuration step within it.

Tacit knowledge is the other constraint. Experienced dispatchers know that a particular facility will not answer before ten, that a specific customer wants a call rather than a message, that a certain lane has a recurring problem in winter. None of it is written down. Extracting it is the genuinely hard part of the first month and it cannot be done from a systems integration; it is done by sitting with dispatchers.

And the relationship dimension is easy to underestimate. Freight is a relationship business at the margins, and the margins are where the work is won. Automation that makes communication feel transactional can cost more in retained business than it saves in dispatcher hours, which argues for automating the notification and the evidence-gathering while leaving the conversation that matters to a person.

An aerial view across a container yard with handling machinery between the rows.

Compliance

Compliance that shapes logistics & 3pl deployments

The regimes your organisation operates under, and what each one constrains in a deployment. We design to these from the first architecture diagram, they describe your obligations rather than our credentials, and VSI's own position publishes only once it is substantiated.

Hours-of-service rules
Driver availability is legally constrained. Any scheduling or routing suggestion that ignores it is not merely wrong, it is unusable.
Detention and accessorial terms
Contractual rather than regulatory, but they set what evidence has to be captured and when the clock starts.
Customs and cross-border documentation
Where lanes cross a border, documentation errors stop freight. Validation before departure is worth more than chasing afterwards.
Hazardous materials handling
Certain loads carry documentation and routing constraints that must be enforced rather than advised.

How we work with public-sector and regulated buyers

Success stories

The track record behind the practice

Published engagements from adjacent sectors carry the same disciplines, programme governance, systems integration, workflow automation, that a logistics & 3pl deployment draws on. Every figure publishes under a named attestation.

Browse the case-study library

The first month

What starting looks like

What actually happens, week by week. Note where the design conversations sit, before the build, not after it.

  1. 01Week 1

    Sitting with dispatchers through a full cycle including a bad day

    Sitting with dispatchers through a full cycle including a bad day. The tacit knowledge extracted here is the input nothing else can substitute for.

  2. 02Week 2

    Exception taxonomy and escalation thresholds built from your own history, which exception types, at what age, at what customer impact, go to a person and how fast

    Exception taxonomy and escalation thresholds built from your own history, which exception types, at what age, at what customer impact, go to a person and how fast.

  3. 03Weeks 3-4

    Outbound status on one customer segment, and exception detection running in shadow mode so you can see what it would have caught before it acts

    Outbound status on one customer segment, and exception detection running in shadow mode so you can see what it would have caught before it acts.

  4. 04End of month

    Reviewed against what actually happened: what it caught early, what it missed, what it escalated unnecessarily

    Reviewed against what actually happened: what it caught early, what it missed, what it escalated unnecessarily. Thresholds adjusted before widening.

Next step

A free 20-minute logistics & 3pl assessment

Dispatch, exception handling and customer communication across sites.

No preparation required and nothing to install. Bring the workflow that costs you the most hours; leave with a view of what we would automate first, what it depends on, and what we would not touch.

Book the free assessment

Questions

Asked often enough to answer here

Will customers know they are talking to an agent?
For routine status they are receiving an update rather than having a conversation, and it should be obviously automated, clear, factual, no pretence. Anything that is an exception, a complaint or a negotiation goes to a person. The failure mode worth avoiding is an agent that maintains a fiction of being human through a conversation the customer cares about; freight is a relationship business and that fiction is expensive when discovered.
How do you set escalation thresholds?
From your own history rather than from a default, in week two. We look at what exception types actually became problems, how long they took to become problems, and which customers have the least tolerance, and set thresholds against that. Then we run in shadow mode so you can see what would have been escalated before anything actually is.
What if a receiving facility is new and we have no history?
It routes to a person until the pattern is learned. Facility rules are idiosyncratic and largely unwritten, and confidently guessing at a new facility is how a load sits at a dock. Designing the unknown case to fall back to a human is not a limitation of the approach, it is the correct behaviour.
Does this need us to change our transport management system?
No, and we would advise against combining the two. Integration is against your existing system, and where the data quality in it is the actual constraint we will say so, that is a cheaper problem to fix and fixing it first makes everything downstream work better.
How does this handle drivers who do not speak English?
In their language, on the channel they actually use, which for a lot of the driver population is a messaging app rather than a portal. The substance gets written back into the record in English so the next dispatcher has context. This is one of the more reliably valuable pieces because the alternative today is often a call that is understood approximately.
What happens on a genuinely bad day?
More escalates, which is correct. The system is tuned so that when the exception rate spikes, more goes to people rather than the automation absorbing it silently, because a bad day is precisely when a wrongly-handled exception costs most. That is a deliberate design choice and it is worth knowing that a supplier who promises the opposite is promising something you would not want.

Usually bought with

The delivery underneath

Other sectors

We also deploy in