How Should a Small Business Handle Customer Complaints?

By Bill Stilwell · Last reviewed October 17, 2026

The short answer

When a customer complains, write down what happened, deal with any safety risk first, and confirm you received it with a clear time for your next reply. Look at the records before you decide. Then fix it, explain it, refund it, or escalate it under your written policy. Send threats, claims, and government contacts to the right professional, and track complaints so the same problem stops happening.

Why it matters

A complaint is a customer telling you they’re about to leave or post a bad review. Handled fast and fairly, many turn into loyal customers. Handled slowly, they turn into reviews, chargebacks, or legal claims. A written process also keeps you calm when you’re upset, and the records protect you if the matter goes further.

17.8.1 Complaint intake

What it means: recording what happened, when, where, and who was involved.

How to do it: use one complaint log for every channel: phone, email, text, in person, and reviews. Record the date received, customer, job number, what they say happened, what they want, and who took it. Use the customer’s own words where you can.

Common mistake: a complaint taken by phone that only lives in one person’s memory.

17.8.2 Immediate safety

What it means: handling injury, danger, damage, or urgent risk before anything else.

How to do it: if anyone is hurt or in danger, get help first and follow your emergency steps (see 22.9 Emergency Procedures and 11.9.6 Severe Injury). Stop work if needed (see 11.4.7 Stop-Work Procedure). Protect property from more damage. If a worker is badly hurt, federal Occupational Safety and Health Administration (OSHA) rules require employers to report a work-related death within 8 hours, and an in-patient hospitalization, amputation, or loss of an eye within 24 hours. Call your insurance company early.

Common mistake: arguing about who’s at fault while water is still leaking.

17.8.3 Acknowledgment

What it means: confirming you received the complaint and when they’ll hear from you next.

How to do it: reply within one business day, sooner if it’s urgent. Thank them, say who is handling it, and give a date for your next update. Don’t admit fault or promise a specific fix before you’ve looked into it.

Common mistake: waiting until you have the full answer, so the customer hears nothing for a week.

17.8.4 Investigation

What it means: looking at the records, messages, scope, and evidence before deciding.

How to do it: pull the agreement, scope, change orders, photos, messages, and quality checklist for the job (see 17.5 Project Delivery and 17.7 Quality Control). Talk to the people who did the work. Visit the site if needed. Write a short summary of what you found.

Common mistake: deciding based on how upset the customer sounds instead of what the records show.

17.8.5 Resolution

What it means: offering a fair fix, explanation, refund, credit, or escalation.

How to do it: use your written refund, warranty, and cancellation policies so customers in the same spot get the same answer (see 11.1.8 Refund Policy and 11.1.9 Warranty). Explain your decision in plain words and put it in writing. If you offer money, record the amount and how it was paid (see 10.7.8 Refunds).

Common mistake: making up a different deal for each customer, which creates claims of unfair treatment.

17.8.6 Legal escalation

What it means: sending threats, claims, government contacts, or serious disputes to the right professional.

How to do it: decide in advance what triggers escalation. Common triggers are a lawyer’s letter, a threat to sue, an injury, a property damage claim, a demand over a set dollar amount, or a contact from a licensing board, the state attorney general, or another agency. Stop arguing with the customer, save every record, and call your attorney and insurer (see 6.3.1 Business Attorney and 6.3.4 Insurance Professional).

Common mistake: replying to a lawyer’s letter yourself in anger.

17.8.7 Trend tracking

What it means: recording complaints that repeat and what you changed because of them.

How to do it: give each complaint a cause category, like scheduling, quality, price, communication, or damage. Review the log monthly. When one cause repeats, fix it at the source and note the change.

Common mistake: closing each complaint and never looking at them together.

22.7.1 Receive

Record every complaint and refund request in the same log, as in 17.8.1 above. The procedure version of this step lives in your written procedures binder (see 22.1 Writing Standard Operating Procedures).

22.7.2 Protect

Handle safety, privacy, and urgent risks first, as in 17.8.2. If the complaint involves someone’s personal information, limit who sees it and follow 11.9.4 Data Breach Response if data was exposed.

22.7.3 Investigate

Review the scope, records, messages, and evidence, as in 17.8.4. The procedure should name who investigates and how long they have.

22.7.4 Decide

Apply your approved policy, as in 17.8.5. The procedure should say who can approve refunds or credits and up to what amount (see 10.6.1 Spending and Refund Authority).

22.7.5 Communicate

Explain the outcome in writing, in a calm and professional tone. Keep a copy in the complaint log.

22.7.6 Escalate

Send serious or disputed matters to the owner, attorney, or insurer, using the triggers in 17.8.6.

