How to Automatically Identify Jobs That Are Waiting on the Customer
A quote has been sent.
The customer needs to approve it.
Or maybe you are waiting for:
Access details.
A purchase order.
A colour selection.
A deposit.
A preferred installation date.
The business has done its part.
Now the job is waiting on the customer.
That is normal.
The problem starts when those jobs disappear into a generic status such as:
Pending
and nobody knows who is supposed to do what next.
Separate Internal Delays From Customer Delays
Not every stalled job is your team's fault.
A job waiting on:
Technician notes
is different from a job waiting on:
Customer approval
The system should make that distinction clear.
For example:
Status: Waiting
is vague.
A better structure might be:
Waiting On: Customer
Required Action: Approve quote
Since: 12 September
Owner: Sales
Now the system knows why the job is not progressing.
Record What You Are Waiting For
Whenever a job becomes dependent on the customer, capture the specific action.
For example:
Waiting On: Customer
Reason: Deposit payment
or:
Waiting On: Customer
Reason: Site access details
or:
Waiting On: Customer
Reason: Quote approval
This matters because different customer actions may need different follow-up rules.
Track How Long the Customer Has Had the Action
Once you know when the job entered the waiting state, you can calculate:
Days Waiting: 4
That lets you create sensible follow-up rules.
For example:
Follow up after 3 days.
Deposit payment
Follow up after 2 days.
Site information
Follow up after 5 days.
Installation date confirmation
Follow up after 1 day if scheduling is urgent.
The timing should reflect the impact on the job.
Automate the First Follow-Up
A basic customer follow-up can happen automatically.
For example:
Quote sent
↓
No approval after 3 days
↓
Send reminder
The message might say:
Hi John, just checking whether you had a chance to review the quote for Job J-6328. Let us know if you have any questions.
That removes simple chasing from the team.
The system handles the first reminder automatically.
Escalate When the Delay Starts Affecting the Job
Not every unanswered request is urgent.
But customer delays can eventually threaten scheduling.
For example:
Installation scheduled in 7 days
and:
Customer access details still missing
The system can raise the priority.
You might use rules such as:
5 days remaining
Customer reminder.
3 days remaining
Notify job coordinator.
1 day remaining
Escalate to operations.
The closer the scheduled date becomes, the more visible the unresolved customer action should be.
Do Not Lose Ownership Internally
Even if the customer is responsible for the next action, someone inside the business should still own the follow-up.
For example:
Waiting On: Customer
does not mean:
Nobody owns this job.
Instead:
Customer Action: Approve quote
Internal Owner: Sales
That person remains responsible for making sure the job does not disappear.
Create a Waiting-on-Customer View
Your team could have one simple view containing:
Jobs Waiting on Customer
For example:
J-6328 – Quote approval – 4 days
J-6341 – Deposit payment – 2 days
J-6350 – Site access details – 6 days
J-6363 – Installation date confirmation – 1 day
Now the team can see every external dependency in one place.
Stop Customer Delays Distorting Internal Performance
Separating these jobs also improves reporting.
Imagine a job spends:
12 days in progress
That might look like an internal delay.
But perhaps:
8 of those days were waiting on customer approval.
That changes the interpretation.
You can start measuring:
Internal processing time
separately from:
Customer waiting time
That gives you a more accurate view of where delays actually occur.
Track What Customers Usually Delay
Over time, the data may show patterns.
For example:
58 customer delays this quarter
26 quote approvals
14 deposits
10 access details
8 scheduling confirmations
That can lead to process improvements.
Perhaps quote reminders need to happen sooner.
Perhaps deposits should be collected through a payment link.
Perhaps access questions should be included in the booking form.
Automation can reduce the amount of waiting in the first place.
Start With One Customer Dependency
Choose the customer action your team chases most often.
Define:
What are we waiting for?
Who owns the follow-up internally?
When should the first reminder happen?
When does it become urgent?
Then build that workflow.
At 5M Consulting, we help trade and service businesses build systems that keep customer-dependent jobs visible instead of letting them quietly disappear into a waiting status.
Waiting on the customer is normal.
Losing track of the job is not.