Dispatcher identity verification

Confirm the human, not just the MC number.

An MC number tells you a carrier exists. It doesn't tell you the person emailing you actually works there. VettaVerify closes that gap: before a load goes out, the carrier's dispatcher confirms a one-time passcode sent to the email FMCSA has on file for that carrier. You get a verified badge and an audit trail you can stand behind.

01 · The gap an MC number leaves

Identity matters more than the number on the packet.

Vetting tools answer “is this a real carrier?” well. The harder question is “is this real person from that carrier?” Three places where the number alone runs out of road:

The MC checks out

Authority is active, insurance is on file, the safety record looks fine. All of it can belong to a real carrier that has nothing to do with the person contacting you.

The contact is unverified

A free email address and a borrowed company name read as legitimate in an inbox preview. Reusing a real carrier’s identity is the core move behind chameleon carriers and double-brokering.

Documents follow trust

Once a rate con leaves your hands, it can be re-posted or tendered onward. The MC number you verified was never the part that needed verifying — the human was.

02 · How verification works

A one-time passcode to the email of record.

Four steps, no captcha and no phone-number challenge. The check rests on the one thing tied to the real carrier: access to the mailbox the federal government has on file.

  1. 01

    Send an identity request

    From the carrier record, request verification before sharing load details. No new portal for the carrier to learn — it arrives as a link.

  2. 02

    Passcode goes to the FMCSA email of record

    The one-time passcode is sent only to the email FMCSA has on file for that carrier — the channel that connects to the actual company, not any address typed into a thread.

  3. 03

    The dispatcher confirms the code

    Receiving and entering the passcode proves the dispatcher can read mail at the carrier’s registered address. That’s the credential an impersonator can’t borrow.

  4. 04

    You get a verified badge and an audit trail

    The record shows a clear verified status with a timestamp, IP, and device. Future reviews — billing, disputes, compliance — read from the same trail.

03 · What lands on the record

A verified badge your whole team can read.

Verification isn't a one-off check buried in someone's inbox. It lands on the carrier record as a status everyone on the team can see, with the evidence attached: when it happened, from where, and on what device.

Because the trail lives with the carrier, it's there later when you need it — reconciling billing, working a dispute, or answering a compliance question. The same record that helped you book the load explains why the load was safe to book.

-- identity verification --

dispatcher
verified
channel
FMCSA email of record
timestamp
07:42 CT
ip
logged
device
fingerprinted
audit trail
retained

04 · Built into rate-con delivery

Identity-verified rate-con delivery is built in — not bolted on.

Verification doesn't live in a separate tool. It's part of how you send the rate con: the document goes to the dispatcher who confirmed the passcode, and the handoff is recorded on the same record. That's the anti-double-broker wedge — the rate con reaches the verified contact, and nobody else.

The result is one continuous path from carrier lookup to a verified dispatcher to a delivered rate con, with the audit trail following the load instead of scattering across inboxes.

Get started

Verify the dispatcher before the load goes out.

Look up any carrier for free. When you're ready to book, send an identity request and let the dispatcher confirm they're actually from that carrier — with the verified badge and audit trail to show for it.