Pull the call log at your counter for a single Tuesday morning and sort it by reason. A good share of it isn't new business. It's a facilities manager in Sugar Land checking whether the compressor came in, a project super asking if his PO shipped, somebody wanting a fresh promise date on a part that was supposed to land last week.
None of those calls make you a dime. They just move information that already lives in your system out to the person waiting on it, one interruption at a time. And the caller isn't happy either, because by the time he's dialed your number he's usually already decided you dropped the ball.
The fix is boring, and it works. You tell them first. The moment an order ships, slips, or a promised date changes, something fires off a text or an email so the person on the other end hears it from you before he thinks to ask. Below is how to sort out what to automate, what still needs a real phone call, and how to word the bad news so it reads as on top of it instead of a mess.
Start with the three moments worth a message
You don't need to narrate every step of an order. Nobody wants a text when the pick ticket prints. Three moments actually matter to the person waiting, and those are the ones to automate:
- It shipped or it's ready to pick up. A one-line note with the PO or order number and, if you have it, a tracking link. This kills the single most common status call.
- The promised date moved. The instant your system shows a new date on a backordered line, the customer should know. A silent slip is what turns a patient buyer into an angry one.
- It arrived or was delivered. Closes the loop so he stops wondering and you stop fielding the "did it ever show up" call two days later.
Everything else (order received, in processing, being staged) is noise to the customer. Send those and people start ignoring your texts, which defeats the whole point. Keep the automated messages rare enough that each one means something.
Know what a text can't carry
Automation is great at the routine slip. A gasket that's a day late, a fitting that jumped from Tuesday to Thursday, a truck running behind. Those are texts. The customer reads it, adjusts, and moves on.
Some delays are too big for a text, and pretending otherwise makes you look worse, not better. A two-week slip on a rooftop unit during a July heat wave, when the building's cooling is riding on it, is a phone call. So is anything that blows a scheduled install, forces a crew to reschedule, or leaves a tenant without air in 98-degree weather. The customer has decisions to make off that news, and he needs a person who can answer the follow-up questions in the same breath.
A rough line to draw: if the delay changes what the customer has to do, a human makes that call. If it only changes what he knows, a text is fine. When you're not sure, err toward the call. The automated system should still log the slip, but a person should be the one who delivers it.
Word the delay so it reads as on top of it
A delay message can say the exact same facts and land two completely different ways. The difference is whether it sounds like you're tracking the order or like you got caught. You want the first one.
Lead with the new plan, not the apology. "Your condenser now ships Thursday and lands here Friday morning" tells him what he needs. "We're so sorry, there's been a delay" makes him ask the questions you should have answered up front. Give the fact, the new date, and one next step, in that order.
A template that holds up:
- What moved: "Heads up on PO 4471, the two rooftop curbs."
- The new date, specific: "New ship date is Oct 6, here by the 8th." Not "early next week."
- Why, in a few words: "Manufacturer pushed the run." Short and honest beats a paragraph of excuse.
- The out: "Need it sooner? Call us at the counter and we'll look at alternates."
Notice there's no groveling and no vague hedging. It reads like a dispatcher who already knows the whole board. That tone is worth more than a discount, because it tells the buyer he can plan around you.
Wire it to the system you already have
The good news is you're not building a database. The order and promised dates already live in your ERP, your distribution software, or whatever your counter rings orders through. You're just letting a change in one field trigger a message.
The moving parts are simple:
- Pick the trigger fields. Usually the ship-status flag, the tracking number, and the promised or expected date on each line. When one of those changes, that's your signal.
- Confirm the contact and the channel. You need a good cell number or email tied to the order, and a note of which the customer actually reads. Most facilities folks want a text; some purchasing offices want email for the paper trail.
- Write the templates once. Three or four short messages, one per event, with the order number and dates dropped in automatically. Get them right the first time and they run for years.
- Set a human tripwire. Any slip past a threshold you pick (say, more than three days, or any date change on a flagged critical order) routes to a person instead of firing a text. That's your July rooftop rule, baked in.
Be honest about the limits. Automation is only as good as the data behind it. If your promised dates are wishful and your system doesn't get updated when a vendor slips, an automated message will just broadcast a wrong date faster. Clean up how you track expected dates first, then automate. This kind of order-status texting is one of the more practical setups we install for supply houses and contractors, precisely because it rides on data you already keep.
Worth doing this week
You don't have to build the whole thing to start getting calls off the counter. A few concrete first steps:
- For one morning, tally your inbound calls by reason. Count how many were just somebody checking an open order or a backorder. That number is your case.
- Write the three messages by hand: shipped, date moved, delivered. Keep each to a sentence or two, lead with the fact, and read them out loud to make sure they sound like a person.
- Pick your human tripwire now, before you automate anything. Decide the slip size and the order types that always get a call, and write that rule down where dispatch can see it.
- Check whether your order system has good cell numbers and emails on file. If it doesn't, that's the real first job, and it's worth doing regardless.
- Start manual if you have to. Have the counter text the shipped and slipped notes by hand for a week. You'll learn exactly what to automate, and you'll feel the phones go quiet before you've spent a dollar on software.