How do you coordinate deliveries to 164 locations without adding coordinators?

Key Takeaways

Coordination grows with locations, not just loads. Every new consignee brings its own contacts, receiving rules and paperwork expectations.
Put the rules on the location, not in someone's memory. A location record with contacts, notification rules and appointment requirements lets every load to that address run the same way.
Appointments, ETAs and PODs are where follow-up piles up. Each one needs a trigger, a channel and an escalation point for when the carrier goes quiet.
Wilson, by Cartage, is an AI logistics agent that runs those follow-ups on every shipment, notifying the contacts set for each order and collecting the POD after delivery.

What does coordinating 164 delivery locations actually require?

You coordinate deliveries to 164 locations without adding coordinators by moving per-location knowledge out of people's heads and into rules attached to each delivery location, then having an agent execute the follow-up those rules call for. The coordinator's job shifts from chasing every appointment, ETA and POD to handling the exceptions the rules can't settle.

The hard part isn't the number of trucks. It's that each consignee (the party receiving the shipment) has its own receiving hours, its own contact who needs the ETA and its own idea of when a delivery is done. A coordinator with ten regular customers can remember those details. At 164 locations, nobody can.

Why does every new location add coordination work?

A repeat lane gets easier with each load. The carrier knows the dock, the receiver knows the carrier and the coordinator knows who to call. A new delivery location resets all of that, so the first load to any address carries the most questions.

For building materials, those questions are concrete:

Does the site require a delivery appointment, and how far in advance?
Who on site receives the load, and who at the customer's office wants the update?
Are there receiving hours, a call-ahead requirement or equipment needs such as a liftgate?
Who signs the POD (proof of delivery, the signed record that the consignee received the freight), and how fast does billing need it?

When the answers live in old email threads, each load to that location means digging them up again. That's where coordinator time goes, and it grows with every location added, even when total volume stays flat.

What should each location record hold before the first load ships?

Set up each delivery location once, with the details every future load will need. The table below is a starting point; your team decides which fields are required.

Field	Why it matters	Who usually owns it
Receiving contact (name, email, phone)	Gets pickup, delay and delivery updates	Customer service or sales
Office or buyer contact	Wants ETA changes, not every status	Sales
Notification rules	Which updates go to whom, on which channel	Logistics lead
Appointment requirement	Whether the carrier must set a delivery time	Logistics
Receiving hours and site notes	Prevents arrivals at a closed gate	Customer or sales
POD expectation	Who signs, and when billing needs it	Finance or customer service

Notification rules deserve the most care. Shipment status should follow the contacts tied to that shipment, so people get only the updates configured for their order and role. A job-site receiver may want "running late" and "delivered" by text. A purchasing contact may only want "delivered" and the POD by email.

Sending every update to everyone creates noise. Across many customers, it also creates the risk of one customer's shipment status landing in another customer's inbox.

How do you keep appointments, ETAs and PODs moving across many consignees?

Give each follow-up a trigger, a channel and an escalation point, and run it the same way on every load. Consistency is what lets one team cover many locations.

Delivery appointment. If the location requires one, confirm the time with the carrier at booking and reconfirm it before delivery. If it changes, the receiving contact needs to know before the truck arrives.
ETA. Check status at a set frequency. When a load runs late, get the new ETA (estimated time of arrival) and the reason, then tell the people set to be notified for that location.
Delivery confirmation. Confirm the load arrived and send the “delivered” update to the contacts who asked for it.
POD. Request the POD after delivery, follow up until it arrives, file it on the shipment and escalate if it’s still missing past the window you set.

The failure pattern is predictable: step 4 slips first, because it happens after the truck leaves and nobody is waiting at a dock for it. For more on that, see when to chase a missing POD. When a delivery time moves, the carrier has to hear it too, which what to do when a delivery appointment changes covers.

How does Wilson, by Cartage, carry the per-location work?

Wilson, by Cartage, is an AI logistics agent that executes freight coordination for manufacturers and distributors, from quote to payment. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

For multi-location delivery work, that means:

Notifications by contact and role. Wilson tells the consignee when the load is picked up, running late, delivered and POD filed, by email or SMS. The team gets those updates plus "booked," in Slack or Microsoft Teams. Each company chooses who's notified and how.
Appointments and ETAs. Wilson calls carriers and drivers for check calls, pickup and delivery appointments and ETA follow-ups, at the frequency set in the company's SOP. When a load runs late, it gets the new ETA and the reason. Wilson coordinates delivery times with carriers; it doesn't manage dock slots inside a facility.
The best tracking source for each load. Wilson uses the carrier's API, GPS or ELD data, or the carrier's website by PRO number, and emails or calls when none of those exist. Customers can follow their loads on a tracking link with the shipper's branding.
POD collection. Wilson requests the POD after delivery, follows up until it's received, files it and escalates if it's still missing past the set window.

Every message, confirmation and call transcript is recorded in the shipment's change history. A coordinator who picks up an escalation can see what was already said to that location, and to whom.

What this looks like at a wood products shipper

Since May 2026, one wood products company has used Wilson to coordinate 221 shipments across 164 delivery locations. With nearly as many locations as shipments, there's little repetition to lean on: many loads go to an address the team has rarely shipped to before. That's where per-location contacts and notification rules matter most, because the setup has to be right before the load ships instead of being learned over many trips.

FAQs

Do we need an appointment rule for every location? No, only for locations that require one. Mark the requirement on the location so the carrier is asked for a delivery time on every load going there.
Can two contacts at the same customer get different updates? Yes. Each company chooses who's notified and how, so a site receiver and a buyer can get different updates on different channels.
What happens when a carrier doesn't answer an ETA request? If a carrier doesn't respond with an update, Wilson calls. If it still can't get one, it escalates to the team.

The test for your own delivery network

Ask whether a load to a location you've shipped to once runs as cleanly as a load to your busiest customer. If it depends on who remembers the receiver's phone number, coordination will keep growing with your customer list. Pick five of your least frequent delivery locations and map their contacts and appointment rules with our team.

Sources