Our customer wants a heads-up before the truck arrives. How do we do that?

Driver arrival and detention guideNov 17, 202617 min read

Short answer

Agree with the customer on when they want the heads-up and who should get it. Before you send it, get a fresh ETA from the carrier or driver. Say the expected time, its source and who to call. Send a new note if the time moves. Wilson, by Cartage, an AI logistics agent, can check that ETA and send the heads-up by email or text where configured.

Book 15 minutes with the team →

How do you give a customer a heads-up before the truck arrives?

A distributor's receiving lead calls the plant at 1:30 p.m. A truck just showed up at her dock with 22 pallets. She has two people on the floor, one forklift free and another truck already unloading. "Next time, can someone tell us before it gets here?" She is not upset about the freight. She is upset that she found out when the driver walked in.

The logistics team had an ETA for that load. It came from the carrier's morning update. Nobody sent it to the customer, and nobody checked whether it still held.

To give a customer a heads-up before the truck arrives, agree with them on when they want notice and who gets it, check a fresh ETA from the carrier or driver shortly before that point, and send a short message with the expected time, its source, the load reference and a contact. If the time changes after that, send a second note. Save every message on the shipment, so the team can see what the customer was told.

This sounds simple. It fails in practice for three reasons. Nobody owns the task, so it happens only when someone remembers. The ETA used is old, so the heads-up is wrong. And the customer's preferences live in one person's memory, so they change from load to load.

Why customers ask for a heads-up

Receivers plan labor and dock doors. A known arrival time lets them staff the dock, clear a door and get the right equipment ready. For some customers, a heads-up also means they can move other deliveries, prepare paperwork or warn the production line that material is coming.

A heads-up also helps the shipper. When a receiver is ready, unloading is faster and drivers wait less. The American Transportation Research Institute found that detention happened at 39.3% of truck stops in 2023, with more than 135 million hours lost and $3.6 billion in direct costs. Not all of that is preventable, but a dock that knows a truck is coming is better placed to unload it on time.

What a heads-up is not

A heads-up is not a delivery appointment. If the receiver requires appointments, the appointment has to be booked separately, and the heads-up should match it. A heads-up is also not a promise that the truck will arrive at that minute. It is the best current estimate, with its source.

Where to start

Let's review which customers want a heads-up before delivery. You don't need to prepare anything: Cartage maps the workflow with you on the call.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

How should the heads-up workflow run, step by step?

A reliable heads-up has five steps: record the customer's preference, track the load, check the ETA at the trigger point, send the message and follow up if the time moves. Each step needs an owner.

Step 1: Record the customer's preference

Each customer that wants notice should have a short rule on file. It answers:

  • How much notice? Some receivers want a morning-of note. Others want a note a set number of hours before arrival.
  • Who gets it? A named receiving contact, a shared receiving email or a phone number for text messages.
  • Which channel? Email, text or both.
  • Which loads? All deliveries, only truckload, only loads to one site, or only loads with an appointment.
  • What to include? PO number, pallet count, carrier name, trailer number, driver contact, or the appointment number.

Keep the rule with the customer's delivery location, not in someone's inbox. When a new person handles the load, the rule should be visible without asking.

Step 2: Track the load to the trigger point

Before the heads-up goes out, the team needs a current picture of where the load is. That picture can come from several places:

  • The carrier's API or EDI status messages.
  • GPS or ELD location data, when the carrier shares it.
  • The carrier's website, using the PRO number for LTL.
  • An email or phone call to the carrier's dispatch.
  • A call or text to the driver, when the team has the driver's number.

Use the best source available for that load. A GPS ping from ten minutes ago is better than a dispatch estimate from this morning. A driver who says "I'm 40 minutes out" is better than a portal status that says "in transit".

Step 3: Check the ETA at the trigger point

When the trigger time comes, confirm the ETA. Do not reuse the morning number. If the source is old or vague, ask for a fresh one. If the carrier only says "today", ask a more specific question: "What time will the driver arrive at the receiver? Is the driver on schedule from the last stop?"

