Keep every handoff moving.
One place to coordinate incidents across the fleets you serve: clear handoffs, complete job tickets, and a record of who was told what and when.
Bellwether Dispatch is software for dispatch companies. Bellwether is not a dispatch service.
Many fleets, many systems, one shift
A dispatch company works for more than one fleet, and every fleet brings its own cameras, contacts and rules.
Every client is different
Each fleet has its own vendors, contacts and requirements, and it is easy to lose track of which applies to which call.
Handoffs depend on memory
Under pressure, a call carries a location and a guess. The next person decides with half the story.
The record starts late
Who was called, when and on whose behalf is not written down in one place, so billing and reviews start from zero.
From the first signal to a closed record
Intake
An event arrives from a client fleet's cameras, ELDs or telematics, tied to that fleet.
Verify
Review the vendor's footage and classification before you act.
Notify
Work from a call script with the facts in order, and log who was called.
Assign
Choose a provider from your own directory who can do the job.
Close out
Track arrival and resolution, and keep a complete record for the client.
Give the provider the full picture
One link, no login, readable on a phone in the cab of a wrecker.
What happened
- Vendor camera frames before and after the event
- Fault codes and likely fixes for roadside service
- The owner's request and who has been called
What they are moving
- Truck, trailer and weight details when known
- Load and hazmat information entered by your team
- Driver and contact details
Where it is
- Position, with state and county
- Distance off the road and terrain, as reported by the driver
- Access notes from your dispatcher
Match the provider to the job and the road
- Hazmat capability. If the load is hazmat, providers in your directory are checked for certification. If one cannot handle it, the ticket says hazmat is required.
- State clearance rules. Some roads need certified recovery vendors. For example, Florida's RISC program covers incidents that close an interstate. Bellwether flags the requirement and prefers qualified providers.
- On behalf of the fleet. Tickets and call scripts state that the provider is sent at the fleet owner's request.
- Your providers only. Bellwether never invents a provider. You decide who is in your directory.
Rules vary by state and municipality. We add programs with pilot partners, and every rule is shown so a person can confirm it.
Each client's data stays theirs
A client fleet shares access with your company, for the data and the time it chooses, and can end it at any time. Your team sees only the fleets that have granted access.
- Separate by design: one client's incidents are never visible to another.
- Roles for your team: owners and admins, dispatchers who work incidents, and read-only viewers.
- An activity log of sign-ins, invitations and sharing.
Coordinate work across fleet relationships
Bring each fleet you serve into one console without mixing their records, and keep communication and handoffs clear for everyone on the call.
Questions dispatch companies ask
Are you a dispatch service?
No. Bellwether Dispatch is software that dispatch companies use. We do not dispatch on your behalf or take your clients' calls.
Does it send the messages and call the providers?
Today it prepares the call script and the job ticket and logs the result. Sending messages, and connections to providers and agencies, are simulated in the demo and are part of what pilots will shape.
Where do the providers come from?
From your own directory. You add or import the companies you work with, and Bellwether uses only those.
How do client fleets connect?
Each fleet's cameras, ELDs or telematics feed Bellwether through its own API key, and the fleet shares access with your company.
Is this live?
There is a working demo on synthetic data. We are connecting live fleets through pilots now.
See a handoff from first signal to closed record
We will take one incident from intake to a provider's job ticket.
We'll set up a short walkthrough on a working demo. It runs on synthetic data, so nothing of yours is needed to start.