Someone Is Using Your Brokerage’s Name: Build a Response Plan

Someone may be using your brokerage's name. Your response now has two tracks: help resolve the reported shipment and protect the company identity being misused.

This brokerage impersonation response plan focuses on the second track. It is a practical recommendation for organizing reports, checking your systems, and giving partners a reliable way to reach you. Tailor it with your operations, IT, legal, and insurance teams.

Centralize brokerage impersonation response reports

Choose a monitored inbox or existing support channel for suspected impersonation. Assign an owner and a backup. The person who receives the first complaint should know where to send it without guessing.

Collect a small, consistent set of details: the reporter's company and contact information, the disputed load reference, the communication they received, and whether freight or money has already moved.

Ask reporters to preserve the original message and document. Use an approved secure method for collecting evidence. Do not ask them to post driver licenses, customer records, or shipment details in public comments.

A simple intake process helps the team see whether several complaints involve the same sender or document template.

Check whether your systems are involved

Impersonation can involve a lookalike address, stolen documents, or access to a real business account. Do not announce a data breach until the facts support that conclusion. Do not assume your systems are safe just because the first email came from another domain.

Have qualified IT staff review the accounts and services relevant to the report. Give them the original messages, dates, and employee names being used. Ask them to preserve evidence and follow the organization's account-containment process where needed.

The FBI's business email compromise guidance describes both spoofed identities and compromised accounts. It recommends multifactor authentication. Your security team should evaluate how those risks apply to the actual systems involved.

Compare the claimed work with your records

Create a list of reported loads and check each one against your brokerage's systems. Record whether your company issued the tender, whether it recognizes the customer, and which employee was assigned.

Mark uncertain cases for investigation. Avoid replying “fake” simply because one dispatcher cannot find a record during a busy shift.

If an affected load is real but the contact details changed, route it to the operational incident lead. If your company never authorized the load, prepare a factual statement that the responsible reviewer can approve.

Keep that statement narrow. “We have not located an authorized tender for this reference” may be more accurate than a broad claim about every person involved.

Give partners a stable verification route

Use company channels your customers and carriers already know. Publish a short notice on your official website when appropriate, and reach affected partners through their established contacts.

Explain which communication pattern is in question. Identify the official domain and verification route. Say what the recipient should do if they received a similar message.

Avoid linking readers directly to suspected phishing pages. Do not include private driver or customer information in a public warning. Have the appropriate team review notices that identify outside organizations or individuals.

FMCSA's identity-theft guidance recommends notifying relevant business partners and using company communications to warn customers. Keep each notice specific to what your investigation has established.

Contact platforms through their official support channels

Report suspected misuse to the relevant load board, email provider, domain service, or other platform. Explain which company identity is affected and provide the evidence requested through a verified channel.

Track each report, its case number, and the next expected step. A submitted report does not mean the false account or website has been removed. Verify the result before telling partners the problem is resolved.

Where a crime or theft is suspected, follow your reporting plan. The FBI cargo-theft advisory identifies unauthorized shipments made in a company's name as a warning sign. Preserve the details that connect the reported activity to your company.

Keep legitimate operations understandable

During an incident, customers may hesitate to trust even genuine updates. Give account owners a consistent explanation and a verified route for callbacks. Avoid creating several emergency phone numbers or new email addresses that add more uncertainty.

CargoGuard brings shipment tracking and records into one workflow. Clear shipment records can support operational reviews while your team investigates the misuse of its name.

For genuine loads, keep driver and vehicle checks tied to the approved assignment. An impersonation incident should not lead the team to skip normal checks to catch up.

Close the incident with evidence

Set specific closure criteria: affected accounts reviewed, partner warnings delivered where needed, disputed loads assigned an owner, and platform reports resolved or actively tracked. Record any remaining uncertainty.

Then update the response plan using what your team learned. Book a CargoGuard demo to explore how shipment evidence can support the operational side of that plan.