Case snapshot
  • Business type: Regional food and beverage distributor, Netherlands, 8 staff, ~80 active B2B clients
  • Problem: Customers calling and emailing about delayed shipments they hadn't been warned about in advance
  • Agent type: Shipment monitoring + proactive communication agent
  • Platform used: Custom Python script + Aftership API + SendGrid
  • Monthly running cost: €48/month
  • Status: Running since October 2024

The problem with reactive communication

In B2B distribution, a delayed shipment isn't just an inconvenience — it's often a production or operational problem for the customer on the other end. A restaurant that doesn't receive a key ingredient on time can't serve a dish. A retailer whose product doesn't arrive before a planned promotion loses sales they've already marketed.

The distributor in this case was handling around 120 shipments per week. Their logistics team knew when delays were happening — carrier tracking data was available — but communicating that information proactively to customers was nobody's explicit job. It happened when someone remembered to do it, or when a customer called first.

What the monitoring agent does

The agent checks Aftership's unified tracking API every two hours for all active shipments. When it detects that a shipment's estimated delivery date has moved, or that a shipment has been stuck at the same tracking status for more than 8 hours (a common early sign of a delay that hasn't been formally flagged yet), it sends a proactive email to the customer contact for that order.

The email uses a template that's personalized with the order number, original delivery date, new estimated date, and a brief explanation of the cause when Aftership provides one. It includes a direct contact number for their logistics team if the customer needs to escalate.

The agent also logs every delay and its notification to an internal spreadsheet, which their team reviews weekly. This created a side benefit: they now have structured data on which carriers cause the most delays on which routes, which they're using in carrier negotiations.

Results across 90 days

Inbound complaint calls and emails about delayed shipments dropped 40% compared to the previous 90-day period. The agent notified customers proactively in 87% of delay situations before the customer contacted them. In the remaining 13%, the delay was too short to trigger the 8-hour detection threshold before the shipment resumed normal movement.

Several customer accounts commented on the proactive communication in their quarterly reviews. Two mentioned it as a reason they were increasing their order volume with the distributor over a competitor who offered similar pricing but less communication.

Technical note

This implementation required a developer to set up — the Python script runs on a small cloud server. It's not a no-code implementation. For businesses without developer access, the same outcome is achievable through Zapier + Aftership + an email service, though with less customization over delay detection logic. If you're comfortable with no-code tools, budget an extra week for configuration compared to the custom setup described here.