Step 4: Send the heads-up

Send a short, plain message. A hypothetical example:

"Heads-up: PO 48812, 22 pallets, is expected at your Dock 3 at about 1:30 p.m. Central today. Source: driver confirmed by phone at 10:40 a.m. Carrier: [carrier], trailer 5531. Questions: logistics desk, [phone]."

The receiver gets what they need to plan, and they know how firm the time is.

Step 5: Follow up when the time moves

If the ETA moves after the heads-up, send a second note. Most receivers care about changes of more than a set window, for example 30 minutes or an hour. Agree on that window as part of the customer's preference. Do not send a stream of small updates. Send the ones that change what the receiver will do.

Who owns each step

Step Owner Common failure
Record the preference Customer service or logistics manager The rule lives in one person's head
Track the load Load owner Status checked once in the morning, never again
Check the ETA Load owner The old estimate is reused
Send the heads-up Load owner or customer service Sent to the wrong contact or not sent at all
Follow up on changes Load owner Customer learns about the delay from the driver

Which ETA should the heads-up use, and how firm is it?

Use the freshest, most direct ETA you can get, and say where it came from. The source tells the receiver how much to trust the time.

Ranking the sources

Not every ETA is equal. A rough order from most to least direct:

  1. The driver, by phone or text, recently. The driver knows where the truck is and whether there is a stop or a break ahead.
  2. GPS or ELD location data, recently updated. It shows where the truck is, but the team has to estimate drive time and stops.
  3. The carrier's API or EDI status, recently updated. Often good, but some carriers update only at milestones.
  4. The carrier's dispatch, by email or phone. Dispatch may be estimating from the plan, not from the truck.
  5. The carrier's website by PRO number. Useful for LTL, but terminal updates can lag.
  6. The original appointment or plan. Only an intention, not a location.

The right source depends on the load. For a truckload with a driver's number, a short call is often the best answer. For LTL that goes through terminals, the carrier's tracking and a delivery-day check with the terminal may be all there is. The guide on what happens to the customer's ETA when an LTL load moves between terminals covers that case.

LTL versus truckload

Heads-ups work differently by mode:

  • Truckload: one truck, one driver, often a direct route. The ETA can be fairly precise once the driver is on the way.
  • LTL: the freight goes through terminals and rides on a delivery truck with other stops. The carrier may know only the delivery day, and a narrower window comes from the terminal or the driver on delivery day.
  • Parcel: the carrier's own notices are usually the heads-up, and the shipper adds little.

Tell customers what to expect by mode. A receiver who gets a precise time for truckload may expect the same for LTL. Set the expectation once, and the follow-ups make sense.

Email or text: which channel fits

The channel changes how the message should read.

  • Email suits a receiving team with a shared inbox and a desk. It can carry more detail: PO numbers, pallet counts, the appointment number and a link back to the load reference. It is also easy to forward to the person on the floor.
  • Text suits a receiving lead who is on the dock, not at a desk. It should be one or two short lines: the reference, the time and the source. Anything longer gets skipped.

Some customers want both: an email the day before and a text when the truck is close. That works if both messages come from the same record, so the time in the text and the time in the email never disagree.

Whatever the channel, give the receiver a way to answer. A heads-up often triggers a reply: "Dock 3 is full, can the driver go to Dock 5?" or "We close at 3:00 today." Those replies change the load. They should reach the load owner and be saved on the shipment, not sit in a personal inbox.

Inbound loads need heads-ups too

The same idea works in the other direction. When the company is the receiver, its own warehouse wants to know when inbound trucks will arrive. The workflow is the same: a rule for who gets notice, a fresh ETA from the supplier's carrier and a second note when the time moves. Many teams set up heads-ups for customers first and only later realize their own dock has the same problem.

Checking before you tell the customer

