Delivery status update email templates for freight brokers (pickup, in transit, delay, delivered)

Step 1: Decide which status changes trigger a delivery status update email

Don't email on every ping. Pick four moments and stick to them for every shipper:

• Picked up: the truck left the shipper's dock, with the delivery ETA.
• In transit: one midpoint update on multi-day loads, or a morning-of-delivery update.
• Delayed: only when the ETA slips past the delivery appointment.
• Delivered: with the delivery time and a note that the POD follows.

Ask big shippers once if they want a different rhythm. Some want an update every morning. Write their preference in the customer notes in your TMS so every rep sees it.

Step 2: Write the four status update email templates with AI

Paste this prompt into ChatGPT, Claude, Gemini or Copilot. It uses placeholders only, so no shipper or load data goes into the chat:

You write for a small US freight brokerage. Write four short email
templates a broker sends a shipper about a booked truckload:
1) Picked up: confirm pickup time and the delivery ETA.
2) In transit: current city/state and whether the ETA still holds.
3) Delayed: the new ETA, the reason in one plain line, and what we're
   doing about it (for example, rescheduling the receiver appointment).
4) Delivered: delivery time, and that the signed POD follows.
Blanks: [SHIPPER FIRST NAME], [LOAD #], [PO/REF #], [ORIGIN CITY],
[DESTINATION CITY], [PICKUP TIME], [CURRENT LOCATION], [ETA],
[NEW ETA], [DELAY REASON], [DELIVERY TIME], [REP NAME], [DIRECT LINE].
Rules: under 70 words each. Subject line starts with the load and
PO number. First sentence is the status. No apologies longer than
one sentence. No blame on the driver. Plain words.

Read every draft before you save it. Here's the shape the delayed email should take, because it's the one that matters most:

Subject: Load [LOAD #] / PO [PO/REF #]: new ETA [NEW ETA]

Hi [SHIPPER FIRST NAME],

Your load to [DESTINATION CITY] is running late. The new ETA is
[NEW ETA], because [DELAY REASON].

I've let the receiver know and asked to move the appointment.
I'll confirm the new time as soon as they reply.

[REP NAME]
[DIRECT LINE]

And the delivered email:

Subject: Load [LOAD #] / PO [PO/REF #]: delivered

Hi [SHIPPER FIRST NAME],

Delivered in [DESTINATION CITY] at [DELIVERY TIME]. I'll send the
signed POD as soon as the carrier uploads it.

Anything else on this one?

[REP NAME]

Step 3: Save the templates in Outlook or Gmail

In the new Outlook or Outlook on the web, start a new email, open Apps on the Message tab and choose My Templates. Click + Template, give it a title like "Status: delayed" and paste the text. My Templates holds plain text snippets, which is all these emails need.

In Gmail, open Settings > See all settings > Advanced, turn on Templates and save. Write each email in a new message, then choose More options > Templates > Save draft as template.

Now a rep can reply in the load thread, insert the template and fill four blanks in under a minute.

Step 4: Let your TMS or tracking app send the routine ones

Once the templates work by hand, move the routine updates into the systems you already pay for. Check your own version's help pages, since setups differ.

Tai TMS. Tai's workflow automation can trigger on a shipment status update, filter for a status such as In Transit or Out for Delivery, and use Send Email as the action. You choose the sender, the recipient and a content template. Paste your Step 2 wording into that template.

Aljex. Aljex notifications are managed from the bell icon, and its Descartes MacroPoint integration brings tracking updates into the load. Ask your Aljex rep which status changes can email a customer contact on your plan.

Revenova. Revenova runs on Salesforce, so a status email can be set up as a Salesforce automation on the load record. Ask your admin to trigger it when the load status changes.

MacroPoint. When you create or edit a tracked load, you can add the shipper's address to receive copies of updates. Pick the trip event and late alerts only. A location email every 15 minutes will bury your shipper.

Keep the delayed email manual. A person should confirm the reason and the new appointment before it goes out.

The same rhythm as a list:

• Pickup, confirm: picked up at [PICKUP TIME], ETA [ETA].
• Midway or morning of delivery, reassure: location and "ETA holds."
• Delay, own it: new ETA, one-line reason, what you're doing.
• Delivered, close: time delivered, POD to follow.

Example (illustrative): a four-person truckload brokerage

This is a walkthrough, not a client story. Picture a founder and three reps moving dry van loads in one TMS, with most shippers emailing in their orders.

Each rep replies in the shipper's order thread with the pickup template when the driver checks out. A TMS workflow sends the in-transit email on the morning of delivery. When a tracking alert shows a truck behind schedule, the rep confirms with the driver, then sends the delayed template by hand. The delivered email goes out when the status flips, and the POD follows.

At a glance

• Problem: shippers chasing reps for updates on booked loads.
• What was set up: four templates and one TMS workflow for routine statuses.
• Tools it lives in: the TMS, the tracking app and Outlook.
• What the owner still does: decides how delays are explained, handles any claims or detention talk.
• Payoff: not measured here. Count "where's my truck" emails for two weeks before and after.

Mistakes to avoid

• Sending a delay email before you know the new ETA. Call the driver or dispatcher first.
• Turning on every tracking notification. Location pings every few minutes teach the shipper to ignore you.
• Letting AI explain a delay or promise an appointment. That's a judgment call for your rep, not the AI.
• Starting a new email for each update. Reply in the load thread so the history stays together.
• Blaming the driver in writing. State the fact and the fix. Shippers forward these emails.

If it still doesn't work

If shippers still ask for updates, check who's getting them. The person who books the load is often not the person waiting at the dock. Ask once for the right contact and add them to the load.

If your TMS can't send emails on a status change, keep the templates in Outlook or Gmail and send them by hand at the same four moments. If a long carrier thread is hard to read before you update the shipper, have AI summarize it first.

Doing this inside the tools you already use

Deeplathe is a team of developers and solution builders who build custom AI inside the tools a business already uses. For this job, a custom build could watch the status of every booked load in your TMS and tracking app. It drafts each update in the shipper's original thread with the real load number, location and ETA, and holds anything that looks like a delay for your rep. Your reps approve the delay emails, the routine ones send from their own address, and every update is logged on the load.

You keep every promise to the shipper, and no load goes quiet. See how a custom build works.

FAQ

How often should a broker update shippers?

At four moments for most truckloads: pickup, once in transit, any delay and delivery. On multi-day loads, a morning update each day is common. Ask big shippers what they want and note it in your TMS. More emails aren't better. A predictable rhythm is what stops the "where's my truck" emails.

What should a delivery status update email say?

Start with the load and PO number in the subject. The first sentence is the status: picked up, in transit, delayed or delivered. Add the ETA or delivery time, and for a delay, one plain reason and what you're doing about it. Keep it under 70 words, sign with a direct line and reply in the load's thread.

How do you write a load delay email to a customer?

Send it as soon as you know the new ETA, not before. Give the new time first, then a one-line reason without blaming the driver. Say what you've done, like asking the receiver to move the appointment, and when you'll confirm. Keep it short and factual, because shippers often forward it to their own customer.

Can you automate shipment status update emails?

Partly. Tai TMS can send an email when a shipment status changes, and MacroPoint can email copies of tracking updates to an address you add on the load. Automate pickup, in-transit and delivered updates. Keep delay emails with a person, since the reason and the new appointment need checking first.

Keep these

• Four moments: pickup, in transit, delay, delivered.
• Status and ETA in the first sentence.
• Reply in the load thread.
• A person sends every delay email.

Sources

• Tai TMS Knowledge Base: Shipment Status and Alerts Workflows
• Tai TMS Knowledge Base: Consignee Upcoming Delivery Notices
• MacroPoint Academy: Email Notifications
• Microsoft Support: Create email templates in Outlook

Related reading

• Part of Quotes and leads you never followed up
• Summarize a long email thread with AI before you reply
• Project status update email template for customers
• Quotation follow-up email templates that win the order
• Use AI to draft customer emails and follow-ups that sound like you