A customer sends an order and hears nothing until the truck arrives, short three items. Then the calls start: is it coming, when, can you replace it. Most of those calls exist because the information was in the system and nobody sent it.

What customers actually need to know

  • That the order was received and entered correctly.
  • What will ship, on which date, and what is missing.
  • When a date changes, before they discover it on delivery.
  • When a backordered item arrives, and whether it will ship on its own.

How the automation works

  • When an order is entered, the ERP data is turned into a confirmation sent to the customer: lines, quantities, prices and expected date.
  • Lines that cannot be filled from stock are marked as backordered with the expected date when it is known.
  • A change of date or a partial shipment triggers a short notice to the customer.
  • When stock arrives, customers waiting for that item are told, and the order is released for shipping or for approval.

Where a person stays in the loop

Proposing a substitute product, splitting a shipment for a large account or promising a date outside the usual rules are decisions with a cost. The system prepares them with the stock, the alternatives and the customer's history, and a person approves before anything is sent.

The result is fewer calls asking where an order is, and more time for the calls that matter. It also gives the sales team a reliable view of what each customer has been told, which avoids two people promising two different dates.

How to start

Start with the confirmation at order entry, which only needs data your ERP already has. Add backorder notices next, then date changes, and write each message once with the team so the tone matches the way you already talk to your customers.

Keep an eye on the questions customers still ask after the notices start. Each one points to information that was missing from a message, and adding it is usually a small change to the template rather than a new project.