A heads-up that turns out wrong costs trust. If the source is weak, check it before sending. The article on verifying with the carrier before you update a customer's ETA explains how to do that check quickly. If the carrier goes quiet, the article on following up on a stale ETA covers the next steps.

When the driver's number is available

A direct line to the driver is often the fastest way to a firm time. Keep the call short and specific: confirm the load, ask where the truck is, ask for an arrival time, and ask if anything will slow the truck down. Write down what the driver said and when. Respect the driver's time and safety: a text that can be answered at the next stop may be better than a call.

What goes wrong with customer heads-ups?

Most heads-up failures come from missing ownership, stale ETAs, the wrong contact or no follow-up. Each one has a simple fix.

Mistake 1: Nobody owns it

When the heads-up is "something we try to do", it gets skipped on busy days, which are the days receivers need it most. Make it a step on the load, with an owner and a time.

Mistake 2: Sending the morning ETA in the afternoon

The ETA from the morning check call may be hours old by the time the heads-up goes out. Check again at the trigger point.

Mistake 3: Sending to the buyer instead of the dock

The person who placed the order is often not the person who runs the dock. A heads-up to a purchasing inbox may never reach receiving. Ask for the receiving contact.

Mistake 4: No second note when the time moves

A heads-up that says 1:30 p.m. and a truck that arrives at 4:00 p.m. with no update can be worse than no heads-up. The receiver held a door and staff for nothing.

Mistake 5: Promising what the carrier has not confirmed

"The truck will be there at 1:30" sounds firm. "Expected at about 1:30, confirmed by the driver at 10:40" is honest. Avoid language that turns an estimate into a promise.

Mistake 6: Mixing the heads-up and the appointment

If the receiver requires an appointment, a heads-up does not replace it. If the ETA falls outside the appointment, the team has a different problem: the appointment needs to move, or the carrier needs to make it. See what to do when a delivery appointment changes for that workflow.

Mistake 7: Not keeping a record

If the customer later says they were not warned, the team should be able to show the message, the time sent and the recipient. Save every heads-up on the shipment.

A short decision guide

Situation What to do
Customer wants notice, ETA is fresh and direct Send the heads-up with time and source
Customer wants notice, ETA is old or vague Ask the carrier or driver for a fresh time first
ETA moved after the heads-up by more than the agreed window Send a second note with the new time and reason if known
ETA falls outside the delivery appointment Tell the team, contact the carrier and the receiver about the appointment
Carrier cannot give a time, LTL delivery day Send a delivery-day notice and say a narrower time is not available yet
No receiving contact on file Ask the customer before the next load, and send to the order contact this time

What checklist should you use to set up customer heads-ups?

Set up the heads-up once per customer and delivery location, then let the rule drive each load. This checklist covers the setup.

Item Question to answer Owner
Customer list Which customers and delivery locations want a heads-up? Customer service
Notice time How much notice does each one want? Customer service
Recipient Who receives it, by name, shared email or phone number? Customer service
Channel Email, text or both? Customer service
Load scope All loads, only truckload, only appointment loads? Logistics
Message content Which references: PO, pallets, carrier, trailer, appointment number? Customer service and logistics
ETA source Which source is checked before sending, by mode? Logistics
Driver contact Does the carrier share the driver's number on these lanes? Logistics
Change window How big a change triggers a second note? Customer service and logistics
Exceptions Who tells the customer when the load will miss the appointment? Logistics
Record Is each heads-up saved on the shipment? Logistics
Review Who checks each month whether heads-ups went out and were accurate? Logistics manager

How to roll it out

Start with the customers who ask most often, or whose docks are hardest to schedule. Set up the rule, run it for a few weeks and ask the receiving leads one question: did the heads-up help? Adjust the timing, the contact or the content, then add more customers.

What to measure

  • Share of loads for these customers where a heads-up went out on time.
  • How far actual arrivals were from the heads-up time.
  • Receiver complaints about surprise arrivals.
  • Driver waiting time at these receivers, if detention records show it.

