What a custom agent looks like inside a freight brokerage or 3PL — the ten roles in your language, and what each plugs into in a business running a broker TMS alongside load boards and carrier vetting.
last reviewed
A brokerage's product is coverage and information, and both are produced by people on the phone. Margin per load is thin enough that every minute of manual handling matters, and the work itself is repetitive in a very specific way: quoting from history, covering from a carrier list, checking a carrier is legal and insured, then answering "where is my truck" until delivery. All four repeat on every load.
The honest version of "does it integrate with my software." These are the systems this industry actually runs on, and what each one means for a build.
The systems of record for loads, carriers, quoting, settlements and customer billing, ranging from established enterprise platforms to modern integration-friendly ones.
DAT and Truckstop, where capacity is found and where market rate data lives, both accessible programmatically.
RMIS, Carrier Assure, Highway and similar, verifying authority, insurance and fraud risk — a check that is increasingly load-by-load rather than onboarding-only.
Macropoint, Project44 or direct ELD connections, producing the location data customers now expect without asking.
Where shipper tenders arrive with short acceptance windows and specific acknowledgment requirements.
Rate confirmations and proofs of delivery, which gate both carrier payment and customer invoicing.
Quick pay, factoring companies and payment terms, where errors create carrier relationships you cannot use again.
Each of these is a real build, not a feature of a product you already pay for. Follow one through to see how it works in general.
Nothing you are owed gets dropped.
Whatever arrives, in whatever format, becomes a clean record.
Writes the recurring document from your own past work.
Knows what expires, renews or comes due — and says so first.
Answers from your own records, not from the internet.
The conversation becomes the record, without anyone typing it up.
Assembles the recurring report from systems that do not talk.
Matches two sets of records and queues only the exceptions.
Two systems that do not talk, now talking.
Applies your rules, escalates only what needs judgment.
If that is a job in your business, the next step is half an hour on a call. Bring whatever you know about the volume — how many a month, who owns it now, which systems it touches. That is enough to scope it properly and quote it flat before anything starts.
Everything in this library is built to order rather than bought off a shelf — and whatever I build, I host and maintain. The rest of the library is here.