How to follow up when a carrier does not answer a BOL request
Key Takeaways
When a carrier does not answer a BOL request, the team should follow up on a set schedule, with a specific message, through a second channel, and escalate to a named person when the deadline passes. An AI logistics coordinator can run that follow-up on every load and save each attempt with the shipment.
- A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
- Shippers ask carriers for BOL-related items at three points: before pickup, when the BOL changes, and after pickup.
- Each request should have a deadline tied to the pickup or to invoice review.
- A good follow-up names the load, the exact item, the reason, and the deadline.
- If email gets no answer, the next attempt should use a second channel, such as a phone call or the carrier's portal.
- Escalation should go to the carrier's dispatch or account contact, not to the same inbox again.
- Wilson, by Cartage, is an AI logistics coordinator that requests carrier documents, follows up on a schedule through email and phone where configured, and escalates when a deadline passes.
What BOL requests do carriers often leave unanswered?
Carriers most often leave three kinds of BOL requests unanswered: requests for the carrier's own BOL or PRO number before pickup, requests to confirm a BOL change, and requests for the signed BOL copy after pickup. An AI logistics coordinator should treat each one differently, because each has its own deadline and risk.
The table below shows the three types.
| Request | When it happens | Why it matters | Deadline driven by |
|---|---|---|---|
| Carrier BOL or PRO number | Before pickup | Some carriers require their own form or number | Pickup time |
| Confirmation of a BOL change | After booking, before pickup | Weight, class, or address changes may affect price | Pickup time |
| Signed BOL copy | After pickup | Proof of what was tendered and any exceptions noted | Invoice review or claim |
A PRO number is a tracking number a carrier gives to a shipment. Some carriers assign it in advance and want it printed on the BOL.
Before pickup: the carrier's own form
Some carriers, especially for less-than-truckload freight, ask shippers to create the BOL in the carrier's portal or to use a PRO number the carrier assigns. Less-than-truckload, or LTL, is freight that shares a trailer with other shippers' freight. When the shipper asks for a PRO number and gets no answer, the pickup may go ahead with the shipper's own BOL. That can work, but tracking and billing may be harder later.
After a change: the carrier's confirmation
When the BOL changes after booking, such as a higher weight or a new delivery address, the shipper should ask the carrier to confirm in writing. If the carrier does not answer, the change may still ship, but the price question waits until the invoice. That is where disputes start.
Why the change confirmation matters for audit
When a BOL change raises the weight or class, the carrier's invoice will often follow the new numbers. If the carrier never confirmed a price for those numbers, the audit has nothing to compare against. The team ends up negotiating after the fact, with less leverage and more emails. A confirmation before pickup turns that negotiation into a quick check.
After pickup: the signed copy
The driver signs the BOL at pickup. The shipper usually keeps a copy, but sometimes the warehouse does not scan it, or the driver takes the only signed copy. Then the shipper must ask the carrier for it. Without it, the shipper may struggle to prove what was tendered if there is a shortage or damage claim.
Requests from the receiver side
Sometimes the request starts with the receiver. A customer asks for a copy of the BOL to match a delivery against its purchase order, or to support a claim. If the shipper does not have the signed copy, it must ask the carrier. The receiver's deadline then becomes the shipper's deadline, and the follow-up should reflect that.
Why carriers do not answer
Most unanswered requests are not refusals. The message went to a general inbox. The dispatcher is busy with live loads. The request did not say which load or what was needed. The carrier's billing team, not dispatch, holds the signed copy. A follow-up plan solves most of these causes by being specific and by trying the right contact.
When should the team follow up on an unanswered BOL request?
The team should follow up at set times tied to the deadline: a first reminder when the reply is overdue, a second attempt through another channel, and escalation before the deadline is missed. An AI logistics coordinator should set these times when the request goes out, so nothing depends on memory.
Follow-up timing by request type
| Request | First request | First follow-up | Second channel | Escalation |
|---|---|---|---|---|
| PRO number or carrier BOL | At booking | 4 business hours later | Phone or portal by end of day | Day before pickup |
| Change confirmation | When the change is made | 2 hours later | Phone call | 4 hours before pickup |
| Signed BOL copy | Day after pickup | 1 business day later | Carrier billing contact | 3 business days after pickup |
These times are examples. Each team should set its own based on its lanes, carriers, and how close to pickup loads are usually booked.
The follow-up workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Request | Item needed for the load | Sends a specific request with a deadline | Never for routine items |
| 2. Wait | Request sent | Watches for a reply and matches it to the load | Never |
| 3. Remind | Reply overdue | Sends a short reminder to the same contact | Never |
| 4. Switch channel | Reminder unanswered | Calls, checks the portal, or tries another contact | Never for routine calls |
| 5. Escalate | Deadline near | Sends the history to the load owner and a higher carrier contact | Owner decides what happens to the load |
| 6. Close | Item received | Saves the item, checks it, and stops the follow-up | When the item has errors |
Tie the deadline to the risk
A change confirmation for a load that leaves in three hours is urgent. A signed BOL copy for a delivered load with no issues is not. The follow-up timing should reflect what happens if the answer never comes. Requests that could stop a pickup or change a price should move faster than requests for records.
Who owns the follow-up
The follow-up should have one owner per load. If the coordinator who booked the load assumes the shipping clerk will chase the PRO number, and the clerk assumes the coordinator will, nobody does. An AI logistics coordinator can own the routine follow-up for every load and pass only escalations to a person, so ownership is never in doubt.
Do not follow up too often
Messages every 30 minutes annoy carriers and get filtered. A clear schedule with fewer, better messages works better. Each follow-up should add something: a new channel, a new contact, or a clearer deadline.
Set the schedule by carrier
Some carriers answer email within an hour. Others rarely answer email at all but pick up the phone. Over time, the team learns each carrier's habits. The follow-up schedule should reflect them: a shorter wait and an earlier call for carriers that are slow on email, and fewer reminders for carriers that reliably answer.
Stop the clock when the answer arrives
When the carrier answers, the follow-up should stop right away. Nothing makes a team look less organized than a reminder sent after the carrier already replied. The AI logistics coordinator should match each reply to its request and close the task.
Weekends and holidays
A request sent on Friday afternoon may not be read until Monday. If the pickup is on Monday morning, that is too late. The schedule should account for business hours at the carrier and move urgent requests earlier before weekends and holidays. A phone call on Friday afternoon is often better than an email that waits all weekend.
Check the answer, not just its arrival
When the reply comes, it should be checked. A PRO number should have the right format for that carrier. A signed BOL should be for the right load and should be legible. A rate confirmation for a change should show the new weight or class. If the answer is wrong or incomplete, the task stays open and the follow-up continues with a clear note about what is still missing.
Hypothetical example: a PRO number before pickup
This example is hypothetical and does not describe a real customer. A distributor books an LTL load on Monday morning for Wednesday pickup. The carrier requires a pre-assigned PRO number. The AI logistics coordinator asks the carrier's customer service inbox at booking. By Monday afternoon, there is no reply. It sends a reminder with the load details. On Tuesday morning, it calls the carrier's local terminal, gets the PRO number, and adds it to the BOL. Pickup goes ahead on Wednesday with the right number.
What should a BOL follow-up message say?
A BOL follow-up message should say which load, what item is needed, why, by when, and how to send it, in the first two lines. An AI logistics coordinator should write a short, specific message for each attempt, so the carrier can answer without searching.
What each message needs
| Part | Example |
|---|---|
| Load reference | "Load 6120, PO 88214, pickup Nov 5 from Dayton, OH" |
| Item needed | "PRO number for this shipment" |
| Reason | "Our receiver requires it on the BOL" |
| Deadline | "By 3 p.m. today" |
| How to reply | "Reply to this email or call 555-0100" |
Example: first request
"Load 6120, pickup Nov 5 from Dayton, OH. Please send the PRO number for this shipment by 3 p.m. today. Our receiver requires it on the BOL. Reply here or call 555-0100."
Example: follow-up
"Following up on Load 6120, pickup Nov 5 from Dayton, OH. We still need the PRO number by 3 p.m. today. If this should go to someone else, please let us know who."
Example: change confirmation
"Load 6233, pickup tomorrow 8 a.m. The weight changed from 4,200 to 5,050 pounds. Please confirm the rate stays at $640, or send the new rate, by 4 p.m. today."
Example: signed copy request
"Load 6012, picked up Nov 2 from Dayton, OH, PRO 445-221. Please send the signed BOL copy, including any exceptions the driver noted. We need it for invoice review by Nov 6."
Reply in the same thread
Each follow-up should go in the same email thread as the first request, so the carrier sees the history in one place. If the team switches contacts, it should forward the thread with a short note at the top. Starting a new thread for every reminder makes the carrier search for context and slows the answer.
Match the carrier's language
Carriers use their own terms. Some call the PRO number a "tracking number" or a "freight bill number." Some call the signed BOL a "shipper copy" or a "pickup receipt." Using the carrier's own term in the message removes one reason for a slow reply. The AI logistics coordinator can store each carrier's terms with its contact list.
Avoid vague messages
A message that says "Please send the BOL" without a load number may never get an answer. A message with three questions in one paragraph may get a partial answer. One request per message, with the load details first, gets the fastest replies.
Which channels should the follow-up use?
The follow-up should start with the channel the carrier uses for that kind of request, then move to a second channel when the first gets no reply. An AI logistics coordinator should know each carrier's preferred contacts and try them in order.
Channel order by request
| Request | First channel | Second channel | Third channel |
|---|---|---|---|
| PRO number or carrier BOL | Carrier customer service email or portal | Phone call to the local terminal | Carrier account rep |
| Change confirmation | Dispatcher email | Phone call to dispatch | Carrier account rep |
| Signed BOL copy | Carrier billing or document email | Carrier portal download | Phone call to billing |
Why the second channel matters
Email is easy to send and easy to miss. A phone call reaches a person who can answer on the spot. A portal may already hold the document. Moving to a second channel is often faster than a third email to the same inbox.
Portals often hold the answer
Many carriers post signed BOLs, delivery receipts, and PRO numbers in their customer portals. Checking the portal before sending another email can close the request without waiting for anyone. The AI logistics coordinator should know which carriers use portals and what each one shows, so it checks there first for those carriers.
Keep a contact list by carrier
Each carrier has different contacts for dispatch, billing, and documents. A small contact list for each carrier, kept with the carrier record, saves time on every follow-up. When a contact changes, the list should be updated, so the next request goes to the right place.
Use EDI or API where the carrier supports it
Some carriers can send PRO numbers, status updates, and document images through EDI or an API. EDI, or electronic data interchange, is a standard format that lets two companies' systems exchange business documents. An API is a connection that lets two software systems talk directly. Where a carrier supports these, the request may not need a person on either side.
Phone calls need a short script
A phone call works best when the caller has the facts ready: load number, PO, pickup date, origin, and the exact item needed. The call should end with a clear promise, such as "I will email the PRO number within 30 minutes," and the promise should be saved with the load. If the promise is not kept, the next follow-up can quote it.
Text messages for drivers, not offices
Some teams text drivers directly for a photo of the signed BOL right after pickup. This can be fast, but only when the carrier allows it and the driver's number is on file. Office requests, such as PRO numbers and price confirmations, should still go to dispatch or billing.
Record every attempt
Each attempt should be saved with the load: the time, the channel, the contact, and the message. If the request is escalated, the person who receives it can see what has already been tried.
When should an unanswered BOL request be escalated, and to whom?
An unanswered BOL request should be escalated before the deadline is missed, to a named person inside the company and to a higher contact at the carrier. An AI logistics coordinator should send the escalation with the full history, so the person can act without asking what happened.
Escalation paths
| Situation | Escalate inside to | Escalate at the carrier to |
|---|---|---|
| PRO number missing the day before pickup | Load owner | Carrier account rep |
| Change not confirmed hours before pickup | Load owner | Dispatch manager |
| Signed BOL missing several days after pickup | Logistics lead or AP contact | Carrier billing manager |
| Repeated non-response from one carrier | Logistics manager | Carrier account rep |
AP, or accounts payable, is the finance team that pays suppliers.
What the load owner decides
When a change confirmation is still missing close to pickup, the load owner decides whether to ship at the original terms, hold the load, or move it to another approved carrier. The decision depends on the price risk, the delivery promise, and the carrier relationship. The decision should be saved with the load.
Move the load if the carrier stays silent
If a carrier will not confirm a change and the pickup is close, the load owner may move the load to another approved carrier. This is a big step. It can cost more, and the first carrier should be canceled in writing so two trucks do not arrive. The decision should follow the company's rules and approval limits, and it should be saved with the load.
What happens at invoice time
If the signed BOL never arrives, the invoice review may need other proof of pickup, such as the carrier's tracking data or the warehouse's loading record. The audit should note that the signed copy is missing. Some teams hold payment until the copy arrives; others pay and flag the load. The rule should be set in advance.
Do not punish the carrier for the shipper's gaps
Sometimes the carrier did not answer because the request was unclear, went to the wrong contact, or was sent after the carrier's cutoff. Before blaming the carrier, the team should check its own messages. A pattern of non-response from one contact may simply mean the contact list is out of date.
Use non-response in carrier reviews
A carrier that often ignores BOL requests creates work and risk. The team should track response times by carrier and discuss them in carrier reviews. A carrier that improves can stay in the tender order. A carrier that does not may move lower.
Measure follow-up results
The team should track how many BOL requests were answered on the first attempt, how many needed a second channel, and how many reached escalation. It should also track the average time to an answer by carrier and by request type. These numbers show where the process works and where the contact list or message needs work. The AI logistics coordinator can report them on request from the loads it handles.
Hypothetical example: a missing change confirmation
This example is hypothetical and does not describe a real customer. A manufacturer changes an LTL load's class from 70 to 85 the day before pickup. The AI logistics coordinator emails the carrier's dispatcher, then calls dispatch two hours later and leaves a message. By 8 a.m. on pickup day, there is still no confirmation. It escalates to the load owner with both attempts and the estimated rate difference. The owner approves shipping and asks the carrier's account rep to confirm the new rate in writing. The rep confirms by 10 a.m.
Where does Wilson fit when a carrier does not answer a BOL request?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, prepares the documents each load needs, such as bills of lading, and follows up with carriers when a document or confirmation is missing. Wilson sets the follow-up schedule when each request goes out and escalates before the deadline.
Wilson replaces the TMS for freight execution and connects to the company's ERP. A TMS, or transportation management system, is software used to plan, book, and track freight. An ERP, or enterprise resource planning system, is the company's main business system for orders, inventory, and accounting.
What Wilson does not do
Wilson does not accept a carrier's new price above the customer's approval limits, and it does not move a load to a new carrier outside the customer's rules. Wilson does not invent a PRO number or sign documents for the carrier. When a carrier stays silent past the deadline, Wilson brings the decision to the person who owns the load.
How Wilson follows up
Wilson has its own email address on the customer's domain, so carriers reply to it the way they would reply to a coordinator. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured. It matches each reply to its request, closes the task when the answer arrives, and notifies internal teams through Slack, Microsoft Teams, email, or SMS when escalation is needed.
Carriers, approvals, and payment
Wilson tenders the customer's approved carriers first, and the customer approves each new carrier before Wilson uses it. When the carrier invoice arrives, Wilson audits and reconciles it against what was booked, including any confirmed BOL change. Customers use the Wilson Wallet to pay their carriers. Payments above approval limits or outside the rules wait for a person. Wilson has no subscription or platform fee; its pricing is a percentage of the freight payments coordinated through the Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom.
What Cartage asks in discovery
Cartage asks which carriers require their own BOL or PRO numbers, how signed BOLs come back today, who the team calls when a carrier goes quiet, and how long the team waits before escalating. These answers shape the follow-up schedule an AI logistics coordinator uses for each carrier.
Where teams start
Wilson starts with assisted execution. Approval limits are set by the customer, and routine actions can run automatically within those rules as reliability is proven. Timing depends on scope: most teams start on a few lanes and expand from there. Every request, follow-up, and reply is saved in the shipment record with change history.
Teams that follow up on other carrier documents can use the same approach for a missing carrier rate confirmation. Teams deciding who owns follow-up can read which software owns the second ask when a carrier does not reply.
This article is part of our complete guide to bills of lading from booking to delivery.
FAQs
How soon should a team follow up on an unanswered BOL request?
It depends on the deadline. For items needed before pickup, follow up within a few hours. An AI logistics coordinator sets the schedule when the request goes out.
What should a BOL follow-up message include?
The load reference, the item needed, why, the deadline, and how to reply. An AI logistics coordinator puts these in the first two lines.
What if email gets no answer?
Try a second channel, such as a phone call or the carrier's portal. An AI logistics coordinator moves through each carrier's contacts in order.
When should a BOL request be escalated?
Before the deadline is missed, to the load owner and a higher carrier contact. An AI logistics coordinator sends the escalation with the full history.
Should a team hold carrier payment until the signed BOL arrives?
It depends on the team's rules. Some teams hold payment; others pay and flag the load. An AI logistics coordinator applies the rule the team sets and records the decision.
Sources
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator follows up with carriers on bill of lading requests and escalates before a deadline is missed: talk to the Cartage team.