A complaint resolution process that keeps customers

Why a written process beats good intentions

Most home service companies handle complaints the way they handle emergencies: whoever picks up the phone does their best. Sometimes that works. Often the customer tells the story three times to three people, waits days for a callback and gets an offer that feels improvised. By then, a fixable problem has become a lost customer and, frequently, a public review.

A simple written process changes that. It makes sure every complaint has an owner, gets acknowledged on time, is investigated before anyone promises anything, and ends with a clear outcome that is recorded. It also protects your team: technicians know complaints will be looked at fairly, and managers know what they are allowed to offer.

Complaints often start with money. In Angi's 2025 survey, 56% of homeowners faced budget issues on maintenance projects and 55% on improvement projects^[1]. A customer stretched by an unexpected bill is quicker to see a problem with the work, and slower to accept an explanation.

The seven-step process

1. 01

   1. Log it

   Every complaint, however it arrives (call, text, email, review, technician report), goes into one log with the job number, customer, date, channel and the complaint in the customer's words.

2. 02

   2. Acknowledge within set hours

   Contact the customer within the time set for its severity level, confirm you heard the problem, name the person handling it and say when they will hear back.

3. 03

   3. Investigate

   Read the job notes and invoice, look at photos, listen to the call recording if there is one, and talk to the technician. Visit if needed. Do not offer a remedy until you know what happened.

4. 04

   4. Offer options

   Present one to three remedies that fit the facts, within the authority limits below. Let the customer choose where possible.

5. 05

   5. Confirm in writing

   Send a short text or email with what was agreed, who will do what, and by when.

6. 06

   6. Follow up

   After the remedy, check that the problem is solved and the customer is satisfied. Close the case only then.

7. 07

   7. Fix the root cause

   Tag the cause (communication, workmanship, scheduling, pricing, conduct, product failure) and review the tags monthly.

Severity levels and response times

These response times are an example. Choose targets you can actually meet every day, publish them internally and track them. A promise to call back within two hours that is broken half the time is worse than a promise of one business day that is always kept.

What managers may offer

Unclear authority slows everything down and makes remedies inconsistent. Write down who can offer what, so the person on the phone can resolve most cases in one conversation.

• Office staff: apologize, rebook a return visit at no charge for work-not-fixed cases, and correct clear invoice errors.
• Service manager: approve a return visit by a senior technician, a partial credit up to a set amount, or waiving a service fee.
• Owner or general manager: full refunds, replacement of equipment or materials, and any case involving property damage, injury or a lawyer.
• Anyone: escalate immediately if the customer mentions safety, injury, police, a regulator or legal action.

Words that calm, words that inflame

The first call sets the course. Let the customer finish, repeat the problem back in their words, and say what happens next. Avoid 'our policy is', 'that's not possible' and anything that sounds like blame.

When you call back with options, be specific: 'We can send our senior roofer tomorrow morning to inspect and repair at no charge. If the leak is from something we didn't touch, we'll show you photos and give you a written price before doing anything.' Then confirm the choice in writing.

When the complaint is already public

Sometimes the first you hear of a problem is a one-star review. Run the same process, and add one step: a short public reply that acknowledges the experience and gives a direct contact. Pew found that 82% of adults at least sometimes read reviews before a first purchase^[4], so future customers will read the reply as closely as the complaint.

Google notifies the reviewer when you reply, and reviewers can change their review after reading the response^[5]. If you resolve the issue well, some will update the review on their own. Let that be their decision. The guide on responding to negative reviews covers the wording.

Example: one case from start to finish

Example: a fictional pest control customer calls on Monday saying ants are back a week after treatment. The office logs it as level 3, the service manager calls within three hours, apologizes for the trouble, explains that some treatments take more than one visit, and books a free re-service for Wednesday. On Wednesday the technician finds a new entry point by a dryer vent, treats it and seals it. The manager texts a summary that afternoon, calls the following Monday to check, and closes the case. The root cause tag is 'inspection missed entry point', and at the next team meeting the technicians review dryer vents as a common miss.

Preventing the most common complaints

The cheapest complaint is the one that never happens. When you tag root causes for a few months, the same handful usually rises to the top. Each has a simple preventive habit.

• Price surprises: explain how fees work on the booking call, and give written options with prices before any work starts.
• Late or missed arrivals: send confirmations, a reminder and an on-the-way text, and warn customers before the window closes if you are running late.
• Work not fixed: add a short test at the end of each job and show the customer the result working.
• Mess and damage: use drop cloths and shoe covers every time, and photograph the work area before starting on larger jobs.
• Poor communication: name one contact for each job and tell the customer how to reach them.

Share the monthly root cause summary with technicians and office staff together. Complaints often start in one part of the business and land in another, and the fix usually needs both sides in the room.

Measuring the process

• Complaints per 100 jobs, by service line and by technician.
• Share acknowledged within the target time for each severity level.
• Median days from complaint to closed case.
• Cost of remedies per month: return visits, credits and refunds.
• Top three root causes and what was changed for each.
• Customers who complained and booked again within a year.

Review these monthly alongside your survey results. Complaint handling links closely to your satisfaction guarantee and your workmanship warranty terms; the clearer those promises are, the easier each complaint becomes to resolve fairly.