Blog
How do you stop "where is my order?" eating half the day?
Status chasing is the most interruptive job in a shop. How to answer it automatically from your own job data, on any channel.
By answering it automatically from your job data, on whatever channel the customer uses. Status chasing is one of the most interruptive jobs in a subcontract shop: the answer already exists in your system, it just needs someone to stop and look it up. When a system can look it up for them, the calls stop landing on your planner and the office stops acting like a switchboard.
Why this one hurts more than it should
A status call is short. That is exactly why it is corrosive. It is thirty seconds of information wrapped in five minutes of interruption: find the job, check the traveller, ask the cell leader, ring the customer back.
Do that eight times a day and you have lost an afternoon, usually from the person who is also planning the week. Worse, the interruption lands mid-task, so the real work restarts from cold each time.
And the volume is not random. It clusters exactly where you are least able to absorb it: the week a big order is due, the days after a promised date slipped, and the run-up to a customer's own shutdown.
Why customers chase in the first place
Not because they are difficult. Because they have their own line to keep running and no visibility into yours. Every chase is really one of three questions:
- Is it still on for the date you gave me?
- Has it shipped, and what is the tracking?
- Will the paperwork, including the cert of conformity and material certs, arrive with it?
If those three are answered before they have to ask, most of the chasing disappears.
What answering it properly looks like
The agent takes the call or the email, recognises the customer from their phone number or email address, finds the order, and answers from the same job data your planner would use:
- It knows who is asking. An existing customer is recognised from their phone number or email address, so they do not have to start from scratch or read out a purchase order number twice.
- It looks it up rather than guessing. It says it is checking, checks, and comes back with the real position: cleared final inspection, booked for despatch tomorrow, on an overnight pallet.
- It gives the date and the paperwork in one reply. Delivery date, tracking, and the certificate of conformity in the same answer, because that is the actual question.
- It escalates the genuine problems. A slipped date or a quality issue goes to a person, with the job history included. It never invents a date to make a call end well.
The part that stops the calls before they start
The bigger win is the chase that never happens. Once the agent is on the despatch data it can confirm proactively: the job is booked, here is the date, here is the tracking, the certs follow automatically. Customers stop ringing because they already know.
That is usually where a shop notices the change first. Not "we answer status faster", but "the phone is quieter".
What stays with your people
Deciding what to do when a date slips. Telling a customer something they will not want to hear. Anything that involves a concession, a quality escape or a commercial conversation. The agent handles the ninety percent that is pure lookup, and hands you the ten percent that needs judgement, which is the right split.
Frequently asked
Does it need our ERP?
It works with the job data you already keep, whether that is an ERP or MRP such as Sage, Epicor or SYSPRO, or the spreadsheets and job files most shops actually run alongside them.
What if the date has slipped?
It does not paper over it. It gives the real position and routes the customer to a person, with the job history attached.
Can it send the certificates?
Yes, it can find and send the conformity and material certs against the order, which removes one of the most common chases entirely.
Will customers accept it?
They mostly want the answer, not the person. The complaints we hear about status are always about waiting, never about who told them.
See it on your own enquiries.