The National Retail Federation forecasts 2026 holiday retail sales of about $1.013 trillion, up 4.2%, with 325,000 to 375,000 seasonal hires (NRF, Oct 15, 2026), and that volume will move on a truck market where tender rejections are running near 13.75% (FreightWaves, Oct 9, 2026). Delays are coming. Shippers know that. What damages relationships during peak is not the delay itself but finding out late, or finding out by calling. The fix is a communication cadence decided in advance: milestone updates, exception-first alerts and ETA changes sent before the customer has to ask.

What does the 2026 holiday forecast mean for freight?

The NRF forecast puts holiday sales above $1 trillion for the season (NRF, Oct 15, 2026). Online spending will be heavy at the usual peaks; Adobe forecasts $15.1 billion in online spending on Cyber Monday alone (Adobe, Sep 29, 2026). Seasonal hiring in the 325,000 to 375,000 range signals retailers expect to staff warehouses and stores for that demand.

On the truck side, rejections near 13.75% (FreightWaves, Oct 9, 2026) mean more than one in eight contract tenders is being turned down. Each rejection is a load that has to be re-tendered or moved to the spot market, and each re-tender adds time. For shippers, that shows up as later pickups, changed carriers and ETAs that shift.

None of this is unusual for peak. What is different is the combination: high retail volume, a tight truck market and customers who have less patience for silence than they did a few years ago.

Why is silence the biggest shipper complaint during peak?

Silence is the biggest complaint because it forces the shipper to do the work. When a load is late and nobody says so, the shipper's planner finds out from the DC, calls the broker, waits on hold or waits for an email reply and then has to explain the delay internally without details.

Every one of those calls is also a cost for the broker or 3PL. Status requests flood the inbox during peak, which we covered in our triage rules for the Q4 email flood. Answering "where is my load?" for the fifth time in a day takes time away from fixing the load.

Over a season, silence also costs customers. Our framework for stopping 3PL customer churn with visibility makes the case that shippers rarely leave over a single late load. They leave over a pattern of finding out late.

What does a good shipper-update cadence look like?

A good cadence tells the shipper what they need at the moments they need it, and nothing more. It has three layers.

1. Milestone updates. A short message at the moments that matter: carrier assigned, picked up, in transit with ETA, delivered with POD. Agree the milestones with each customer before peak. Some want every one; others only want pickup and delivery.

2. Exception-first alerts. When something goes wrong, the alert goes out before the milestone is missed. A carrier falls off, a pickup slips, weather affects a lane, a driver reports a breakdown. The alert says what happened, what you are doing and the new expected time.

3. ETA changes before they're asked. If the ETA moves by more than an agreed threshold, the shipper hears about it immediately. The threshold might be two hours for a retail DC appointment and half a day for a less time-sensitive lane.

• Milestone — Trigger: Status change in the TMS · What the message includes: Load reference, status, current ETA
• Exception — Trigger: Carrier, driver or appointment issue · What the message includes: What happened, action taken, new ETA
• ETA change — Trigger: ETA moves past agreed threshold · What the message includes: Old ETA, new ETA, reason

We applied the same structure to a disruption in our playbook for proactive customer updates during Hurricane Isaias. Peak is a slower, longer version of the same problem.

How do you run this cadence at peak volume?

You run it by letting agents send the routine updates and keeping people on the exceptions. A team cannot manually send three layers of updates on every load during peak. An agent can, because the triggers are already in your systems.

• Watch status and tracking data per load. When a milestone hits, the agent sends the update in the channel the customer prefers: email, portal, SMS or WhatsApp.
• Recalculate ETAs continuously. When tracking data or a driver check-in moves the ETA past the customer's threshold, the agent sends the change with the reason. Real-time tracking that ends "where's my load?" messages is the subject of our post on making the "where's my package" question obsolete.
• Answer inbound status questions instantly. When a shipper emails asking about a load, the agent replies with current status and ETA, and escalates only if there is an open exception.
• Route exceptions to a person with context. The rep gets the load, the problem, what the customer has already been told and the options. Our operator's guide to automating track-and-trace exceptions covers how to set those handoffs up.

What should you set up before November?

Peak starts in a few weeks. Use the time to set the rules, not to build from scratch:

1. Confirm update preferences with your top customers. Which milestones, which channel, which ETA threshold.
2. Write the exception templates now. Carrier fall-off, missed pickup, weather delay, appointment change. Keep each to three sentences.
3. Set the escalation rule. Decide which exceptions a rep must handle personally, such as anything affecting a retail appointment.
4. Measure inbound status requests. Count them per customer this week, then again in December. If the cadence works, the number falls.

Frequently asked questions

What is the NRF 2026 holiday sales forecast? NRF forecasts 2026 holiday retail sales of about $1.013 trillion, up 4.2%, with 325,000 to 375,000 seasonal hires (NRF, Oct 15, 2026).

How tight is the truck market heading into peak? Tender rejections were running near 13.75% in early October (FreightWaves, Oct 9, 2026), meaning more than one in eight contract tenders was declined.

How often should brokers update shippers during peak? At agreed milestones, immediately when an exception occurs and whenever the ETA moves past a threshold the customer has set.

Can AI agents send shipment updates automatically? Yes. Agents can watch status and tracking data, send milestone and ETA-change updates in the customer's preferred channel, answer status questions and route exceptions to a rep with context.

The bottom line

A trillion-dollar holiday on a tight truck market will produce delays. Agree milestones and ETA thresholds with each customer, send exception alerts before the miss and let agents handle routine updates and status questions, so your shippers hear about problems from you first.

Debales deploys AI agents for milestone updates, ETA change alerts, exception handling and inbound status requests across email, SMS and WhatsApp. Book a demo.