Picture a shipper who has tendered the same Dayton to Atlanta lane every week for a year. They call to book this week's load. Whoever answers asks for the company name, the pickup address, the commodity, the equipment type and the weight. The shipper sighs and answers all of it again.
That is a hypothetical, but you have heard the real version. Intake built for strangers treats regulars like strangers. The regular does not complain. They start calling the broker who remembers them.
This is about shippers who are active right now, not the ones who went quiet. Winning back dormant accounts is a separate follow-up problem.
Decide what counts as a returning shipper
Write a rule down, such as "an account with a tendered load in the last N days." Choose N from how often your shippers actually ship. A weekly lane and a quarterly project shipper should not share one window.
Then decide what the system knows about each account. Keep it small: company and known contacts with their numbers and emails, the assigned rep and a named backup, usual lanes with addresses, usual equipment and standing requirements like liftgate or appointment only, and the date each fact was last confirmed.
Teams skip that last one. An undated fact cannot be trusted next month.
Treat a number match as a hint, not proof
Matching the caller's number to an account is a good way to pull up their lanes. It is a bad way to prove who they are.
The FCC defines spoofing as a caller deliberately falsifying the information sent to your caller ID display, and notes that scammers sometimes spoof a number from a company you already know and trust ([FCC](https://www.fcc.gov/consumers/guides/spoofing-and-caller-id)). The FCC also requires voice service providers to implement STIR/SHAKEN call authentication, which it says gives subscribers "more confidence" that caller ID is accurate ([FCC](https://www.fcc.gov/call-authentication)). More confidence is not certainty. DAT warns that scammers can easily get a number that looks very similar to the one on file for a carrier ([DAT](https://www.dat.com/blog/trucking-scams-how-brokers-and-carriers-can-protect-themselves)).
Split what a match allows into two tiers. A match can greet the caller by company, offer their usual lane, and pre-fill the intake for a human to review.
A match should not, alone, change a delivery address, change where invoices or payments go, release rate history, or reroute a load in motion. Those requests get a callback to the number on the account record, or a human check, however familiar the voice sounds.
Confirm instead of re-asking
Read back what you have and ask for a yes or a correction. "Is this the Dayton to Atlanta lane, 53-foot dry van, picking up at the Hamilton dock?" is a yes or a correction. Asking for each of those from scratch is slower and invites typos.
Sort your intake fields into two groups before you build anything. Confirm from the record what rarely changes: company, billing contact, dock address, usual equipment, standing accessorials, appointment rules. Always ask fresh what changes every shipment: pickup date, weight, piece count, delivery date, and whether this load differs from the usual.
Some fields look stable and are not. Hazmat status should be asked on every shipment, not carried forward from the last one. A shipper whose usual freight is dry goods can tender something different next Tuesday, and a stale "no" is a bad thing to find at pickup. Commodity belongs in the same bucket.
Set an age limit per field. A dock address last confirmed eight months ago gets asked again.
Flag what changed
Confirming makes the exceptions stand out. When an answer differs from the record, the system should not quietly overwrite the old value. It should write down what the record said, what the caller said, and when, then mark the intake as changed.
Changes worth flagging to the rep: different equipment than usual, a new pickup or delivery address on a known lane, weight or piece count well outside the normal range, a new commodity, a new contact placing the order, or a lane the account has not tendered before.
The system should not turn a flagged change into a price. The intake captures the change cleanly, says a rep will follow up, and stops. The default profile on the account changes only when a person updates it.
Route to the assigned rep, with a backup
Every active account needs an owner and a backup in the record. Write the rules out:
- If the rep is available, warm transfer, or offer a callback window the rep has agreed to. - If the rep is out, go to the named backup, not a general queue. - If the caller asks for someone by name, honor it. - If the call is about a load in transit, route to whoever is working that load, who may not be the sales rep.
Do not let the system promise a callback time your team will not keep.
Handle the awkward matches
A few cases break a simple lookup, so decide them in advance.
An unknown number from a known company usually means someone new at the shipper. Confirm the company, treat it as a returning account with a new contact, and flag the contact for the rep to verify.
One number tied to two accounts, such as a shared office or a third-party logistics firm, means you ask which company this shipment is for. Do not guess.
Email works the same way. A free webmail address claiming to be a known shipper gets the caution you would give an unexpected number.
Test it before you trust it
Run test calls before real traffic: a normal repeat load, a changed equipment type, an unknown number from a known company, a number on two accounts, a matched number asking to change the delivery address, and a call while the assigned rep is out.
Then count how often reps correct a pre-filled field. If they fix the same one repeatedly, move it to the always-ask group.
If you want help setting up returning-shipper recognition and rep routing, [book a call with Chosen AI Solutions](https://chosenai.co/book).
Sources
- Federal Communications Commission. [Caller ID Spoofing](https://www.fcc.gov/consumers/guides/spoofing-and-caller-id) - Federal Communications Commission. [Combating Spoofed Robocalls with Caller ID Authentication](https://www.fcc.gov/call-authentication) - DAT. [Trucking scams: how brokers and carriers can protect themselves](https://www.dat.com/blog/trucking-scams-how-brokers-and-carriers-can-protect-themselves)