Check calls your TMS starts itself
Dograh is the self-hostable voice agent platform with an open-source workflow builder. Automate carrier check calls first, keep the rate limits in your TMS, and keep every recording of a rate conversation on your own servers.
Check calls first, invoices last
Call only when tracking has a gap
API Triggeryour TMS decides, the agent dials
When a geofence event is missing, the TMS starts the call with the load details in the initial context. The agent asks where the truck is and when it arrives.
→ A GPS conflict is flagged for a person, never overwritten
Relay the rate, never decide it
HTTP API toolyour TMS answers inside or outside
A carrier names a rate. The agent sends it to your TMS, which answers inside or outside your limits. Outside means a broker calls back.
→ The AI never holds the ceiling, so nobody can talk it past the limit
Read payment status, hand off disputes
VerificationMC number or account digits first
The agent confirms the carrier, reads the invoice status from your accounting system and sends any dispute to a person.
→ Add this call last, once the first two are running
Five checks before the first carrier call
- Consent captured at onboardingMost carriers answer on a mobile, so capture consent in the onboarding paperwork.
- Trigger wired to the geofence gapThe TMS fires the production URL only when a tracking event is missing, never on a timer.
- Carrier verified before any load detailThe agent asks for the MC number or the last digits of the account on file.
- Rate check endpoint testedYour TMS returns inside or outside for a test rate before the agent ever quotes one.
- Transfer tested on a real callTransfer Call runs on Twilio numbers and passes no summary, so the write-back comes first.
Rate conversations stay in the brokerage
Recordings on your servers
Every load booking call is a rate conversation. Self-hosted Dograh keeps the recordings and transcripts under your retention rules.
No enterprise minimum
Self-host the BSD-2 code with no per-minute platform fee. Mid-sized desks get the same calls the largest brokers buy.
Rules live in your TMS
The agent picks the next step from your system's answer. Money decisions are checked by your software, not by a prompt.
Fewer calls for carriers
The agent calls once per gap and writes the answer where dispatch can see it, so fewer people phone the same driver about the same load.
What you get below the enterprise tier
| Dograh | closed freight voice AI vendors | |
|---|---|---|
| Open-source code you can read before you sign | ✓ | ✕ |
| Self-host without an enterprise contract | ✓ | ✕ |
| No per-minute platform fee when self-hosted | ✓ | ✕ |
| Published pricing for the hosted option | ✓ | ✕ |
The freight calls, one post each
Which freight call should we automate first?+×
Carrier check calls. They are structured, high volume, and your TMS already knows when one is needed.
Can the agent negotiate rates?+×
No. It sends the offered rate to your TMS through an HTTP API tool and relays inside or outside. Anything else goes to a broker.
What if the carrier's answer disagrees with the GPS?+×
The agent records both and flags the load for a dispatcher. It never picks a winner or overwrites the GPS.
Do check calls to drivers need consent?+×
Calls to a mobile generally need prior express consent. Capture it at carrier onboarding and confirm your position with counsel.
Will this add calls to a carrier's day?+×
Not if the agent calls only when a tracking event is missing and writes the answer where your team can see it.
Can the call be handed to a broker?+×
Yes, with Transfer Call on Twilio numbers. The agent writes what it heard to the TMS before transferring.
Start with one lane and one dispatcher reading the outcomes.
Self-host in one command, or start on Dograh Cloud.
$ curl … start_docker.sh && ./start_docker.sh