How do you run carrier sourcing in a CRM?

Most CRMs in freight are built for the shipper side. That makes sense. Shippers pay the bills, so that's where the first CRM project goes.

Then somebody asks: what about the carriers?

At Worldwide Logistics (WWL), the carrier sourcing team ran on distribution lists, inboxes and walking over to someone's desk. Round one feedback on an RFP got asked for four times, because nobody could find where it had been sent. Nobody was lazy. The work just had no home.

A carrier sourcing CRM gives it one. Here's how we set it up.

Why does carrier sourcing need its own CRM setup?

Carrier sourcing works differently from selling to shippers. You're managing thousands of carriers, most of them dormant at any moment, and the job is to find capacity on the right lanes before you need it. That needs its own records, its own queues and its own rules, not a copy of the sales pipeline.

The difference shows up in three places:

• Volume. WWL had 4,057 carriers in the first file we looked at, and a later import covered about 49,000. No one works 49,000 records. You need a way to decide who gets attention this week.
• Identity. Carrier names are messy. The same carrier shows up three different ways across email, the TMS and a spreadsheet. You need one key that doesn't change.
• Rhythm. RFPs run in rounds, with feedback, awards and start dates. Spot coverage happens in hours. Both need to land in the same place.

If you're also setting up the shipper side, our answer on what a freight brokerage CRM should track covers the other half of the model.

How should carriers be identified in a CRM?

Use the DOT number as the unique ID for every carrier, not the name. Names change and get typed five ways, but the DOT number stays with the carrier. Import on DOT number, match on DOT number, and flag any carrier record that doesn't have one so someone fixes it.

The FMCSA's public SAFER Company Snapshot lets anyone look a carrier up by its USDOT number, so it's a key your team, your TMS and your data vendors can all check. That makes it the obvious choice. When you match on DOT number, duplicates collapse and every email, load and RFP response lands on the right record.

At WWL, about 100 of the first 4,057 carriers had no DOT number on file. That's normal. Those records go into a short cleanup list before the import, not into the CRM as orphans.

Before the larger import, we ran a test import first. A test tells you whether the matching works, how many duplicates you really have and which fields are empty, before you load tens of thousands of records and have to undo them.

How do you decide which carriers each manager works?

Give each carrier manager a fixed-size working queue of cold carriers that refills itself. When a manager works a carrier, it stays with them. When a carrier sits untouched too long, it goes back to the pool so someone else can try. A short hold list protects carriers that just need a follow-up.

Here's the setup we built at WWL:

1. A queue of 75 cold carriers per manager. Enough to fill a week, small enough to actually work.
2. Automatic refills. When a manager converts or releases a carrier, the queue tops itself back up from the pool. Nobody hunts for the next name.
3. Idle after 7 days. A carrier with no activity for 7 days is marked idle and returned to the pool.
4. A 14-day hold list. A manager can hold a carrier for 14 days when a conversation is live but slow, so it isn't pulled away mid-discussion.

These rules sound small. They're the whole system. Without them, the best carriers get hoarded, the rest get ignored, and the database slowly fills with records nobody owns. It's the same problem sales teams have with accounts, and the same fix. Our answer on designing sales territories that scale walks through the account side of it.

There was pushback. Some managers worried about who could see which carriers, and in which zones. That's a fair concern, and the answer is a visibility rule written down before go-live, not a fight afterward.

How do you keep RFPs and feedback out of inboxes?

Put every RFP on a record with its rounds, the feedback from each round and the final award file, linked to the shipper and the carriers involved. Then the question "where's the round one feedback?" has one answer, and it doesn't need an email.

At WWL, the RFP flow moved from sales to pricing to operations, back to pricing and back to sales. Every handoff was an email. That loop was the top bottleneck in the whole process, and it's where visibility disappeared.

A good RFP setup in the CRM has:

• One RFP record per bid, with the shipper, lanes and due dates.
• Rounds as stages, each with its feedback attached when it comes in.
• The award file stored on the record, not in someone's downloads folder.
• Tasks for each handoff, so pricing and operations know when it's their turn.

The same pattern applies to spot quotes and contract bids on the shipper side: two motions, two pipelines, one place to look.

How do you send alerts without creating noise?

Alert people only when they need to act, and send everything else as a daily digest. A carrier going quiet on a key lane, an RFP round due tomorrow or feedback that just arrived deserve an alert. A field changing doesn't. Push the alert before the problem costs money.

WWL's carrier team said it plainly: they needed award files and alerts without noise. The ops side said the same thing about shippers, that alerts must push before silent churn costs revenue.

That's why we pair the CRM with an AI digest. At WWL, a daily AI briefing goes to about 153 users and surfaces $10K to $100K of freight a day before it turns into an escalation, for under $1 a day in model cost. Median customer reply time dropped from 9.32 to 6.27 business minutes. The full story is in the WWL case study and on how the WWL AI briefing works.

The rule we use: if an alert doesn't name the person who has to act and what they have to do, it belongs in the digest. If you're deciding which of these jobs a person should do and which an agent should do, our answer on where the line sits between human reps and AI agents lays out how we draw it.

Frequently asked questions

Should carriers and shippers live in the same CRM?

Yes, as different record types. RFPs link both sides, and leaders want to see shipper demand and carrier capacity together. Keeping them in one CRM lets an RFP record point to the shipper and to every carrier that bid, while separate record types keep the sales and carrier teams from seeing views that aren't theirs.

What about carriers without a DOT number?

Put them on a cleanup list before you import. Someone checks each one, finds the DOT number or confirms the carrier shouldn't be in the system. At WWL about 100 of the first 4,057 carriers needed that check. It's a short job, and it keeps every record in the CRM matchable.

How many carriers should each manager work at once?

Start with a fixed queue that fits a week of real work. At WWL that was 75 cold carriers per manager, refilled automatically, with idle carriers returned after 7 days. Adjust the number once you see how many a manager can really touch in a week, not before.

Do we need to bring TMS load data into the CRM for carriers?

Bring summaries, not every load. Lanes covered, recent volume and last load date are enough for a carrier manager to see who is active and where. Key everything on the DOT number so the TMS data and the CRM record always match. Start with a short sample of TMS data to test the matching.

Who owns the carrier sourcing setup after go-live?

A named operations owner, not IT and not the vendor. That person keeps the queue rules, the hold list and the visibility rules up to date as the team changes. A quick weekly look at idle carriers and records without a DOT number keeps the database clean.

Sources

• Worldwide Logistics (WWL) carrier sourcing sessions, 2026: 4,057 carriers with about 100 missing DOT numbers, DOT number as the unique ID, 75 cold carriers per manager refilled automatically, idle after 7 days, a 14-day hold list, a later import of about 49,000 carriers with a test import first, and questions about zone visibility.
• WWL carrier sourcing team, January 2026: RFP information in distribution lists, inboxes and desk visits, round one feedback asked for four times, and the need for award files and alerts without noise.
• WWL operations, 2026: the manual RFP flow from sales to pricing to operations and back as the top bottleneck, and alerts that must push before silent churn costs revenue.
• WWL case study and the WWL AI briefing story: a daily digest to about 153 users, reply times from 9.32 to 6.27 business minutes, $10K to $100K of freight a day surfaced, and under $1 a day in model cost.
• Federal Motor Carrier Safety Administration, SAFER Company Snapshot: look up any carrier by USDOT number, MC number or name.