22.7.7 Learn

Record the cause and the change you made, as in 17.8.7. Update the related procedure so the fix sticks.

Public reviews and complaints

If the complaint shows up as a review, reply politely and briefly, and move the details to a private conversation (see 14.6.3 Review Responses and 14.6.4 Negative Review Escalation). After you fix a problem, you may ask the customer if they’d like to update their review. The Federal Trade Commission (FTC) says its review rule doesn’t stop you from contacting customers to resolve issues. It does ban unfounded legal threats, physical threats, intimidation, and knowingly false accusations used to get a review removed. Never offer money or a refund on the condition that they change or remove a review. Google’s policy also says businesses can’t offer incentives to remove a negative review.

When to get help from a pro

An attorney can help you set escalation triggers and handle legal threats. Your insurance professional can tell you when to report a possible claim. Questions to ask:

At what point should I stop talking to an unhappy customer and call you?
Does my insurance require me to report complaints that could become claims, and how fast?
Can my refund or settlement letters include a release, and what should it say?

Bill’s note

[Bill: add a short note. For example, how you handle an unhappy SiteSmarty client, or a complaint that turned into a long-term customer because it was handled fast.]

If you’d rather have help with this, SiteSmarty helps businesses monitor and respond to Google reviews.

How I did this for SiteSmarty

[Date I did this:]
[What I actually did, step by step: the SiteSmarty complaint log, acknowledgment message, and escalation triggers]
[What it cost and how long it took:]
[What surprised me or what I’d do differently:]
[Screenshot or photo to add, with private info blurred: the complaint log template and acknowledgment message]
[Result so far:]

Questions people ask

What should I write down when a customer complains? The date, customer, job, what they say happened, what they want, and who took the complaint.

How fast should I respond? Acknowledge within one business day, sooner for urgent or safety issues, and give a date for your next update.

When should I offer a refund? When your written refund or warranty policy says to, after you’ve checked the records. Treat similar cases the same way.

When should I call a lawyer? When you get a lawyer’s letter, a threat to sue, an injury or damage claim, a large demand, or a contact from a government agency.

Can I ask a customer to update a bad review after I fix the problem? You can ask, but never make a refund or credit depend on it, and never threaten or pressure them.

Audit check

Outline line	Question	Pass looks like	Fail looks like	Evidence to collect
17.8.1 Complaint intake	Is every complaint recorded in one log?	All channels logged with details	Complaints lost in phones and inboxes	Complaint log
17.8.2 Immediate safety	Are safety risks handled first?	Safety steps followed and recorded	Delay while arguing fault	Incident records
17.8.3 Acknowledgment	Is every complaint acknowledged within one business day?	Prompt reply with next update date	Days of silence	Acknowledgment messages
17.8.4 Investigation	Are decisions based on records?	Written findings	Decisions with no review	Investigation notes
17.8.5 Resolution	Are resolutions based on written policy?	Same answer for similar cases	Different deals each time	Policies and resolution records
17.8.6 Legal escalation	Are escalation triggers written and followed?	Attorney or insurer called when triggered	Owner argues with lawyers	Trigger list and escalation log
17.8.7 Trend tracking	Are repeat causes tracked and fixed?	Monthly review with changes noted	No review	Log with cause categories
22.7.1 Receive	Is there a written intake step?	Procedure names the log	No procedure	Written procedure
22.7.2 Protect	Does the procedure cover safety and privacy?	Safety and privacy steps listed	Missing	Written procedure
22.7.3 Investigate	Does the procedure name who investigates and by when?	Owner and time limit set	Unclear	Written procedure
22.7.4 Decide	Are approval limits set for refunds and credits?	Named approvers and limits	Anyone can refund any amount	Authority list
22.7.5 Communicate	Are outcomes sent in writing?	Written outcome on file	Verbal only	Outcome letters
22.7.6 Escalate	Are serious matters escalated?	Escalation recorded	Handled alone	Escalation log
22.7.7 Learn	Are procedures updated after repeat complaints?	Dated procedure updates	No changes	Procedure change log

Where this fits

Do this first: 17.7 Quality Control, 11.1.8 Refund Policy

Do this next: 17.10 Retention and Reactivation

Sources

Occupational Safety and Health Administration (OSHA), "Report a Fatality or Severe Injury" (checked October 17, 2026)
Federal Trade Commission, "The Consumer Reviews and Testimonials Rule: Questions and Answers" (checked October 17, 2026)
Google, "Prohibited and restricted content" (Maps user contributed content policy) (checked October 17, 2026)
Google Business Profile Help, "Tips to improve your local ranking on Google" (checked October 17, 2026)

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.