AI for Aljex. Triaged along the keel.
Aljex runs your brokerage. Keelway runs on top of it — reading every carrier reply to an Aljex-posted load, extracting the rate, scoring trust against FMCSA, and writing the accepted carrier and rate back into Aljex when you pick.
Why Aljex brokerages need an AI overlay
Aljex, under the Descartes umbrella, is a widely deployed TMS for mid-market freight brokerages. It ships strong carrier management, dispatch, and EDI modules, with deep integration into the Descartes visibility + compliance suite.
What Aljex does not solve — and does not try to — is the inbound carrier email stream. When dispatch posts a load to the boards, 30–50 carriers respond to the broker's inbox within two hours. That inbound triage is still a manual job in most brokerages on Aljex. Keelway is the overlay that closes the gap.
What Keelway adds to Aljex
Every carrier reply, triaged in seconds
FMCSA trust score on every reply
Top five along the keel
Accepted carrier flows into Aljex
How this works alongside Descartes visibility tools
If your brokerage layers Aljex with Descartes MacroPoint (shipment visibility) or Descartes GLN (carrier compliance), Keelway is orthogonal — we operate on the email-triage layer, not the in-transit visibility or compliance layers. Every inbound carrier Keelway scores can also be checked against whatever additional compliance rules Descartes is already enforcing.
What a week on Aljex + Keelway looks like
A mid-sized brokerage on Aljex typically posts 250–600 loads a week. Each pulls 30–50 replies. Without Keelway, 20–30 minutes per load goes to reading threads and cross-checking authority. With Keelway:
- Every reply is already triaged by the time anyone opens the thread.
- Red-flag carriers get caught on the ranked list before booking — double-broker domains, MCs without operating authority, insurance mismatches.
- Dispatch never has to clean up a carrier record; the one Keelway wrote back to Aljex is correct by construction.
Deployment alongside Aljex (under 2 weeks)
- Day 1–2. Reply address issued + Aljex API credentials exchanged. Keelway starts reading replies to loads posted today.
- Day 3–5. Ranking weights calibrated from your last 30 days of accepted quotes.
- Day 6–8. Aljex write-back live. First accepted carriers flow back into the Aljex load record automatically.
- Day 9–12. Flagged suspected double-broker emails get labeled; Keelway's fraud detector learns the shape of your book.
- Day 13+. Steady state.
For the full capability breakdown independent of TMS, see Carrier Email Automation. If your shop runs on Tai or McLeod instead, we have dedicated pages for each: Tai TMS · McLeod TMS.
Frequently asked questions
What is Aljex?+
How does Keelway integrate with Aljex?+
Does Keelway replace Aljex's carrier management module?+
We're on Descartes MacroPoint / Descartes Aljex Enterprise — will Keelway work?+
Can Keelway catch double-brokering before we book?+
What does Keelway cost on top of Aljex / Descartes?+
