Answer Hub · CRM and Customer Management
How do restoration companies send customers job progress updates?
The short answer
Set a predictable update rhythm tied to job milestones: arrival, end of each mitigation day, drying complete, scope or approval changes, reconstruction start and final walkthrough. Send short updates through one channel the customer chooses, include what happened, what is next and who to contact, and log every update on the job record so anyone in the office can answer questions.
Why progress updates matter
A homeowner with fans roaring in their living room is anxious, and anxious customers call. They call the office, the PM, the tech's cell and sometimes the adjuster. Most of those calls ask the same three questions: what is happening, when will it be done, and who do I talk to.
Proactive updates answer those questions before they are asked. They reduce interruptions for the field team, cut down on "nobody told me" complaints and make the job file stronger, because a written update is a timestamped record of what the customer was told.
The milestones that deserve an update
Not every visit needs a long message, but customers should never wonder whether the job is moving. Build updates around these points:
- Before arrival: who is coming, the arrival window and what to expect on the first visit.
- End of day one: what was done (extraction, equipment placed, areas affected), what the equipment is for and when the next visit is.
- Each monitoring visit: a one-line status such as "Readings are coming down in the hallway; the closet is still wet. Next visit Thursday morning."
- Drying complete: equipment removal scheduled, and what happens next.
- Scope or approval changes: if the carrier needs more information, if a wall must come out or if a subcontractor is added.
- Reconstruction start and schedule: trades, sequence and expected disruption.
- Final walkthrough: completion, sign-off and how to reach you if something comes up.
How to send updates customers actually read
- Ask the customer's preferred channel at intake. Text, email or a customer portal. Record it on the job and use it.
- Keep it short. Three to five sentences. Long explanations belong in a call or a walkthrough.
- Use plain language. "The floor is still wetter than the dry reference area" is better than unexplained jargon.
- Add a photo when it helps. A picture of the cleared area or the new drywall says more than a paragraph.
- Avoid promises you cannot control. Do not commit to carrier timelines or coverage decisions. Say what you will do and when you will follow up.
- Log it. Every update should land on the job record so any office person can see what the customer was told.
A worked example
Say a family has a second-floor bathroom overflow that reached the kitchen ceiling. A sample update rhythm:
| Day | Update |
|---|---|
| Day 1, 9 a.m. | "Our technician will arrive between 10 and 11 to extract water and set drying equipment. Please make sure we can reach the kitchen and upstairs bath." |
| Day 1, 5 p.m. | "We removed standing water, set four air movers and two dehumidifiers, and documented the affected areas with photos. Please keep the equipment running. Next visit tomorrow around 9." |
| Day 3 | "The bathroom subfloor is drying well. The kitchen ceiling is still wet near the light fixture. We will check again Thursday." |
| Day 5 | "Drying is complete. We will pick up equipment Friday. Your project manager will call about reconstruction next week." |
| Reconstruction | "Drywall repair starts Monday, then texture and paint Wednesday. Expect noise and dust control in the kitchen." |
Notice what the updates leave out: guesses about insurance decisions, technical detail the customer did not ask for and vague phrases like "soon."
Who sends the update
Assign it. The tech on site can send the end-of-visit note from the field. The PM owns updates about scope, schedule and reconstruction. The office owns anything about paperwork, signatures and invoicing. When nobody owns it, nobody sends it.
Building simple templates
Write one short template per milestone and keep them where every sender can reach them. A template is a starting point, not a script: the tech still adds the specific room, the reading trend or the next visit time. Review the templates every few months and retire wording that keeps prompting the same follow-up questions from customers.
Common mistakes
- Going silent during waiting periods. When a job is waiting on approval or materials, send an update anyway. "Nothing new yet; we will check again Wednesday" prevents a frustrated call.
- Using personal phones. Updates sent from a tech's personal number never reach the job record.
- Over-sharing carrier details. Coverage questions belong between the customer and their carrier. Point them there politely.
- Inconsistent messages. If the tech says one thing and the PM another, trust erodes fast. One job record keeps everyone aligned.
- Not including tenants or property managers. On rental and commercial losses, confirm who should receive updates.
How RestoreUnited can help
RestoreUnited's Job Connect is built for customer communication, so updates and photos can be shared from the job, and the Restoration CRM keeps each customer's contacts and preferences in one place. Field techs can send updates from the mobile app, and everything stays on the job record for the office to see. A simple template for each milestone, plus a named sender, is what turns the tool into a habit.
See it in RestoreUnited: Job Connect
RestoreUnited product videoFrequently asked questions
How often should restoration customers get updates?
At each meaningful milestone and at least after every site visit during mitigation. During waiting periods, such as pending approvals, a short check-in every couple of days keeps customers from wondering whether the job stalled.
Should technicians send updates or only the project manager?
Both, with clear lanes. Techs can send short end-of-visit notes from the field; the PM handles scope, schedule and reconstruction updates. The office handles paperwork and billing questions.
What should we avoid saying in customer updates?
Avoid predicting what the carrier will approve or pay, and avoid firm dates you do not control. State what your team did, what comes next and when you will follow up.
Do written updates help with documentation?
Yes. A logged update is a dated record of what the customer was told and when, which helps resolve misunderstandings later. Keep updates factual and accurate.