You keep customers updated during a job by answering the time question on a fixed schedule they agreed to before work started, and by putting the work question somewhere they can look at without going through you. Most contractors do the reverse. They improvise updates whenever a gap appears in the day, then get frustrated when the customer calls at 9:40am asking how it is going.
That inversion explains why the standard advice on this topic does not survive contact with a real week. Search this question and every result tells you to communicate more. Then read what operators actually say to each other. On r/handyman, the top-voted answer to a thread about handling incoming requests mid-job was blunt: "I don't answer any calls until 4 or 5pm... If I answered phone during the day I would get nothing done." The second was a contractor who leaves his phone in the truck and checks it on two scheduled breaks.
Both camps are half right. Communicating more, unscheduled, destroys your production day. Communicating less turns you into the contractor who went quiet. The way out is not a volume dial. It is deciding in advance which updates fire automatically, which ones you deliver on named days, and which ones deserve you personally picking up the phone.
The update your customer wants is not the one you are giving
Ask a contractor what customers complain about and you get "they want constant updates." Ask customers and the answer is different.
FIELDBOSS commissioned a Pollfish survey of 1,000 US homeowners who had hired an HVAC professional in the previous twelve months. Overall satisfaction was high, at 94.9%. But when respondents named their single biggest frustration, the ranking is worth sitting with:
| Top frustration | Share |
|---|---|
| Costs higher than expected or surprise fees | 21.0% |
| Technician arrived late or outside the window | 13.0% |
| Difficulty getting an appointment when needed | 12.6% |
| Problem not fixed right the first time | 7.1% |
| Lack of communication or updates during service | 6.8% |
| Felt pressured to buy extras | 5.2% |
| Technician did not respect the home | 4.2% |
| No major frustrations | 30.1% |
Read the two lines that matter together. Roughly 26% of homeowners named a timing failure, arriving late or being hard to book, as their top frustration. Only 6.8% named a lack of updates about the work itself.
That is not a small distinction. It means the thing you find hardest to produce, a meaningful narrative of what got done today, is the thing customers are least aggravated by not having. And the thing you find easiest to produce, an accurate arrival time, is the thing they care about most.
By the numbers
In the same survey, 73.8% of homeowners expected service within 24 hours for an urgent outage, and 29.8% expected it within a few hours. When you are competing against that expectation, an honest "we can be there Thursday between 8 and 10" outperforms a vague same-week promise you cannot hold.
Two different businesses, two different systems
Most guides on this topic quietly assume you are a general contractor running a twelve-week kitchen. If you run same-day service calls, that advice is useless to you, and vice versa. The update problem splits cleanly in two.
Same-day service work covers HVAC, plumbing, electrical, garage door, appliance repair, pest control. You are doing five to eight stops a day. The customer's entire experience of "being updated" happens in a ninety-minute window: is he coming, when, is he here, is it done, what do I owe. Nobody in this bucket wants a weekly progress report.
Multi-day project work covers remodels, additions, roofing, restoration, landscaping installs, custom builds. Here the customer lives with your absence for weeks. Their anxiety is not about today, it is about whether the whole thing is on track and whether their money is doing anything.
The mistakes are opposite. Service businesses under-communicate on time and think buying a CRM will fix it. Project businesses over-communicate at random and burn their own day doing it. The six rules below apply to both, but the implementation splits, and I will flag which is which.
Rule 1: Answer the time question before anyone asks it
For service work, this is the entire ballgame. Two messages carry almost all of the value:
- A confirmation the day before with the window and the technician's name.
- An on-my-way message when the tech leaves the previous stop, with a real ETA.
That is it. Both are triggerable off dispatch status, which means neither requires anybody to remember anything. Service Fusion's own data puts the stakes plainly: most home service businesses miss between 15% and 35% of incoming calls, and the peak of that miss rate lands during the hours crews are busiest. Every "where is he" call you prevent is a call your office was statistically likely to drop anyway.
For project work, the time question is different but just as concrete. The customer wants to know what happens next and on what date. "Drywall Tuesday, inspection Thursday, tile the following week if we pass" is worth more than three paragraphs about what happened yesterday.
Tip
Send the confirmation the day before, not the morning of. A morning-of text arrives after the customer has already rearranged their day around you, which means it can only confirm or ruin the plan, never improve it.
Rule 2: Put the status somewhere they can check without you
The most useful comment I found in a week of reading these threads came from a contractor on r/Contractor answering a peer whose client was texting multiple times a day: "Externalize the status into something they have access to 100% of the time... They can reload that page as many times as they need to."
That is the whole mechanism. An anxious customer is not trying to talk to you. They are trying to reduce uncertainty, and you are the only interface available. Give them a second interface and most of the contact volume disappears without a single boundary conversation.
The externalized status does not have to be sophisticated. In descending order of effort:
- A shared photo album per job that the crew dumps into at end of day.
- A one-page shared doc you update when status changes, not on a schedule.
- A client portal in your job software, which is what most operators eventually land on. We compared the realistic options in our breakdown of client portal software for contractors.
The failure mode to avoid is a portal nobody logs into. One contractor in that thread flagged the practical constraint straight away: one of his clients was an older guy who would struggle to log in and download anything. If access requires an app install and a password reset, the customer will keep calling you, and you will have paid for software that changed nothing.
Rule 3: Name two update days and put them in the contract
For project work, the operators who have solved this all describe the same shape. A GC with 26 years in on r/Contractor: "We do updates Mon/Thurs. Monday letting folks know the intentions of the week, Thursday with progress report on what was done." Another: "I aim for end of day Mon, Wed, and Friday with pics sent. Have a schedule and it tends to avoid the random calls while your hands are full."
Two things make that work, and neither is the frequency.
The first is that the days are named. "I'll keep you posted" creates an open-ended obligation the customer will test constantly. "You will get an update Monday and Thursday by 5pm" creates a contract the customer can wait on.
The second is that it is set before the job, not during it. This is where most attempts fail. A boundary introduced in week three reads as a reaction to the customer personally. The same boundary introduced at contract signing reads as how a professional operation runs. A contractor summarising the pro approach on the same thread put the front-loading step well: ask the client their preferred method, how frequently they want updates, and what specifically they are anxious about. Then build the schedule around the answer instead of guessing.
If your update schedule lives in your head, it breaks the first busy week. We build custom CRMs that fire confirmations, on-my-way messages and end-of-day summaries off job status changes, so the customer gets updated whether or not anyone remembered.
Rule 4: Communicate the downtime, not just the work
This is the rule nobody writes about, and it is where most status calls actually come from.
A contractor on r/Contractor described the only situation where constant homeowner contact genuinely irritated him: "when there is scheduled down time and they are wondering what's happening." That is the pattern. Customers do not call you when the site is full of trucks. They call when it is empty.
The problem is structural. Downtime is exactly when you have nothing to report, so it is the period you are least motivated to send an update about. Meanwhile the customer is driving past a silent job site and doing the worst possible math in their head.
So flip it. Downtime gets communicated in advance and by date:
"We are waiting on the rough-in inspection, booked for Thursday. Nobody will be on site Tuesday or Wednesday. That is expected, not a delay. If the inspection passes Thursday, drywall starts Friday."
Three sentences, sent before the quiet period rather than during it, and you have pre-answered the call. For service work the equivalent is the parts backorder. "Your compressor ships Tuesday, we install Thursday, I will confirm Monday once tracking updates" prevents a week of calls you would otherwise field one at a time.
Rule 5: Match the channel to the message, and do not assume text
Every field service software blog on the internet will tell you to move your customer communication to SMS. Half your customers disagree.
In the FIELDBOSS survey, when asked how they prefer to communicate with an HVAC provider when scheduling or coordinating service, 50.3% chose a phone call. Text came second at 23.7%. App or online booking got 12.0%, email 8.2%, and 5.8% had no preference.
That number should change how you build the stack. A fully automated text-only system optimises for the quarter of your customers who prefer text, and quietly degrades service for the half who wanted a human voice. The right split is by message type, not by customer:
| Message | Channel | Why |
|---|---|---|
| Appointment confirmation, arrival window | Text | No reply needed, needs to be re-readable |
| On-my-way and ETA | Text | Time-sensitive, glanceable |
| End-of-day progress and photos | Text or portal | Reference material, not a conversation |
| Anything involving cost or scope change | Call, then email summary | Needs a real conversation and a paper trail |
| Bad news, delays, discovered damage | Call | Never deliver bad news by text |
| Approvals and sign-offs | Written, always | A verbal yes is not evidence |
That last row is not optional. A contractor on r/Contractor described giving out only the office number and pushing everything else to email specifically to kill the "I told you that was approved on the phone three months ago" argument. If it costs money, you want it in writing. Our guide on how to stop losing track of customer texts covers what goes wrong when approvals live in a personal phone.
Rule 6: Price concierge communication instead of absorbing it
Some customers want daily contact. That is a legitimate preference, and it is also a service with a cost.
The instinct on the trades subreddits is to charge for it, and the top-voted reply to the contractor being texted multiple times a day was exactly that: tell them you allocate a set amount of time per day for communication, and if they want more, it gets billed. The 26-year GC quoted earlier described the same thing as a product rather than a penalty. He has had many clients who wanted concierge-style five to seven day a week communication, and he told them upfront it came with a premium price, which they were comfortable paying.
The difference between those two framings matters. Billing for excess communication mid-job is a fight. Offering a higher-touch tier at quote time is an upsell. Same money, opposite customer experience.
Watch out
Do not solve a communication problem by ghosting. The FIELDBOSS data found 42.6% of homeowners hired a company they had used before and another 26.3% came from a personal referral, meaning roughly 69% of work in that sample came from loyalty and word of mouth. The customer you stop answering is the referral you do not get.
What an unanswered call actually costs you
The reason so many good operators end up avoiding the phone entirely is that they have felt the real cost of an interruption without ever seeing it quantified.
Research by Gloria Mark at UC Irvine found it takes an average of 23 minutes and 15 seconds to return to a task after an interruption, and that people typically work on two intervening tasks before getting back to the original one. Three status calls in a day is not four minutes of talking. It is over an hour of degraded work, on a day you priced as productive.
Meanwhile the expectation pressure is going the other way. Zendesk's CX Trends 2026 research found 74% of consumers now expect round-the-clock availability and 88% expect faster responses than they did a year ago. You cannot out-hustle that gap by answering more calls. You close it by making sure the routine questions never get dialled in the first place.
That is the honest case for automating the boring updates: not that customers prefer robots, but that every question a trigger answers is a question that does not interrupt a technician mid-repair. If your phone problem is bigger than your update problem, missed call text back is the cheaper first fix.
The one-page update plan
Write this once, attach it to every quote, and hold it.
Before the job starts
- Ask how they want to be contacted and how often. Write the answer in the file.
- Name the single point of contact and the number that reaches them.
- State your response time in plain terms: texts same business day, calls returned by 5pm.
- Put the two named update days in the contract for project work.
- Flag the known quiet periods, inspections, material lead times, before they happen.
During the job
- Day-before confirmation with the window and the tech's name.
- On-my-way message with a real ETA, fired off dispatch status.
- End-of-day photos into the shared album or portal, captioned in plain English.
- Updates on the named days whether or not there is exciting news.
- Any cost or scope change: call first, written summary same day.
When something goes wrong
- Confirm the facts before you call. Do not relay half a problem.
- Call. Do not text bad news.
- State the problem, the schedule impact, the cost impact and your plan, in that order.
- Follow up in writing the same day.
After the job
- A short check-in a day or two later. This catches small problems while they are still free to fix.
- Ask for the review at that moment, while the experience is fresh.
None of this requires new software on day one. It requires deciding the schedule before the job instead of during it. The software question only becomes real when you are running enough concurrent jobs that the constraint stops being what to send and starts being remembering who is owed what. That is the point where a system that fires updates off job status, rather than off your memory, stops being a luxury. If you are weighing that decision, our comparison of CRM versus field service software is a reasonable place to start.
The short version
Customers are not asking you to talk more. They are asking to stop being uncertain. Uncertainty about time is what actually drives them to the phone, uncertainty about progress is a distant second, and silence during quiet periods is the accelerant on both.
Answer the time question automatically. Publish the work question somewhere they can read without you. Name your update days before the job and hold them. Communicate the downtime like it is work. Use a phone call for anything that costs money, because half of them wanted a call anyway. And if someone wants concierge contact, sell it to them rather than absorb it.
Do that and the mid-job status call mostly stops happening. Which is the actual goal, because the update you never had to send is the only one that costs nothing.