Dispatcher Scam Red Flags

How this comes up in practice

A load moves, the receiver confirms delivery, and two weeks later the carrier calls asking why payment went to a dispatch company they severed ties with three months ago. The rate confirmation named the right carrier; the MC number checked out in SAFER; the insurance certificate matched the carrier's registered entity. The dispatcher had documents from a prior arrangement with the carrier — a packet that was never formally revoked because the carrier didn't know there was anything to revoke. The broker had verified the carrier's authority and insurance, both of which were legitimate. What no one verified was whether this specific dispatcher was still authorized to act for this specific carrier on this load. That verification is a call to the carrier's main management line — reached through SAFER, not through the dispatcher — asking whether the current load was dispatched through them and whether the named dispatch company still has authority to collect on their behalf. The carrier's answer would have been no. The check costs a few minutes; the payment dispute cost considerably more.

Why dispatcher authorization is a separate question from carrier authorization

A dispatcher who represents themselves as acting for a carrier doesn't automatically have the carrier's authorization to do so. This distinction matters because dispatcher fraud often involves someone who legitimately markets dispatch services to carriers, obtains their credentials and documents, and then uses those credentials to book loads independently — routing revenue away from the carrier while leaving them to address the fallout from loads they never authorized. For adjacent verification steps, compare this with Dispatch Service vs Carrier Identity Risk, Carrier Identity Theft Warning Signs, and Load Board Scam Red Flags.

For brokers and shippers, the operative question isn't whether dispatch services are legitimate in general — many are — but whether this specific dispatcher is authorized by the carrier for this specific load. The authorization question is answered by reaching carrier management directly, not through the dispatcher. A dispatcher who encourages contact with carrier management is acting within a legitimate arrangement; one who discourages it isn't.

FMCSA registers motor carriers and brokers but doesn't separately license dispatch services. There's no FMCSA lookup for dispatcher authorization. The verification that exists is a call to the carrier's SAFER-listed number, asking whether the named dispatcher is authorized and whether this load was dispatched through them. That call is the only check that confirms authorization rather than just presence.

Verifying dispatcher authorization independently from the carrier

Most dispatchers working for carriers operate legitimately. The scam variant typically surfaces when someone markets dispatch services to carriers, obtains access to their documents and authority, and then uses those credentials to book loads under the carrier's identity — keeping the proceeds and leaving the carrier to address the fallout.

For a broker or shipper, the practical risk is in treating a dispatcher's communication as equivalent to the carrier's authorization. The carrier's management is the entity that needs to be independently confirmed when any question arises — not the dispatcher's account.

Records that confirm dispatcher authority for a specific carrier and load

Load board review treats the post as a lead that still needs identity verification. In this guide, that starts with dispatcher authority, carrier permission, document access, and contact verification.

Capture the account, posting details, rate, lane, domain, and packet request before the post is edited or removed. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

What to preserve when a dispatcher is the sole contact for a load

For dispatcher scam red flags, the useful record is usually the one that shows where dispatcher authority, carrier permission, document access, and contact verification first entered the file.

That record is stronger when it sits beside the dated lookup, the original message, and a note from the posting account owner or independently confirmed company contact. It is weaker when it has been renamed, cropped, forwarded without headers, or separated from the transaction timeline.

Questions that confirm carrier management dispatched this specific load

Hold the booking, dispatch, pickup, or payment decision when the file depends on a new contact path, revised document, missing official record, or mismatch that no one has explained.

The pause should be narrow and written down: the field that does not line up, the source used to check it, and the person or channel that must answer before the work continues.

What a dispatcher's knowledge of load details doesn't establish about authority

Save screenshots early because load board details and message threads can disappear after the other party changes course. In this guide, that starts with dispatcher authority, carrier permission, document access, and contact verification.

The useful file shows how the posting identity connected, or failed to connect, to the broker or carrier records behind it. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When a dispatcher-only thread requires a SAFER callback before proceeding

Load board questions should verify the party behind the account before documents or pickup details are shared. In this guide, that starts with dispatcher authority, carrier permission, document access, and contact verification.

A strong answer comes through a known company contact, not through the same profile that created the concern. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Further context on dispatcher scam patterns

A marketplace profile can be compromised or reused. Treat reputation signals as context, not identity proof. In this guide, that starts with dispatcher authority, carrier permission, document access, and contact verification.

When a posting feels unusually urgent or generous, slow down enough to preserve the evidence and verify the entity. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When the posting warrants a report

Escalate when the posting identity cannot be confirmed or when the account appears to be part of spoofing, phishing, or identity misuse. In this guide, that starts with dispatcher authority, carrier permission, document access, and contact verification.

Use platform reporting, known company contacts, IC3, FTC, or FMCSA resources according to the facts and the records you saved. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Source Notes

FAQ