Aljex was built by brokers for brokers, and it still cannot pick up the phone at midnight. The agent answers carriers, runs your check calls, and gets the answers back into the load record.
What it covers for an Aljex shop
Brokers like Aljex because it is quick to work in. That speed disappears the moment a rep is stuck on a call repeating a pickup window, or the check-call list gets pushed to tomorrow because today ran long. A voice agent absorbs the repetitive calls and the entire outbound list so your reps keep doing the part that actually pays: covering freight and selling.
What it handles
Confirms lane, equipment, and windows from the load, captures the MC, and screens before anything reaches your reps.
Works the list on your cadence, captures position, loaded status, and ETA, and writes it back to the load.
Gets the safety questions right first, captures the detail, and escalates to your on-call person immediately.
Calls ahead to confirm dock times and reports back what the facility actually said, not what the rate con assumed.
Runs down the paperwork that is holding up your invoicing without a rep spending an afternoon on it.
Nights and weekends answered by something that can actually look up the load and take real action.
Aljex integration
Descartes Aljex is a cloud TMS that connects to freight tech partners through both EDI and API. We use whichever path your instance supports for each workflow and we tell you which is which up front, so you know exactly where the agent writes automatically and where it hands off to a person.
What we confirm before we build
Not sure what your instance supports?
How it works
We map each workflow to a real, supported path and flag anything that will need a manual handoff.
We build from how your team actually talks to carriers, including what they never say.
After-hours is the usual first step because the risk is low and the payoff is immediate.
Review transcripts, tune, then move more traffic over once you trust what you are hearing.
Where your instance exposes a supported path for that workflow, yes. Where it does not, the agent still handles the call and delivers a structured, timestamped handoff so nothing is lost. We tell you which workflows fall into which bucket before you commit to anything.
No. It holds a real conversation, understands interruptions and corrections, and pulls the actual load record while it talks. A scripted phone tree would fail the first time a driver said something unexpected, which on a breakdown call is every time.
It asks the safety questions first, confirms whether anyone is hurt, and escalates to your on-call person immediately. Those calls are defined as never-handle-alone during setup and we do not compromise on that.
No. You keep your numbers and your provider. We take the calls you forward, and you can stop forwarding at any time.
It depends on your mix. Check calls, appointment confirmations, POD chasing, and routine load questions are highly automatable. Rate negotiation and relationship calls should stay with your reps, and we design for that split rather than pretending otherwise.
About a week for the first workflow once we have confirmed the integration path. After-hours coverage is usually live first because it needs the least approval.
The main page: what a voice agent covers across carrier sales, check calls, and after-hours dispatch.
Read moreHow outbound check calls run themselves and land back in your TMS as timestamped status updates.
Read moreAnswer every is-this-load-still-available call, qualify the carrier, and hand off warm covers.
Read moreAPIs, webhooks, MCP, and what we do when your TMS does not expose the endpoint we need.
Read moreBook 15 minutes. Tell us what happened the last time a driver broke down at 2am, and we will show you how the agent would have handled it.
Part of our voice AI for freight work, alongside AI voice agents for every other kind of business.