Works with the tools you already use.
BrokerMate isn't asking you to replace anything. It's built to sit 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 in active development with early access brokerages, and we're honest about status: some connections are being built now, and some are on the roadmap. If your system isn't listed, tell us — early access members directly shape the integration order.
TMS platforms
BrokerMate writes to your TMS once, at load creation, using the import format your system already accepts — no credentials, no API keys, nothing to open up. Everything after that is read-only: status flows back out to drive tracking and updates, and BrokerMate never writes to the load again.
| System | What BrokerMate does | Status |
|---|---|---|
| Aljex | Generates the load import file; reads status back | Import file today · status sync planned |
| Turvo | Generates the load import file; reads status back | Import file today · status sync planned |
| McLeod | Generates the load import file; reads status back | Import file today · status sync planned |
| AscendTMS | Generates the load import file; reads status back | Import file today · status sync planned |
| Tailwind | Generates the load import file; reads status back | Import file today · status sync planned |
| LOAD Plus | Generates the load import file; reads status back | Import file today · status sync planned |
| Alvys | Generates the load import file; reads status back | Import file today · status sync planned |
| Revenova | Generates the load import file; reads status back | Import file today · status sync planned |
| Not sure / not listed | Neutral CSV layout you map once to your own import screen | Available today |
Column layouts are being 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
| System | What the integration does | Status |
|---|---|---|
| DAT | Post reviewed loads directly from extracted PDF or TMS data — lane, equipment, dates, and rate visibility mapped automatically | Roadmap |
| Truckstop | Post reviewed loads directly from extracted PDF or TMS data — lane, equipment, dates, and rate visibility mapped automatically | Roadmap |
Don't see your system?
Tell us what you run. Early access brokerages get direct input into which integrations we build next — and because BrokerMate generates a standard import file rather than requiring a native connection, 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.