Ask anyone who has worked the phones at a brokerage what the Friday calls sound like. A lot of them aren't shippers asking for rates. They're carriers asking one question: "Where's my money?"
That call is fair. A small carrier hauled your load, sent the paperwork, and has fuel and payroll to cover. But when every payment question lands on a broker's desk, your quoting and covering time goes to looking up invoices. And when nobody picks up, the carrier calls again, then emails, then wonders whether to haul for you next week.
This post is about pulling carrier payment status calls into a clean intake flow. It doesn't pay anyone faster or automate accounting. It makes sure the question is captured completely the first time and lands with the person who can answer it.
Why these calls pile up on the wrong desk
Most carriers call the number they already have. Usually that's the dispatcher or the broker who booked the load, because that's who they talked to. Accounting may have its own line, but the carrier's phone history says "Mike at the brokerage," so Mike gets the call.
Mike doesn't have the answer either. He has to ask: which load? which invoice? when did you send the POD? did you pick quick pay? Then he walks it over to accounting, or forwards an email, and promises a callback he might forget during a busy afternoon.
Intake could have asked every one of those questions before a person touched the call.
What intake should collect on a payment status call
The goal is a ticket accounting can act on without calling the carrier back to ask the basics. A reasonable minimum:
- Carrier company name and MC or DOT number - Caller name, role (owner, dispatcher, factoring company), and best callback number or email - Load number, or pickup date plus origin and destination if they don't have it - Invoice number and the date they sent it, if they know - Whether they sent the signed POD and how (email, portal, app) - Whether they selected a quick pay option for this load, if your brokerage offers one - Whether payment goes to the carrier directly or to a factoring company - What they're asking: status, a short pay, a missing payment, or a remittance detail
That last field matters. "Has it been paid?" and "You paid me $150 less than the rate con" are different tickets. The second is a dispute and should go to a person with authority, not to a status queue.
What the AI receptionist should not do
Here is where brokerages get nervous, and they should. Payment calls touch money and remit-to details, which is exactly what fraudsters like to change. So the rules need to be tight.
An AI receptionist on these calls should not:
- Promise a pay date that isn't already confirmed in your system - Read out bank details, account numbers, or full remittance records - Accept a change to where payment goes. "We switched factoring companies, send it here now" gets routed to a person who verifies it through your normal process, every time - Agree that a short pay was wrong or right - Approve or switch a load to quick pay on the phone
If your accounting system can expose a simple status (received, approved, paid on a date), intake can read that back to a caller you've identified. If it can't, the honest answer is "I've logged this with accounting and here's when they'll get back to you." Pick a callback window your team can actually hit, and write it into the script.
Carriers have a right to the record
Under federal rules for brokers, 49 CFR 371.3, a broker keeps a record of each brokered transaction, and "each party to a brokered transaction has the right to review the record of the transaction." Carriers know this, and some will cite it when they think they've been short paid.
Your receptionist shouldn't email records on request. A request to review the transaction record is formal, not a status check, so tag it and route it to whoever handles those in your office. Logging it cleanly on the first call is better than having a frustrated carrier ask three times.
An example flow
This is a made-up example to show the routing, not a real customer.
A carrier owner calls the main line at 4:40 PM on a Thursday. The AI receptionist asks whether they're calling about a load, a quote, or a payment. They say payment. It collects the MC number, load number, invoice date, and confirms they emailed the POD the day after delivery. They chose standard terms, not quick pay. They're asking for a status, not disputing an amount.
The ticket lands in the accounting queue with all of that attached and a note that the caller wants an email back. The broker who booked the load sees a copy but doesn't have to do anything. Accounting replies the next morning.
Now change one detail. The caller says, "Also, we're with a new factoring company, please update the remit-to." Intake doesn't touch it. It flags the ticket as a remit-to change request, tells the caller a team member will verify it through the brokerage's standard process, and routes it to the person who owns that check.
Why bother, if carriers aren't the ones paying you
Because carriers are your capacity. A carrier who spends twenty minutes chasing a payment answer is a carrier who may not pick up your load next time you're short a truck.
When Harvard Business Review audited 2,241 U.S. companies on how fast they answered a web lead, 37% responded within an hour, 23% never responded at all, and the average among those who did reply within 30 days was 42 hours. That study was about sales leads, not carriers. But the pattern is familiar to anyone in a brokerage: the inbound request sits because nobody owns it. Clean intake gives it an owner.
And keeping relationships you already have is cheaper than finding new ones. HBR's Amy Gallo puts acquiring a new customer at five to 25 times more expensive than retaining an existing one, depending on the study and industry. Carriers aren't customers in the billing sense, but replacing a reliable one you've lost is its own expense in time and risk.
Where to start
1. Pull a week of inbound calls and count how many were carrier payment questions. Guess low, then check. 2. Write the intake fields above into your phone flow and your email triage. 3. Decide who owns payment status, who owns disputes, and who owns remit-to changes. Three names, written down. 4. Write the "do not" list into the receptionist's rules before it takes a single call. 5. Set a callback window you can keep, and track whether you keep it.
None of this requires changing how you pay carriers. It just takes payment questions off your brokers' desks and gets them to someone who can answer.
If you want help setting up AI intake that routes carrier payment calls, shipper quotes and other inbound calls to the right desk, [book a call with Chosen](https://chosenai.co/book).
Sources
- eCFR, 49 CFR 371.3, Records to be kept by brokers: https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-371/subpart-A/section-371.3 - Harvard Business Review, "The Short Life of Online Sales Leads" (2011): https://hbr.org/2011/03/the-short-life-of-online-sales-leads - Harvard Business Review, Amy Gallo, "The Value of Keeping the Right Customers" (2014): https://hbr.org/2014/10/the-value-of-keeping-the-right-customers