Shared Carrier Names, Phones and Addresses: What to Check

Two carrier records that share a name, phone number or address are candidates for a relationship check. The overlap does not establish common ownership, shared purchasing authority, fraud or a single operating fleet. Keep each USDOT entity intact and record the specific connection between each pair, including what remains unknown.

This resource answers: What should a broker, shipper or fleet-service researcher do when several DOT entities share contact details? The useful output is a set of supported relationships and assigned questions, not a merged company record or an accusation.

Sources reviewed October 2, 2026. By John Hauler, USDOTData's editorial persona. The workflow below is independent editorial analysis, not an FMCSA determination.

Start with separate entities and named relationships

FMCSA's guidance on USDOT numbers and business changes explains that numbers are assigned to particular persons or entities and are not transferable. A shared office or familiar trade name does not replace that identifier.

First resolve the records using the legal-name and DBA matching guide. This article starts after that step: you have two or more different USDOT records, and a repeated field connects them.

Keep one entity record per resolved USDOT number. Add a separate relationship entry identifying:

• The two entities being compared.
• The exact field shared and the dates observed.
• The possible relationship, such as shared administration or common purchasing.
• The evidence supporting that specific relationship.
• The decision that depends on resolving it.

“Same phone observed” is a reproducible statement. “Same owner” is a different claim. “One person can purchase for both fleets” is a third claim. Store them separately even when you eventually establish all three.

Compare the same field, including its missing details

FMCSA's MCS-150 instructions distinguish legal business name, DBA, principal business address, mailing address and principal business telephone. The mailing address is for correspondence; the physical address concerns the business's operations and safety records. Do not treat matching text in different address fields as an identical observation.

For each type of overlap, narrow the question:

• Similar names: are the complete legal names the same, or do they only share a brand word? Preserve entity suffixes and geographic terms. A common word is a search clue, not ownership evidence.
• Same phone: did the complete number match, including country code and any available extension? Record whether the source identifies a business line or another contact type. Reaching a switchboard does not establish who can bind each entity to a purchase.
• Same address: are street, unit, city and postal code present? A missing suite is unknown, not proof of the same office. Distinguish principal address from mailing address on both records.

Keep raw values beside any normalized comparison values. Removing punctuation can make a phone comparison easier; removing a suite or company suffix can erase a meaningful difference.

Also compare time. An address displayed for Entity A today and an address from Entity B's undated export establish a cross-source overlap with uncertain timing. They do not establish that the businesses occupied the address together. For changes within one entity, use the address and contact change workflow.

Do not extend one connection through a third company

Suppose Entity A shares a phone with Entity B. Entity B shares a mailing address with Entity C. Those are two observations involving different fields. They do not establish a relationship between A and C.

This matters when a spreadsheet, sales system or analyst creates one group from every connected record. Such a group may be useful as a research queue, but its members have not all been shown to share ownership, operations or purchasing. Label the group by its purpose: “records needing relationship review.”

Require evidence for each proposed connection. If A and B are confirmed to use the same dispatcher, that confirms a dispatch arrangement within its documented scope. It does not establish that B owns A, that C uses the dispatcher, or that a dispatcher can approve software purchases for either carrier.

Do not count repeated copies as independent corroboration. Two directories displaying the same underlying source can repeat the same stale value. Record the originating source where known. More appearances of a phone number do not automatically create stronger ownership evidence.

Ask a question that can change the decision

Possible explanations include a shared office, a service provider, related companies, stale records or an incorrect entry. Treat each as a hypothesis until supported. Investigate only the relationship relevant to the task.

For brokers and shippers, identify the legal entity performing the proposed movement. Keep its applicable authority, insurance, equipment and transaction checks attached to that entity. An account relationship does not transfer another entity's approval. Preserve the result in a carrier-verification evidence record.

For fleet-service sellers, distinguish the customer group from the entities and sites in scope. Ask who owns the particular maintenance, insurance, equipment or software decision. A common administrator may coordinate calls without controlling budgets. Record a need only when a business representative confirms the problem, scope and relevant next step; shared contact details establish none of those.

For an unresolved transaction mismatch, use an independently established verification route. FMCSA's fraud-prevention guidance recommends comparing supplied telephone numbers with SAFER and discussing the load through the posted number when they differ. It also warns that employee identities and documents can be misused. A callback contributes evidence; it is not a guarantee, especially when the contact record itself is disputed.