How does Wilson, by Cartage, handle heads-ups before delivery?

Wilson, by Cartage, is an AI logistics agent that tracks each load with the best source available, follows up with carriers until it gets an answer, and sends updates to customers and consignees by email or SMS where configured. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

The labor

The labor behind a heads-up is the checking and the follow-up. Wilson tracks each load using the best source available for it: carrier API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, and email or phone calls when nothing else is current. It follows up with carriers persistently, by phone and email, with persistence rules per carrier. Wilson usually talks to the carrier's dispatch, and it can call or text a driver directly when it has the driver's number.

When a load runs late or misses its time, Wilson contacts the carrier, tells the team, and tells the customer if configured. When a carrier's change affects the delivery date, Wilson brings it to the team, updates the expected date on the shipment and leaves the agreed date unchanged until the team decides.

What Wilson sends to customers and when follows the setup the company configures. The exact trigger and content of a heads-up are set during onboarding; confirm the details for your customers in discovery.

The data

The data is where the heads-up rules and the record live. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. It keeps rules and preferences, such as "this customer's dock wants notice before arrival", learned from its own work or added by the team, and the team can edit them. Every message, confirmation and change stays in the shipment's change history, so the team can show what the customer was told and when. Wilson replaces the TMS for freight execution and connects to the company's ERP.

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.

The network

The network gives better freight rates on every lane, because the shipper's volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight.

The payments

The payments close the load. Wilson requests and files the POD, audits each carrier invoice against the rate confirmation and the POD, and pays carriers from the Wilson Wallet. A detention line on the invoice is checked against the load record. Invoices over the rate or outside the rules wait for a person.

Control

Teams reach Wilson by email, Slack, Microsoft Teams, SMS, WhatsApp or phone. Control starts with assisted execution: the company sets approval limits, and routine actions run automatically within those rules as the workflow is proven. Timing depends on scope: most teams start on a few lanes and expand from there.

Pricing

Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

FAQs

Can Wilson tell our customer before the truck arrives?

Wilson, by Cartage, an AI logistics agent, tracks each load with the best source available and sends updates to customers and consignees by email or SMS where configured. The trigger and content of each customer's heads-up are set up with the team. Every message is kept in the shipment's change history.

How much notice should a heads-up give?

Ask the receiver. Some want a morning-of note, others want notice a set number of hours before arrival. The right answer is the time they need to staff the dock and clear a door.

Can Wilson call the driver to get a better ETA?

Wilson usually talks to the carrier's dispatch, and it can call or text a driver directly when it has the driver's number. Otherwise it uses the carrier's tracking data, website or dispatch.

Does a heads-up replace a delivery appointment?

No. If the receiver requires an appointment, it must be booked separately. The heads-up should match the appointment, and any gap between them is a separate problem to solve with the carrier and the receiver.

What should a heads-up say?

The load reference, the expected arrival time with its time zone, where the time came from, the carrier and trailer if useful, and who to call with questions. Keep it short.

What if the ETA changes after we send the heads-up?

Send a second note when the change is big enough to matter to the receiver. Agree on that window with the customer, so they get the changes that affect their plan and not every small shift.

Can we give a precise heads-up on LTL loads?

Often only the delivery day is known until the freight is on the delivery truck. A narrower time may come from the terminal or the driver on delivery day. Tell the customer what to expect by mode.

Does a heads-up reduce detention?

It can help, because a receiver who knows a truck is coming can prepare a door and staff. Detention also depends on the receiver's capacity and appointment rules, so a heads-up is one part of the answer.

Who should own the heads-up on our team?

The person who owns the load is usually best placed, because they know the latest ETA. Customer service can own the customer's preferences. Write both down.

Can the heads-up go by text message?

Yes, if the customer prefers it. Wilson can reach customers and consignees by email or SMS where configured.

Sources

Let's review which customers want a heads-up before delivery. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google