Supply chain visibility software: who should receive each customer alert?
Key Takeaways
Each customer alert should go to the person at the customer who will act on it: receiving staff for dock times, buyers or planners for delays, and the account owner for major problems. Supply chain visibility software should support a contact map per customer, and an AI logistics coordinator should send only verified, useful alerts to each contact.
- A customer alert is a message to the buyer or receiver about a shipment's status, such as shipped, delayed, or delivered.
- Different people at the customer need different alerts. Sending everything to one email address wastes their time.
- Receiving teams care about arrival times and appointments. Buyers and planners care about delays that affect their stock or production. Accounts payable cares about invoices and proof of delivery.
- Alerts should be verified before they go out, so customers are not told a time that later changes.
- Each customer's contact map should be set up once, kept current, and reviewed when contacts change.
- Wilson, by Cartage, is an AI logistics coordinator that can notify consignees by email or SMS where configured and informs internal teams through channels such as Slack, Microsoft Teams, or email.
Why does it matter who receives each customer alert?
It matters because an alert only helps if it reaches someone who can act on it. An AI logistics coordinator should route each customer alert to the role that makes the related decision, so the message changes what the customer does instead of adding to its inbox.
Many shippers send every shipment message to one customer contact, often the buyer who placed the order. The buyer may not run the dock. The receiving supervisor never hears that the truck will be three hours late. The truck arrives, waits, and the carrier bills detention. Detention is a fee a carrier charges when its truck waits too long at a dock. A message sent to the right person would have moved the appointment.
The table below shows common customer roles and what each needs.
| Customer role | What they decide | Alerts they need |
|---|---|---|
| Receiving or dock supervisor | Dock doors, labor, appointment times | Arrival time, delays affecting the appointment |
| Buyer or purchasing | Order follow-up, alternatives | Shipped, major delay, partial shipment |
| Planner or production scheduler | Production runs, inventory plans | Delays that change availability |
| Account manager or main contact | Relationship, escalations | Major problems, repeated issues |
| Accounts payable | Invoice approval | Delivery confirmation, POD for billing |
A POD, or proof of delivery, is the signed record that the receiver took the freight.
Internal alerts and customer alerts are different
Internal alerts help the shipper's team act. Customer alerts help the customer plan. An internal alert may say "carrier not answering; second follow-up sent." A customer alert should wait until there is a verified fact to share. An AI logistics coordinator should keep the two streams separate, so the customer sees outcomes and the internal team sees the work in progress.
The customer's view of noise
Customers receive messages from many suppliers. A supplier that sends ten messages per order trains the customer to ignore all of them. A supplier that sends two useful messages to the right people becomes easy to work with. An AI logistics employee should treat the customer's attention as limited and use it only when the message matters.
The cost of the wrong recipient
Sending alerts to the wrong person has real costs. A late truck waits at a full dock and the carrier bills detention. A planner who never heard about a delay runs out of stock. A buyer who gets every message stops opening them, and misses the one that mattered. An AI logistics coordinator that routes alerts by role avoids these costs without sending more messages.
Consignee versus customer
The consignee is the party receiving the freight at the delivery address. Sometimes the consignee is the customer itself. Sometimes it is a warehouse, a job site, or a third-party logistics provider acting for the customer. A third-party logistics provider, or 3PL, is a company that runs warehousing or transportation for another company. Alerts about arrival times should go to the consignee's receiving team, even when the commercial customer is a different company.
What supply chain visibility software usually covers
Many supply chain visibility tools can send status messages to email lists. The harder part is choosing the right recipients, deciding which events matter, and verifying the information first. An AI logistics coordinator adds that judgment within the customer's rules.
Which customer alerts should exist, and who gets each one?
A small set of alerts covers most needs: shipped, appointment confirmed, delay with a new time, delivered, and exception. An AI logistics coordinator should map each alert to one or two roles at the customer.
A customer alert map
| Alert | When it fires | Who receives it | Channel example |
|---|---|---|---|
| Shipped | Carrier picks up the freight | Buyer | |
| Appointment confirmed | Delivery appointment set or changed | Receiving supervisor | |
| Delay with new time | Verified ETA misses the window | Receiving supervisor and buyer | Email or SMS where configured |
| Delivered | POD received | Buyer, accounts payable if requested | |
| Exception | Damage, shortage, refusal, or major delay | Account contact and buyer | Email, plus a call from the account owner |
These are examples. Each customer may want a different set. Some want no shipped alert. Some want an SMS to the dock 60 minutes before arrival.
Alert timing by customer
Customers differ in how much warning they need. A distribution center with tight appointments may want a delay alert as soon as a verified ETA misses the slot. A job site may want an SMS one hour before arrival. A small retailer may want only a delivered alert. The contact map should store each customer's timing. An AI logistics employee can then send the same event at different times to different customers.
Shipped alerts
A shipped alert tells the buyer the order left. It should include the carrier, a tracking or PRO number, and the expected delivery date. A PRO number is the tracking number an LTL carrier assigns. The alert should go out after pickup is confirmed, not when the load is booked.
Appointment and arrival alerts
Receiving teams plan around appointments. An alert should confirm the appointment and warn if it is at risk. Many receivers prefer a short message on the day of delivery. An AI logistics employee can send it to the receiving contact the customer named.
Partial shipment alerts
When an order ships in parts, the customer needs to know what is coming and what is not. A buyer who expects 20 pallets and receives 14 will call unless told. A partial shipment alert should list what shipped, what remains, and when the rest will ship if known. An AI logistics coordinator can send it to the buyer at pickup, so the receiver is not surprised at the dock.
Delay alerts
A delay alert should come with a verified new time and a short reason. A message that says only "delayed" causes calls. A message that says "now arriving Thursday 10 a.m., confirmed with the carrier at 3 p.m., weather delay" lets the receiver re-plan.
Delivered and POD alerts
A delivered alert is most useful after the POD confirms delivery. Sending "delivered" on the carrier's scan, before the POD, can mislead if the delivery was short or refused. Some customers want the POD attached for accounts payable.
Customer-specific requirements
Some customers set their own rules. A retailer may require an advance ship notice, a message sent before delivery that lists what is on the truck, through its own system. A customer may require appointment requests through a portal. An AI logistics employee should follow these rules where the setup supports them, and the contact map should note them so nobody has to remember each customer's requirements.
Exception alerts
Exceptions such as damage, shortage, or refusal need a person on the shipper's side. The AI logistics coordinator should notify the account owner internally first. The account owner decides how and when to tell the customer, unless the team has set a rule for routine exceptions.
How should a customer contact map be set up and maintained?
Set up a contact map for each customer during onboarding, with names, roles, alert types, and channels, and review it when contacts change. An AI logistics coordinator should read the map for every alert and flag gaps, such as a delivery address with no receiving contact.
One map per ship-to location
Large customers often have many delivery locations, each with its own dock and staff. A national retailer may have dozens of distribution centers. The contact map should hold a receiving contact for each location the shipper delivers to. An AI logistics employee can read the ship-to address on each order and choose the matching contact.
What the contact map includes
- Customer and delivery locations. Each ship-to address can have its own receiving contact.
- Roles and names. Buyer, receiving, planner, account contact, accounts payable.
- Alert types per role. Which alerts each person receives.
- Channels. Email, SMS, or a portal, as the customer prefers and the setup allows.
- Hours. When the customer wants messages, especially SMS.
- Language and format preferences. For example, a one-line SMS for receiving.
Who on your team owns the map
Someone on the shipper's side should own each customer's contact map. Usually that is customer service or the account manager. They know the customer and hear about changes first. An AI logistics coordinator uses the map but should not invent contacts. When a contact is missing, it asks the owner.
Collect the map from the customer
The best source of the map is the customer. A short form or email asking "Who should hear about deliveries to your Atlanta warehouse?" usually gets a clear answer. Sales or customer service can collect it during onboarding. An AI logistics employee can then use it on every order.
Start with your largest customers
Building contact maps for every customer at once is a large project. Start with the customers that receive the most freight or complain the most about delays. Their maps deliver the most value. An AI logistics employee can use a simple default for the rest, such as alerts to the buyer only, until each map is built.
Keep the map current
Contacts change. A receiving supervisor leaves; a buyer moves to a new role. Bounced emails and wrong-person replies are signs the map is out of date. The AI logistics coordinator should flag bounces and replies such as "I no longer handle this" so a person can update the map.
Ask what each contact wants
When collecting contacts, ask each person which alerts they want and how. A receiving supervisor may want only same-day arrival alerts by SMS. A buyer may want a weekly summary instead of individual messages. An AI logistics coordinator can follow each preference, which makes every alert more likely to be read.
Default routes for missing contacts
When a delivery address has no receiving contact, the alert needs a default. Often the default is the buyer, with a note asking for a receiving contact. A default is better than silence, but it should prompt a fix.
Alerts for customer-routed shipments
Some customers arrange their own freight and send their own carrier to pick up. These are often called customer-routed shipments. The shipper may still want to tell the customer when the freight is ready and when it was picked up. The contact map should note which customers route their own freight and who should hear about pickup readiness. An AI logistics coordinator can send those messages within the agreed scope.
Privacy and data boundaries
Shipment alerts should go only to people at the customer who are entitled to see them. A distributor shipping to two competing retailers should never send one retailer's shipment details to the other. The contact map should be tied to the customer and location on each order. An AI logistics coordinator should check that the recipient belongs to the order's customer before sending.
Hypothetical example: the dock never knew
This example is hypothetical and does not describe a real customer. A beverage distributor sends all alerts to a grocery chain's buyer. The buyer receives a delay alert at 2 p.m. and does nothing, because the buyer does not schedule docks. The truck arrives three hours late, the dock is full, and the driver waits two hours. The carrier bills detention.
The distributor adds the receiving supervisor for that warehouse to the contact map for arrival and delay alerts. The next month, a similar delay alert reaches the supervisor, who moves the appointment. The truck unloads on arrival.
What makes a customer alert worth sending?
A customer alert is worth sending when it is verified, specific, and changes what the recipient will do. An AI logistics coordinator should hold back alerts that are uncertain, trivial, or repeated.
Tone matters
Customer alerts speak for the shipper. They should be polite, plain, and honest. A message that admits a delay and gives a real time is better than one that hides it. A message that blames the carrier in front of the customer can sound like an excuse. An AI logistics coordinator should use a neutral, helpful tone that the account owner has approved.
Verified before sent
An alert based on an unverified ETA can be wrong. If the customer re-plans around it and the time changes again, trust drops. The AI logistics employee should confirm the time with the carrier before sending a delay alert, or label it clearly as unconfirmed when timing is urgent.
Specific enough to act on
A good alert names the order, the location, the time, and the reason. For example: "PO 44812 to your Dallas DC: arrival now Wed 10:30 a.m., not Tue 4 p.m. Confirmed with the carrier at 1:15 p.m. Please confirm a new dock slot." The receiver knows what to do.
Include a contact for questions
Every customer alert should say whom to contact with questions. A name and email, or a team inbox, saves the customer from guessing. An AI logistics coordinator can include the account's contact line in each message.
Thresholds to avoid trivial alerts
Set thresholds so small changes do not trigger messages. A 15-minute shift within a four-hour window does not need an alert. A shift that misses the appointment does. An AI logistics coordinator can apply thresholds by customer.
Let the customer reply
Customer alerts should accept replies. A receiver may reply "Can you deliver at 8 a.m. instead?" or "Wrong contact, send to Maria in receiving." The reply should reach someone who can act. An AI logistics employee can read replies, act on routine ones within the rules, and pass the rest to the right person on the shipper's team.
Limit repeats
If the ETA changes several times in an hour, send one message with the latest verified time, not several. Customers prefer one correct update to a stream of corrections.
Common mistakes with customer alerts
- Sending every carrier event. Customers stop reading.
- Sending to one generic address. The right person never sees it.
- Sending "delivered" before the POD. Shortages are hidden.
- Sending unverified times as facts. Customers re-plan twice.
- Sending exceptions with no human contact. Serious problems feel automated and cold.
Hypothetical example: alerts for accounts payable
This example is hypothetical and does not describe a real customer. A packaging manufacturer's large customer pays invoices only with a POD attached. Its accounts payable team kept asking for PODs by email. The manufacturer adds the customer's accounts payable address to the contact map for delivered alerts with the POD attached. Payment questions drop, and invoices are paid on the normal schedule.
Hypothetical example: one useful SMS
This example is hypothetical and does not describe a real customer. A building materials supplier delivers to construction sites. Site supervisors do not read email during the day. The supplier's contact map lists the supervisor's mobile number for arrival alerts. An hour before arrival, the AI logistics coordinator sends a one-line SMS: "Lumber delivery for Oak St. site arriving 10:15 a.m., truck 52." The supervisor has a forklift ready. Unloading takes 20 minutes instead of an hour.
How should you evaluate visibility software on customer alerts?
Evaluate visibility software by setting up two customers with different contact maps and triggering the same events for both. An AI logistics coordinator should send the right alerts to the right people at each customer, with verified details.
Demo tests for customer alerts
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Contact map per customer | Set different roles for two customers | Each gets alerts per its map |
| Per-location contacts | Ship to two locations for one customer | Each location's receiving contact gets arrival alerts |
| Verified delay alerts | Change the ETA without confirmation | Alert waits or is labeled unconfirmed |
| Thresholds | Shift ETA by 15 minutes | No customer alert |
| Delivered after POD | Mark delivered without POD | No "delivered" alert yet |
| Exceptions go internal first | Add a shortage on the POD | Account owner notified before customer |
| Data boundaries | Use two competing customers | No cross-customer messages |
Demo questions about customer alerts
- How is the contact map stored for each customer and location?
- Which channels can customer alerts use?
- How does the AI logistics coordinator decide an alert is verified?
- Can thresholds vary by customer?
- How are bounced emails and wrong contacts flagged?
- How does the system prevent sending one customer's data to another?
Test a contact change
Ask the vendor to change a customer's receiving contact during the demo. Then trigger an alert. The new contact should receive it, and the old one should not. Contact changes are frequent in real life, and an AI logistics coordinator should apply them right away.
How to measure customer alert work
Track how many delay alerts reached the receiving contact before the original appointment. Count detention charges at customer docks before and after the change. Ask key customers whether the alerts help. These measures show whether the AI logistics employee's alerts change outcomes.
Ask a customer to review the messages
Before go-live, send sample alerts to one friendly customer and ask for feedback. Customers know which messages help and which they would ignore. An AI logistics coordinator can adjust thresholds and wording based on that feedback.
Scoring the customer alert demo
Score each test as pass, partial, or fail. A pass means the right person got a verified, specific alert. A partial means the alert was right but went to a generic contact. A fail means the customer got noise, wrong information, or another customer's data.
Warning signs in a customer alert demo
- One email list per customer, no roles.
- Every carrier event becomes a customer alert.
- "Delivered" goes out on the carrier's scan.
- No way to send SMS to receiving where needed.
- No checks on which customer a recipient belongs to.
Where does Wilson fit in customer alerts?
Wilson, by Cartage, is an AI logistics coordinator that tracks each load as part of executing it and informs the people who need to know. It can notify consignees by email or SMS where configured, and it sends internal updates through channels such as Slack, Microsoft Teams, or email.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. Its tracking uses the best source available for each load, including carrier APIs, GPS or ELD data where it exists, carrier websites, and email or direct outreach, including calls where configured. An ELD, or electronic logging device, records a truck's location and the driver's hours.
The communication pattern
In a typical setup, Wilson updates the shipper's internal team on key events such as booked, picked up, running late, delivered, and POD filed. The consignee can be notified on events after booking by email or SMS where configured. Wilson asks the carrier for status and informs the rest. Each customer's exact alerts and contacts are set during setup.
What Cartage asks about customer alerts in discovery
Cartage asks which customers want updates, which events matter to them, and who at each customer should hear. Typical questions also cover customers with strict appointments and those that prefer SMS. These answers shape the first contact maps an AI logistics coordinator uses.
What Wilson does not do for customer alerts
Wilson does not replace the account owner's relationship with the customer. Exceptions that need a personal call should go to a person. Specific alert types, thresholds, and channels should be confirmed in a demo for each customer. Exact ERP connection details depend on the customer's systems.
Where teams start with customer alerts
Most teams start their AI logistics coordinator on a few lanes and expand from there. Timing depends on scope. Cartage helps identify the first workflow during discovery. Teams often start with the customers that complain most about surprise delays.
Teams writing rules can read about late freight customer update rules. Teams sending ETAs can see why customer updates should carry a carrier-confirmed answer. Both topics shape the alerts an AI logistics coordinator sends. Teams concerned about data boundaries can review how shipment status data stays with the right customer.
FAQs
Who should receive each customer alert from supply chain visibility software?
Receiving staff get arrival and appointment alerts, buyers get shipped and major delay alerts, and the account owner handles exceptions. An AI logistics coordinator should follow a contact map for each customer and location.
Should customers get every tracking update?
No. Customers should get only verified alerts that change what they do. An AI logistics employee should apply thresholds and skip trivial changes.
When should a customer get a "delivered" alert?
After the signed POD confirms a clean delivery, or with a clear note if the POD shows an exception. An AI logistics coordinator should not rely on the carrier's scan alone.
How do you keep customer contacts up to date?
Collect them during onboarding and update them when emails bounce or recipients say they are the wrong person. An AI logistics employee can flag those signals for a person to fix.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator sends a verified delay alert to a customer's receiving supervisor, not just the buyer, using that customer's contact map: talk to the Cartage team.