How should a contractor document and resolve a customer complaint? | Insights | Contractor SystemsSkip to content

Insights

How should a contractor document and resolve a customer complaint?

Use one contractor customer-complaint process to capture the customer's words, assign the right owner, document every promise, and close the issue with evidence.

By Kyle Burt·Founder, Contractor Systems·November 16, 2026·6 min read

A homeowner discussing a residential project with a contractor at the jobsite.

A customer complaint can enter through a phone call, text, Google review, email, or a conversation with the crew. If each channel creates a different version of the problem, the complaint gets harder to solve every time somebody touches it.

The first note says, “Customer is upset.” The project manager remembers a price question. The technician heard that something was damaged. The owner promises to call, but nobody records when. By Friday, the company is arguing about what the customer meant instead of fixing what happened.

A contractor customer-complaint process should create one factual record, assign one owner, and give the customer a specific next update. It should also separate the complaint from the final decision. The person who answers the call can take the concern seriously without promising a refund, free work, or fault before the facts are checked.

Open one complaint record

Do not leave a complaint inside the channel where it arrived. A text thread is not an owner. A negative review is not the full customer history. A note on a crew member’s phone will not help the office when the customer calls again.

Connect the complaint to the correct customer, property, job, estimate, invoice, and prior communication. Then record:

  • Date, time, and channel received
  • Customer’s name and best contact method
  • Job, invoice, or estimate involved
  • Customer’s description in their own words
  • Dates, locations, products, employees, or work areas mentioned
  • Photos, messages, invoices, or other documents supplied
  • What the customer says would resolve the problem
  • Any immediate safety, damage, access, or schedule concern
  • Person who accepted the complaint
  • Owner of the next action
  • Exact time of the next customer update

This is close to the information the Federal Trade Commission tells consumers to include in an effective complaint: the transaction, the problem, the requested resolution, supporting documents, contact information, and a response date. California’s Contractors State License Board also asks a complainant for project information, contract and payment details, the items of complaint, the requested resolution, and supporting documentation.

You do not need to turn every unhappy call into a legal file. You do need enough detail that the next person can understand the complaint without making the customer start over.

Write what the customer said before writing what you think

“The crew damaged my driveway” is the customer’s statement. “Existing crack, not our fault” is an internal conclusion. Those are not the same kind of note.

Record the statement first. Then add observations, documents, and internal conclusions in separate fields or entries. Use names and timestamps. If the customer says the estimator promised a specific repair, find the estimate, call record, email, or message before deciding that the promise did or did not happen.

Avoid loaded notes such as “difficult customer,” “trying to get free work,” or “always complains.” They do not help anyone inspect the issue. They also make the record harder to defend if it is later shared with management, an insurer, an attorney, or a licensing agency.

A useful note sounds more like this:

Customer called at 10:20 a.m. and said two pavers near the west gate cracked after the crew moved equipment through that area. Customer asked the company to replace the two pavers. Photos requested by text. Jobsite photos and crew notes assigned to Dana for review. Dana will call the customer by 3 p.m. today.

That note does not decide fault. It preserves the complaint and the next commitment.

Put the complaint into the right lane

Not every complaint should follow the warranty process. Sort the issue before assigning the response.

A workmanship or product concern should connect to the original scope, closeout record, photos, and warranty terms. Use the contractor warranty-callback process when inspection and coverage are the decision.

A price or invoice complaint needs the approved estimate, change orders, credits, payments, and current invoice. Do not send the field technician to negotiate a billing record they cannot see.

A scheduling or communication complaint needs the promised date, messages sent, missed checkpoint, and new owner. If the schedule moved, use the project-delay communication process rather than sending another vague apology.

A property-damage or safety complaint may need immediate site control, management, an insurer, or legal advice. Your company should have written escalation triggers for active leaks, electrical or gas concerns, injuries, threats, alleged theft, major damage, discrimination claims, and contact from an attorney, regulator, or insurer. The intake person should not investigate those alone.

A conduct complaint about an employee or subcontractor should go to someone who can protect privacy, gather separate accounts, and decide the work assignment. Do not post the accusation in a group chat or ask the accused person to handle the customer response.

The lane determines who owns the facts. It should not decide the outcome before the review happens.

Give one person the next promise

“The office will call you” is not ownership.

Name the person, action, and time. A useful first response might be:

I have your concern attached to the Miller Street job. Dana is reviewing the signed scope, photos, and crew notes. She will call you by 3 p.m. today, even if the review is still open.

The deadline is for the next update, not necessarily the final resolution. Some complaints need a site visit, a supplier answer, or a conversation with the crew. The customer can handle an honest review period better than silence.

If the owner cannot meet the promised time, the owner still contacts the customer. “We are waiting on the supplier” can be a valid update when it includes what was requested and when the next check will happen.

Do not let several people make separate offers. One employee promises a repair, another offers a credit, and the owner later rejects both. Now the company has created a second complaint about its response to the first one.

Keep the resolution tied to evidence

The resolution record should show what the company reviewed, what it decided, what it offered or completed, and what remains open.

Possible outcomes include correcting covered work, completing an omitted scope item, explaining the written price, issuing an approved credit or refund, repairing documented damage, referring a product claim, declining a request with the supporting reason, or scheduling another inspection because the cause is still unknown.

Record the customer’s response without rewriting it to sound more favorable. If they accept a repair date, save the date and scope. If they disagree, preserve the disagreement and the next escalation. If the company pays, repairs, or credits something as a business decision without admitting fault, make sure the customer-facing language and internal approval match the advice of the company’s insurer or attorney when that matters.

Jobber’s current notes documentation is one example of how field software can support this record. It allows notes and attachments on clients, requests, quotes, jobs, visits, and invoices, with authors, timestamps, linked records, editing indicators, permissions, and photos or files. Whatever system you use, test whether the complaint history stays connected when the issue moves from the office to the job and then to billing.

Close the complaint only after the promised work is checked

Changing a status to “resolved” does not resolve anything.

Before closing the record, confirm:

  • The assigned action was completed or the final decision was delivered
  • Photos, documents, credits, repairs, or inspection findings are attached
  • The customer received a plain-language summary
  • Any future appointment or payment change appears in the operating system
  • A manager reviewed any unresolved disagreement or escalation
  • Review reminders and routine automation will not send a careless message into an active dispute

Keep the original complaint, the work performed, and the final answer together. Do not delete the first note after the company learns more. The history matters, especially if the same issue comes back.

Audit one complaint this week

Pick one recent complaint that arrived by phone, text, review, or field conversation. Can you find the customer’s exact concern, the related job and documents, the named owner, every promised update, the decision, the work completed, and the final customer message without searching personal phones?

If not, start with a complaint status, a required next-update field, and one owner. Software will not make a vague process accountable. It can make a clear process visible.

Contractor Systems keeps calls, texts, and customer history together while connecting with the field software your team already uses. Review the one lead inbox and field-service integrations, then see the connected customer workflow and compare it with the last complaint your team handled.

Sources

Want this handled for you?

Contractor Systems is one monthly system for the website, the inbox, the follow-up, and the reviews. $297/mo. No contracts on monthly or quarterly plans.

More insights

$297/mo

One system

See it in action