Unconfirmed LTL pickups: a follow-up schedule that gets an answer before the dock closes
Key Takeaways
An unconfirmed LTL pickup needs a follow-up schedule that is timed backward from the shipper's dock close, not forward from the moment the request went out. The schedule sets fixed checkpoints: a confirmation number by late morning, a second channel by midday, a driver or route answer by early afternoon, and a decision on rebooking or rescheduling before the last trailer door closes. Wilson, by Cartage, is an AI logistics coordinator that runs those checkpoints for each load, contacts the carrier through email, API, EDI, or phone where configured, and brings the load owner in when a decision is needed.
- An LTL pickup request is not confirmed until the carrier returns a confirmation number or a clear yes. A sent request is only a sent request.
- Build the schedule backward from dock close. Each checkpoint has a deadline, an owner, and a next action if the carrier stays silent.
- Switch channels as the day goes on. A second email to the same inbox rarely gets a different result; a call to the terminal or an API status check often does.
- Separate "driver arrived" from "picked up." A load counts as picked up only on a signed BOL or a confirmed departure.
- Decide the late-day outcome in advance: rebook with another approved carrier, move the pickup to tomorrow, or hold and tell the customer.
- Software for this job should execute the follow-up and record every attempt, not just show a red status on a screen.
- Wilson follows up, notifies the team in Slack, Microsoft Teams, email, or SMS, and initiates rebooking from the approved carrier list within the company's approval rules.
Should a person or software chase unconfirmed LTL pickups before the dock closes?
Most LTL shippers should let software run the routine follow-up and keep people on the decisions that change cost, carrier, or the customer promise. The split depends on how many pickups go out each day, how many carriers are involved, and how late in the day the silence happens.
| Situation on the shipping day | Who should act | Why |
|---|---|---|
| Pickup request sent, no confirmation number after the first check | Software | A second request or status check is routine and time-sensitive. It should not wait for someone to notice. |
| Carrier replied with a question about class, dimensions, or liftgate | Software gathers the facts; the load owner approves changes | Changes to freight class or price affect the BOL and the bill. They go to the person who owns the load. |
| No answer by midday from a carrier that usually confirms early | Software switches channels and alerts the team | A pattern break is a signal the team should see early. |
| Driver shows on the carrier's route but no ETA before dock close | Software asks the carrier or driver for an ETA | An ETA question is factual. It needs persistence, not judgment. |
| No answer 90 minutes before dock close on an order with a must-ship date | Load owner decides, with options prepared | Rebooking, paying more, or moving the date are business choices. |
| Rebooking with an approved carrier inside the configured rate limit | Software, if the company allows it | Within the rules, rebooking is routine. Outside the rules, it waits for approval. |
| Customer must be told the order ships tomorrow | Software sends the notice if configured; account owner handles sensitive accounts | Some customers expect a call from their contact. |
Why LTL pickups go unconfirmed more often than truckload pickups
LTL carriers run pickup-and-delivery routes out of local terminals. A pickup request joins a dispatch board with dozens of other stops, and the route for the afternoon is often built late in the morning. The shipper's request can be received, accepted by the system, and still not be assigned to a driver. The shipper sees a sent request. The terminal may see an unassigned stop. That gap is where most unconfirmed pickups live.
LTL shippers also send many small requests to several carriers on the same day. A distributor might tender eight orders to three regional carriers and two national carriers before noon. Each carrier confirms in its own way: an automated email with a confirmation number, a portal status, an EDI response, or nothing at all until the driver arrives. A person tracking all of those by inbox alone loses the thread by early afternoon.
What the decision is really about
The real choice is not software versus people. It is whether the follow-up runs on a clock or on memory. A coordinator who remembers to check at 2:00 p.m. on a calm day may not remember on the last day of the quarter, when the dock has twice the normal volume. A schedule with fixed checkpoints holds on both days. Software makes the schedule hold without depending on who is at the desk.
Where shared inbox tools and visibility platforms stop
Shared inbox tools organize the carrier emails, but they do not send the next follow-up when a reply fails to arrive. Visibility platforms show status when the carrier reports it, but an unconfirmed pickup is the case where the carrier has reported nothing. In a March 2025 BCI Global survey of 240 supply chain leaders, only 35% said they had detailed end-to-end visibility. Silence on a pickup request is one of the places where that gap shows up first, because there is no event to display.
The follow-up schedule, step by step, from pickup request to dock close
A working follow-up schedule has five checkpoints tied to the dock's closing time, and an AI logistics coordinator such as Wilson can run each one for every load. The times below assume a dock that closes at 5:00 p.m. and pickup requests submitted in the morning. Shift each checkpoint to match the actual dock hours and the carrier's same-day request cutoff.
| Checkpoint | Example time | What should be true | Action if it is not |
|---|---|---|---|
| 1. Request acknowledged | Within 30 minutes of the request | The carrier returned a confirmation number or accepted the tender | Resend through the same channel and check the carrier's portal or API for the request |
| 2. Confirmation in hand | 11:30 a.m. | Every morning request has a confirmation number and a pickup window | Switch channels: call the local terminal where configured, or use a second contact |
| 3. Route assignment | 1:30 p.m. | The carrier says the stop is on a driver's route for today | Ask the terminal for a driver assignment and an ETA; alert the load owner |
| 4. Driver ETA | 3:00 p.m. | There is an ETA that lands before dock close | Contact the driver by phone or text if the carrier shared the number; prepare rebooking options |
| 5. Decision point | 3:30 p.m. | The pickup is still on track | The load owner chooses: rebook, move to tomorrow, or hold; the customer is told if configured |
Checkpoint 1: get a confirmation number, not a send receipt
The first checkpoint confirms that the request reached a carrier system that will act on it. For LTL, that proof is usually a pickup confirmation number. An email bounce, an EDI rejection, or a portal error should trigger a resend within minutes. A request that disappears without a number should be treated as not received, even if the email client shows it as sent.
This checkpoint also catches data problems early. LTL carriers reject or hold requests for missing freight class, missing dimensions on oversized pallets, a residential delivery without a liftgate note, or a pickup address that does not match the account.
Checkpoint 2: change the channel by late morning
If a confirmation has not arrived by late morning, the next step uses a different channel. Repeating the same email to the same address is the most common follow-up and the least effective one. Better options include a status check through the carrier's API, a check of the carrier's website for the request, a call to the local terminal where calls are configured, or a message to a named contact the carrier assigned to the account.
Checkpoint 3: confirm the stop is on a route
A confirmation number means the carrier has the request. It does not mean a driver will come today. By early afternoon, the follow-up should ask a narrower question: is this stop on a driver's route for today, and what window does the terminal expect? Many terminals finalize afternoon routes only after morning deliveries clear.
Checkpoint 4: get an ETA that beats dock close
The fourth checkpoint compares the driver ETA with the dock's closing time and the time the dock needs to load. If the dock needs 20 minutes to load four pallets and closes at 5:00 p.m., an ETA of 4:50 p.m. is a problem, not a success. Where the carrier shares the driver's phone number, a direct text or call often gives the most current ETA.
Checkpoint 5: decide while options still exist
The last checkpoint is a decision, not another follow-up. By mid-afternoon, other approved carriers may still accept a same-day pickup in some markets. By 4:30 p.m., most will not. The schedule should put the decision in front of the load owner early enough that rebooking is still a real option, with the facts already gathered: what was sent, every attempt and reply, the carrier's last statement, and which approved carriers serve the lane.
A hypothetical example: an HVAC parts distributor with a 4:00 p.m. dock close
A hypothetical HVAC parts distributor ships 12 to 18 LTL orders a day from one warehouse, with a dock that closes at 4:00 p.m. In early summer, contractor orders spike and the dock runs near capacity. On one Tuesday, 14 pickup requests go out between 8:00 and 10:00 a.m. to four carriers. By 10:30 a.m., 11 have confirmation numbers. Of the three without one, two belong to a regional carrier whose terminal emails confirmations in a single batch, and one belongs to a national carrier that returned nothing.
The follow-up resends the national carrier request at 10:30 a.m. and checks the carrier's website by account. The request is not there. A corrected request goes out with the right account number, and a confirmation returns at 10:52 a.m. The regional carrier's batch arrives at 11:15 a.m. with both numbers. By 1:00 p.m., one regional stop has no driver assigned. The terminal says the route is full. At 1:15 p.m., the load owner sees the facts and approves rebooking with a second approved carrier inside the rate limit. The freight leaves at 3:20 p.m.
Rules and limits: what the follow-up does alone and what waits for the load owner
A follow-up schedule needs written rules about what runs automatically and what needs a person, and an AI logistics coordinator should follow those rules exactly. For unconfirmed LTL pickups, the rules usually cover contact attempts, channel changes, rebooking, cost changes, BOL changes, and customer notices. A clear set of rules lets the routine work run on time while keeping control of every choice that affects money or the customer.
Actions that can run inside the rules
- Resending a pickup request after a failed delivery or rejection.
- Checking the carrier's API, website by PRO or confirmation number, or EDI status for the request.
- Calling the terminal or texting the driver where those channels are configured and the carrier shared the contact.
- Posting a status update to the team in Slack, Microsoft Teams, email, or SMS at each missed checkpoint.
- Recording every attempt, reply, and status change in the shipment history.
- Rebooking with an approved carrier when the rate is inside the configured limit and the company has allowed automatic rebooking for that lane.
Actions that wait for the load owner
- Any change to the BOL address, freight class, carrier, or price. Those changes go to the load owner before the BOL is updated.
- A rebooking rate above the approval limit, or with a carrier that is not on the approved list. Cartage can present additional capacity, but the company approves each carrier before it is used.
- Moving a pickup for an order with a firm must-ship or must-arrive date set by the customer.
- Customer messages for accounts the company has marked as handled by a named account owner.
- Accessorial charges the carrier quotes at the last minute, such as a liftgate or inside pickup that was not on the original request.
Limits that keep the schedule honest
Three limits prevent a follow-up schedule from producing false comfort. First, an "arrived" status is not a pickup. A driver can arrive, find the freight not ready or the paperwork wrong, and leave empty. The pickup counts only on a signed BOL or a confirmed departure. Second, a carrier reply without a time is not an answer. "We will get it today" should trigger a request for a window. Third, the schedule should not keep sending messages after the decision point. Once the load owner chooses to move a pickup to tomorrow, the follow-up should change to tomorrow's checkpoints, not keep asking the carrier about today.
For a fuller list of which actions can be set to run alone and which hold for approval, see how configurable approvals work for an AI logistics coordinator.
When the carrier still has not answered: late-day outcomes and next-morning recovery
When a carrier stays silent past the decision point, the shipper has three outcomes to choose from, and an AI logistics coordinator should prepare each one before the load owner is asked to decide. The outcomes are rebooking today with another approved carrier, moving the pickup to the next business day with the same carrier, or holding the freight and resetting the customer's expectation. Each has a different cost, and each depends on the order's dates.
| Late-day outcome | When it fits | What has to happen next |
|---|---|---|
| Rebook today with another approved carrier | The order has a firm ship date and another approved carrier can still take the pickup | Cancel the first request in writing, issue a new BOL, update the customer if configured, and record the reason |
| Move the pickup to tomorrow with the same carrier | The order has slack and the carrier gives a firm morning window | Get a new confirmation number for tomorrow, restart the checkpoints at the dock's opening time, and tell the dock |
| Hold the freight and reset the customer date | No approved carrier can take it today and the customer must know now | Send the customer notice, record the new ship date, and flag the order for the first pickup tomorrow |
Cancel the first request in writing
When freight is rebooked, the original pickup request must be cancelled with the first carrier in writing. If it is not, a driver may still arrive the next morning, find nothing, and the carrier may bill a dry run or attempted pickup charge. The cancellation and the carrier's reply belong in the shipment history so that any later invoice line can be checked against it.
Watch for the late driver who does arrive
Sometimes a silent carrier sends a driver at 4:45 p.m. after the freight has been rebooked. The dock needs to know which carrier will take which pallets. The BOL must name the right carrier, so the rebooking decision should reach the dock the moment it is made.
Next-morning recovery
A pickup moved to tomorrow should start tomorrow's schedule at dock opening, not at 11:30 a.m. The first check confirms that the carrier's terminal still has the stop on the route. The second check confirms a driver window. If the same carrier misses twice in a row, the load owner should decide whether to keep the freight with that carrier or rebook. To see how a missed pickup becomes a late delivery and how to catch it in transit, read how to catch a missed LTL pickup before delivery slips.
Seasonal pressure points for LTL shippers
LTL pickups get harder to confirm on the days when volume is highest. Month-end and quarter-end shipping push more freight onto the same terminals. Holiday weeks and winter weather shorten routes. A follow-up schedule should tighten on those days: earlier checkpoints, earlier decision points, and a pre-approved list of backup carriers for the most important lanes.
A hypothetical example: a cosmetics brand shipping to a retail DC at quarter end
A hypothetical cosmetics brand ships six LTL orders on the last business day of the quarter to retail distribution centers with strict delivery appointments. The dock closes at 5:00 p.m. Five pickups are confirmed by 11:00 a.m. The sixth, for a 10-pallet order, has a confirmation number but no driver assignment at 1:30 p.m. A call to the terminal at 1:40 p.m. reaches a dispatcher who says the stop may roll to tomorrow because the route is overbooked.
The load owner sees the update in Microsoft Teams at 1:45 p.m. with two options already priced from approved carriers. One option is inside the rate limit and can pick up at 3:30 p.m. The load owner approves it. The first request is cancelled in writing at 1:55 p.m. The new BOL goes to the dock with the new carrier name. The freight leaves at 3:40 p.m., and the order keeps its quarter-end ship date.
How to test pickup follow-up software on your own LTL loads
The best test of pickup follow-up software is to run it against your own recent LTL loads, including the ones that went wrong, and to check whether an AI logistics coordinator would have acted at each checkpoint. Product demos usually show a confirmed pickup. The useful question is what the software does when nothing comes back.
Bring three loads from last month
- One load where the carrier confirmed quickly and picked up on time. This shows the normal path and how status is recorded.
- One load where the carrier never confirmed and the freight was still on the dock at close. This shows whether the software would have caught the silence early.
- One load that was rebooked late in the day. This shows how the software handles cancellation, a new BOL, and the late driver who still arrives.
Questions to ask in the evaluation
| Question | A useful answer | A weak answer |
|---|---|---|
| What happens 30 minutes after a pickup request with no confirmation? | The software resends or checks the carrier's system and records the attempt | The load turns red on a dashboard |
| Which channels can it use to reach the carrier? | Email, API, EDI where supported, phone where configured, and driver text when the carrier shares the number | Email only |
| How does it tell "arrived" from "picked up"? | Picked up requires a signed BOL or a confirmed departure | The driver check-in counts as pickup |
| Who approves a rebooking above the rate limit? | The load owner, with the options already gathered | The software books the cheapest available carrier |
| Where are the attempts recorded? | In a searchable, exportable shipment history with change history | In a chat thread or an inbox folder |
| Does it need a new integration project to start? | No; it can start from the current ERP feed, file drop, spreadsheet, email, or API | Only after a full implementation |
Score the timing, not the features
For each test load, write down the time the problem first became visible in the old process and the time the software would have raised it. Then write down whether the software would have taken the next action itself or only raised a flag. A tool that sends the follow-up, switches channels, and gives the load owner a prepared decision at 1:30 p.m. has changed the outcome.
Check the implementation burden honestly
Many LTL shippers have lived through a long software rollout. ARC Advisory Group research reported by Inbound Logistics in 2017 found that only 27% of TMS implementations finished on time with full functionality, 39% finished on time without all functionality, 24% were late but functional, and 9% were late and not functional. Pickup follow-up should not require a project of that size. Ask which data flow it starts from and how many lanes it covers first.
How Wilson, by Cartage, handles unconfirmed LTL pickups
Wilson is an AI logistics coordinator that executes the pickup follow-up for each LTL load and brings people in only when a decision is needed. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. Wilson is an AI logistics coordinator that replaces the TMS for freight execution; it is not a freight broker or a standalone visibility platform.
From order to pickup request
Wilson starts from the data flow the company already has: an ERP feed, a scheduled file drop, a spreadsheet, email, or an API. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica, and other ERP environments, with the exact connection depending on the customer's data flow and scope. No integration project is required to start. Wilson quotes and books with the carriers the company has approved, tenders to them first, and prepares the documents the pickup needs, including bills of lading, packing slips, and pallet labels.
Following up through the carrier's channels
After a pickup request goes out, Wilson watches for the carrier's confirmation. If it does not arrive, Wilson follows up through the channels each carrier supports: email, API, EDI where the carrier supports it, and phone calls where configured. When the carrier shares the driver's contact information, Wilson contacts the driver by phone or text for an ETA. Wilson checks status from the best source available for each load, including the carrier's API, GPS or ELD data where it exists, the carrier's website by PRO number, and direct contact when there is no other source.
Keeping the team and the customer informed
Wilson notifies the internal team in Slack, Microsoft Teams, email, or SMS when a checkpoint is missed or a decision is needed. If the company configures customer notices, Wilson tells the customer when a ship date moves. Every attempt, reply, and status change is stored in a searchable, exportable shipment history with change history, so the team can see exactly what happened and when.
Missed pickups, cancellations, and rebooking
When Wilson detects a missed pickup, a cancellation, or a delay, it contacts the carrier, notifies the internal team, notifies the customer if configured, and initiates rebooking from the approved carrier list. Rebooking runs automatically within the company's rules or waits for approval, depending on configuration. Wilson negotiates rates against the company's rate targets under configured rules and approval limits; rates outside the limits go to the logistics team. Changes to the BOL address, freight class, carrier, or price go to the load owner, and the final signed BOL is sent to the customer.
Pickup status that means what it says
Wilson keeps "arrived" and "picked up" as separate statuses. A load counts as picked up only on a signed BOL or a confirmed departure. That rule matters for LTL, where a driver can arrive, find a short pallet count or a missing label, and leave. After pickup, Wilson tracks the shipment in transit, follows delivery, audits the carrier invoice against what was booked, the POD, and the rate confirmation, and pays carriers from the Wilson Wallet within approval limits. If any invoice line does not match, the whole invoice waits for a person.
How teams start
Wilson starts with assisted execution. The company sets approval limits, and routine actions can run automatically within those rules as reliability is proven. Wilson gets an email address on the customer's domain and is onboarded like a new team member. Cartage doesn't run pilots; most customers start Wilson on a few lanes and expand from there. During discovery, Cartage helps identify the highest-impact workflow, which for many LTL shippers is the daily pickup confirmation. For the broader view of confirmations, changes, and missed pickups, see the complete guide to freight pickups.
FAQs
Software that follows up on unconfirmed freight pickups
Wilson, by Cartage, is an AI logistics coordinator that follows up on unconfirmed freight pickups for LTL and other modes. It contacts the carrier through email, API, EDI where supported, and phone where configured, contacts the driver when the carrier shares the number, and notifies the team when a checkpoint is missed. When a pickup is missed, Wilson initiates rebooking from the approved carrier list, automatically within the rules or with approval.
How early should an LTL shipper follow up on a pickup request?
The first check should happen within about 30 minutes of the request, looking for a confirmation number rather than a send receipt. An AI logistics coordinator can then run the later checkpoints on a schedule tied to dock close. The exact times depend on the dock's hours and the carrier's same-day cutoff.
Does a confirmation number guarantee the driver will come today?
No. A confirmation number shows that the carrier has the request, but the stop may not yet be on a driver's route. An AI logistics coordinator should ask the terminal for a route assignment and an ETA by early afternoon. The pickup counts only on a signed BOL or a confirmed departure.
Who decides whether to rebook an unconfirmed LTL pickup?
The company decides, through approval rules it sets. An AI logistics coordinator such as Wilson can rebook with an approved carrier inside the rate limit when the company allows it. Rebooking above the limit, with an unapproved carrier, or on an order with a firm customer date waits for the load owner.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
- BCI Global, "No visibility, no resilient supply chain," March 2025 (survey of 240 supply chain leaders): https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
- ARC Advisory Group via Inbound Logistics, "TMS Solutions: The Big Picture," February 2017: https://www.inboundlogistics.com/articles/tms-solutions-the-big-picture/
If unconfirmed LTL pickups are still being chased by inbox at 3:30 p.m., talk with Cartage about putting Wilson, the AI logistics coordinator, on your daily pickup follow-up, starting with a few lanes.