M360 Compass

M360 Compass · Management insights

Customer complaint handling for small businesses

· 6 min

A coordinator on the phone and a technician examine a lighting controller on a service counter.

Customer complaint handling starts with an acknowledgement that names the problem, the person taking ownership and the time of the next update. It ends when the team checks the outcome with the customer or records its attempts to follow up. If the same issue appears in several files, assign someone to correct the process and check the effect. A small team can use this approach for service complaints that arrive by phone, email or at the counter.

What should you say at first contact?

Give the customer time to explain what happened. Then reflect the impact in one sentence. A controller unavailable on opening day and an identical controller that will sit on a shelf until next week can have the same problem with different urgency. Ask what would allow the customer to get back to work and when they need it.

In a fictional example, a shop receives a lighting controller with a different model code from the one on its order confirmation. The manager has booked a technician for the next morning. Joëlle, the supplier’s service coordinator, says, “I understand you need the lighting working by opening time tomorrow. I’ll check which model we have and call you back before 3 p.m. today.” She has committed to an update she can give even if the team is still working out a solution. The guide to workplace communication styles offers ways to adjust how much detail you give and confirm what the customer understood.

What belongs in a customer complaint handling log?

Open one record when the complaint arrives. Capture the file number, time, channel, reported impact, desired outcome, owner and next contact. If the customer calls and emails about the same order, link both exchanges to the first record. The colleague covering the counter can pick up the file without asking the customer to tell the whole story again.

In fictional file C-184, Joëlle records the model the customer reported, the model on the order and the code the team can see on the packaging. She flags any missing detail as an open question and asks for a photo of the model code, which is enough to move the case forward. Keep contact details and attachments in the service record where the team uses them. For a review of trends, the file number, the category and the facts needed to investigate are usually enough. The NSW Ombudsman guide describes what to record at intake and closure. NSW Ombudsman complaint management guide

What to record in fictional case C-184
StageEntry in the log
IntakeCustomer reports a different model. Shop opens tomorrow. Joëlle will call before 3 p.m.
CheckThe order and photo show different codes. The model on the order is in stock.
RemedyJoëlle confirms an exchange at the counter and shares the reserved model code.
Follow-upThe customer confirms the technician fitted the right model and the lights worked at opening.

How do you decide on a remedy and check it?

Agree on who can make common decisions. A confirmed order and an available part may let a coordinator resolve a case at first contact when they have authority to arrange the exchange. If a workshop decision is needed, name the person who will make it and the time they should reply. Keep one contact for the customer while colleagues coordinate. If the work takes longer, give the promised update and agree on the next time you will be in touch.

In the fictional case, Joëlle confirms the stock before 3 p.m. and the customer chooses to collect the part. The next morning she asks whether the technician completed the installation in time. The counter record shows the part was collected. The customer’s reply confirms that the shop had working lights when it opened. Joëlle logs both facts. If the problem persists, she reopens the case, records what went wrong with the remedy and sets another update. The Australian government business guide recommends recording commitments and contacting the customer after the fix. Business.gov.au guide to handling customer complaints

What should you do about recurring complaints?

Group records by problem at a regular team review. Count one complaint per case even when several people responded or the customer used more than one channel. Look for cases linked to the same product code, process step or time of day. Review open files and missed commitments to update the customer as well. The New South Wales business guidance recommends keeping records and checking regularly that the complaint procedure works. NSW Government guide for businesses

In the fictional example, three complaints in two weeks involve similar models. The team watches two orders being picked and sees that the pick slip shows only the product family. The workshop adds the full model code and asks staff to check it against the label before handing over the item. The workshop lead reviews the next 20 orders and records discrepancies caught at the counter and complaints received. The small trial gives the team a basis for keeping or adjusting the change. The guide to meeting decision follow-up shows how to agree on who will check the change and what they will bring back to the team.

How can M360 Compass help the team follow through?

Once you have agreed on a process change, M360 Momentum lets you record issues and decisions, identify owners and deadlines, and track actions between meetings. In the fictional case, the action could read “Check the full model code on the next 20 orders in this product family.” Individual customer conversations stay in the service file. At the next meeting, ask the workshop lead to show the revised pick slip and any mismatches they found. To see how to track that kind of action in the platform, request an M360 Compass demo.

Frequently asked questions about customer complaints

What if you do not know the cause yet?

Repeat the problem as you understand it, say what you will check and agree on the next update. You can give the customer a realistic option once you have verified the relevant facts.

When can you close a case if the customer does not reply?

Make the agreed follow-up attempts, record the dates and leave an easy way for the customer to get back in touch. Record the action you completed and mark the customer’s outcome as unconfirmed.

How do you count several messages about the same incident?

Attach them to the same file. Count the incident once and retain the dates of each exchange so you can check whether you met the promised follow-up times.

When should you open a separate action to prevent recurrence?

Open one when several files share a problem or a single case reveals a step that could affect other customers. Assign an owner and a review date, then agree on the result you want the owner to show.