Works with the tools you already use.
BrokerMate isn't asking you to replace anything. It sits alongside your TMS, your inbox, and your load boards — reading what comes in, doing the repetitive work, and handing clean results to the systems you already run your brokerage on.
We're honest about status: some connections are live, some are in pilot, and some are on the roadmap. If your system isn't listed, tell us — or have it mapped for your brokerage on the customization retainer.
TMS platforms
There are two ways a load gets into your TMS. The BrokerMate Chrome extension types it straight into your TMS screen, in the tab you're already signed in to, and you press Save: no credentials, no API keys. Or the BrokerMate app builds the import file your system already accepts. Either way, BrokerMate never saves anything in your TMS for you, and after that it only reads.
| System | Chrome extension | Import file |
|---|---|---|
| Aljex | Fills new loads and extra stops on Picks/Stops; drafts customer updates from saved changes · Live | Available today |
| LOADPlus | Fills shipper, consignee and rate · Live, in pilot | Available today |
| AscendTMS | Builds the whole load in one press · Live | Available today |
| Turvo | On request | Available today |
| McLeod | On request | Available today |
| Tailwind | On request | Available today |
| Alvys | On request | Available today |
| Revenova | On request | Available today |
| Not sure / not listed | On request | Neutral CSV layout you map once to your own import screen |
"On request" means we map the extension to that TMS for your brokerage on the customization retainer. Import file column layouts are confirmed against each vendor's published import template. Until a format is verified end to end, BrokerMate says so on screen rather than assuming the file will import cleanly.
Don't know what you run?
It happens more than you'd think — a business partner set the system up, or it's something regional that never shows up on a list like this one. Pick Not sure / not listed and BrokerMate builds a neutral CSV instead of guessing at a vendor's layout. You match the headers to your import screen once; most systems let you save that mapping, so every file after the first drops straight in.
Getting your TMS to confirm the format
The columns above are careful guesses until the vendor confirms them, and there's one reliable way to turn a guess into a certainty: ask them. Not us — you. A TMS vendor answers their own paying customer's support ticket; a cold integration enquiry from a software company they've never heard of waits in a queue.
BrokerMate writes that email for you. It's on the export screen, pre-filled with the system you selected, and it asks for two things at once — their published import template, and whether they support a direct connection for a tool you've authorized. The first question gets answered almost every time, and it's the one that clears the warning on your export screen. The second is how direct integrations eventually get built.
One question in that email matters more than the rest: whether API access is included in your current plan or needs an upgrade. It's the detail that decides whether a direct connection is realistic, and it's almost never in the public documentation.
Email is where freight actually happens, so it's where BrokerMate starts — but it never asks for your mailbox. You get a dedicated BrokerMate address and forward freight mail to it, either with one rule in Gmail or Outlook or by hitting forward. Nothing changes for your customers or carriers, who keep writing to the address they always have.
Why forwarding rather than a mailbox connection: BrokerMate never holds your email password, never sees anything you don't forward, and can't reach the rest of your inbox. Turning it off is deleting one rule — not revoking access and hoping.
| System | What the integration does | Status |
|---|---|---|
| Gmail / Google Workspace | Forward freight mail to your BrokerMate address; categorize and extract documents | In development |
| Outlook / Microsoft 365 | Forward freight mail to your BrokerMate address; categorize and extract documents | In development |
Load boards
The Chrome extension posts from the load you scanned: lane, dates, equipment, length, weight and tarps mapped automatically, your Aljex Pro # as the reference, and comments written for carriers only — never your customer's name, the rate or PO numbers. You check the form and press Post.
| System | What the integration does | Status |
|---|---|---|
| DAT One | Fills the Post A Shipment form in one press, or builds DAT's bulk upload file for Post Multiple Shipments | Live |
| Truckstop | Fills the Load Manager quick-post row from a recent load | Live |
Don't see your system?
Tell us what you run. Early access brokerages get direct input into which integrations we build next, and the customization retainer maps the extension to your own TMS or load board. Because BrokerMate also generates a standard import file, you can put it to work on load entry before any deeper integration ships. Reach us at brent@brokermateai.com or book a demo below.