An adverse finding about one carrier must remain attached to that carrier and its source. A shared address alone does not justify assigning the finding to a neighbor or publishing a claim that both participated in wrongdoing. Equally, a familiar affiliated name cannot clear an unresolved discrepancy in the entity you are actually engaging.

Worked example: three entities, two observations, one scoped confirmation

Hypothetical example. A, B and C are fictional worksheet labels, not real USDOT numbers or companies. A fleet-software researcher has independently resolved three different carrier records:

1. A and B display the same business telephone number when checked on October 2.
2. B and C display the same mailing address, but C's evidence is an export dated July 15 with no displayed source-record date.
3. No direct relationship evidence connects A and C.

The researcher retains three entity records and creates two relationship entries. The A–B entry asks whether there is shared administration or software purchasing. The B–C entry asks whether the mailing overlap is current and what it represents. The researcher creates no A–C relationship claim.

Through an independently established business contact, A and B confirm that an administrative desk handles calls for both. They identify separate software decision owners. That evidence supports shared call handling, with its confirmation date. It does not establish common ownership or a joint software project.

The outcome is specific:

• Observed facts: two pairwise field overlaps, with different evidence dates.
• Confirmed relationship: A and B share call handling; purchasing responsibility remains separate as confirmed in the example.
• Fit hypothesis: either entity might benefit from the researcher's software, but its actual workflow must be assessed separately.
• Confirmed buying need: none. Neither decision owner has identified a problem or requested an evaluation.
• Open question: the B–C mailing relationship remains unexplained; it cannot enlarge the A–B confirmation.

The team may coordinate account research to avoid redundant internal effort. It should not merge three fleet counts into an addressable customer total or mark three entities as qualified opportunities. Even where a genuine group relationship is established, an aggregate needs compatible dates, definitions and checks for overlapping assets before it describes a distinct fleet.

Copyable pair-by-pair review worksheet

Use one block for each proposed relationship. Short fields work in an ordinary note or spreadsheet; no special relationship software is required.

Entity A / USDOT identifier:
Entity B / USDOT identifier:
Shared field and complete raw values:
Normalization applied / missing components:
Source A / record date / observation time:
Source B / record date / observation time:
Originating source independence: known / unknown
Observed overlap:
Relationship hypothesis:
Evidence confirming or contradicting that hypothesis:
Confirmed relationship and exact scope:
Not established:
Decision affected / next check / responsible reviewer:
Review trigger / disposition:

Before using the relationship, check that:

• Both entities retain their own identifiers and source records.
• The two fields have compatible definitions and usable dates.
• Shared administration, ownership and buying authority remain separate claims.
• No connection has been extended through another entity without evidence.
• No safety, insurance or approval result has been inherited from a neighbor.
• The next action answers a specific unresolved business or transaction question.

Close an inquiry when its useful question is answered, even if unrelated ownership questions remain unknown. Keep a supported explanation and a material contradiction visible together rather than forcing every relationship into “safe” or “suspicious.”

Frequently asked questions

Do two DOT numbers with the same phone belong to one owner?

The shared number alone cannot establish ownership. Preserve the two carrier records, identify the source and date of the phone match, and seek evidence specifically addressing ownership only if that question matters to your decision.

Can a common mailing address identify the maintenance yard?

No. A correspondence address does not establish where vehicles are maintained. Confirm the service location for the relevant entity and vehicles before using the overlap to qualify a local repair prospect.

If A is related to B and B to C, can I group all three?

You may place them in a clearly labeled research queue. Do not represent them as one owner, fleet or purchasing account without evidence for the relationship you are claiming. The A–B and B–C connections may have entirely different meanings.

Does the same detail in several databases confirm the relationship?

It confirms that the detail appears in those sources when checked. Determine whether they copied the same underlying record. Repeated data can support locating an observation, but cannot by itself turn an unexplained overlap into an ownership finding.

Should one entity's insurance or safety result apply to connected carriers?

Do not transfer it on the basis of shared details. Review each entity's relevant evidence and the actual scope of any document. If a policy or other record expressly covers multiple entities, examine that documented scope rather than inferring coverage from an address.

What should a CRM say before the relationship is confirmed?

Use a narrow statement such as “shared business phone observed; relationship unconfirmed,” with the two identifiers and date. Avoid a blanket “verified group” label. The guide to verified trucking-lead claims explains how to attach each completed check to the claim it actually supports.

Start with one pair whose relationship would change a current decision. Complete the worksheet, retain both entity records and assign the unanswered question. A useful result can be a confirmed administrative link, a scoped purchasing relationship or a documented unknown.