Justin PenningtonJustin Pennington
All posts

Your Customers Shouldn't Have to Call to Ask Where Things Stand

Status calls mean progress still lives in someone's head. Make it a field that moves with the work, in stages they can read, and tell them before they ask.


A customer calls. Or their office manager emails. Or a text lands while someone is on the job. The question is almost always the same. Where are we on this?

Someone on your side has to stop, find the job, and say the answer out loud.

I run Infraxio from Ponte Vedra. Service businesses and logistics operators around Northeast Florida give up the same part of the morning this way. The person who was doing the work becomes the status desk.

The Call Is the Symptom

"Where are we?" shows up when status lives in a person's head, in an inbox thread, or on a spreadsheet one person updates when they remember. The customer cannot see the record, so a person has to translate it.

Each call interrupts the people doing the work. The project lead, the estimator, the dock office, the person assembling a submission. They stop to look the job up. The customer hears the pause and learns they cannot see progress.

Package tracking and food delivery apps trained people to expect a stage, a time, and a next step on a screen they already have open. A contractor's customer, a carrier at your gate, a client waiting on a deliverable will still pick up the phone when silence is the other option.

CRM and ERP projects have a long version of the same failure. The status field gets set to "in progress" on day one and left there. The report looks calm. The customer, who is living the job, knows it is not. I wrote about the internal form of this in nobody opens the dashboard. A screen people do not trust sends them back to asking a person. A stale status field puts the customer on the phone.

Make the Field Move With the Work

A Friday email and a nicer template still depend on someone remembering to send them. The fix is operational. Status has to be a field that changes when the work changes.

When the job moves from scheduled to on site, or from review to delivered, the field moves with it. A note someone plans to write later will slip, and the customer will call in the gap.

The stages a customer sees have to be stages a customer can read. Waiting on a part, blocked on a drawing, in review, assigned to a writer: those belong to the team. The customer needs a short list. Received. Scheduled. In progress. Done, or held, and why. Pick the handful of milestones they actually care about.

Put that short list where they can see it. A portal, a status page, or an automatic note when the stage changes. The customer should be able to read the record without a person standing in the middle of it.

When the job slips, tell them before they ask. An alert on the delay, the hold, the date that moved. Bad news delivered early is still a status. Silence is a reason to call, usually after they have decided you forgot them.

Keep the Shop Floor Off the Page

Keep internal noise off the customer view. The argument in the thread, the rejected draft, the task that bounced between two people. The customer bought a promise and a way to see whether it is holding.

A portal nobody updates is worse than no portal. A page stuck on last month says the system is decoration and the real answer is still a phone call. If the field cannot stay current, leave it unpublished.

The field stays current when changing the work changes the field. A separate task called "update the client" is the old habit with a new name. Tie the customer-facing stage to the move the team already makes. Mark the work done, and the status moves. Push a date, and the customer sees the new date.

Where the Status Already Lives

In IFX Hub, a job or a project carries a stage. The client-facing view shows that stage, and a change of stage can send the update on its own. The record the team already moved is the update.

That holds only when the stage is the real one. A field someone tidies on Friday is wrong by Wednesday, and the client is back in the inbox. This is the gap I wrote about in the handoff is where revenue leaks. Context that should have traveled with the work waited on a person.

DockOps is that problem at a door. Carriers and shippers want to know whether the appointment still holds. Calling the dock office turns the morning into a switchboard. A status they can see, on the appointment they already have, takes the place of the call.

IFX Bid is the version inside the team. A pursuit has a stage, an owner, and a date. When the only way to know where a submission stands is to ask around, the bid lead becomes the person everyone interrupts. The stage on the pursuit is what the team should read.

Growth7 is where a real stage change should fire the next touch. A follow-up that goes out because a lead or a quote moved, or because it sat still past the point where someone should have moved it, is a system. The trigger is the stage. A reminder to go look is the old check-in.

An Assistant Can Only Repeat the Field

A client asks a chat where the job stands. A teammate asks an assistant. The assistant can answer only if the status in the system is true.

A stale field comes back as a confident sentence. A model does not know the job is on a truck, or waiting on a signature, unless the record says so.

The stage is real because the work changed it. The assistant reads that stage, says it in the customer's words, and routes the slip to a named person. It does not invent a status out of an email thread.

What to Look at This Week

Take the recent "where are we?" calls and emails you can still name. For each one, write down what the customer was trying to see.

A stage they would have understood. If the honest answer was a paragraph of internal detail, the stages are still for the team.

A field that moved when the work moved. A plan to update it later is how the field goes stale.

A place they could have read it. A portal, a page, an automatic note at the stage change. If a person had to translate, the record is not in front of the customer yet.

A named person who tells them when it slips. "Whoever notices" means you are waiting for the customer to call.

Pick the handful of milestones. Leave the rest inside the shop. Let the stage move with the work, and say so when it breaks, early enough that they hear it from you.

The call is the system using a person as the status page. That is a job you can stop staffing.