Every business can make a mistake. A delivery may be late, a service may not meet an agreed expectation, a quotation may have been misunderstood or a customer may believe that a problem has not been resolved fairly.
What happens next can influence whether the issue is settled constructively or becomes a prolonged dispute.
Small businesses do not always need a complicated customer service department to handle complaints consistently. They do need a clear process that explains how a complaint is received, who investigates it, how decisions are recorded and what happens when the customer remains dissatisfied.
A written customer complaint procedure helps staff respond consistently and gives the business a record of what it did to address a concern.
For businesses serving customers in Maboloka, Soshanguve, Centurion and other parts of South Africa, the same basic principles apply: listen carefully, establish the facts, communicate clearly and follow through on agreed actions.
This guide explains how to design a practical procedure. It is general operational guidance, not legal advice or a statement that every business is subject to identical consumer-protection obligations.
1. Define the purpose and scope
Begin by explaining what the procedure is intended to achieve.
A useful objective is to ensure that customer complaints are acknowledged, assessed fairly, handled by an appropriate person and resolved or escalated through a documented process.
Define which complaints the procedure covers.
Depending on the business, these may include:
- Problems with the quality of a product or service.
- Delays or missed appointments.
- Billing or payment disputes.
- Disagreement about the agreed scope of work.
- Communication failures.
- Alleged damage or loss.
- Concerns about staff conduct.
- Requests to correct an earlier decision.
Decide whether the same procedure will cover complaints from suppliers, employees or other business stakeholders. These may require separate procedures because the parties, responsibilities and applicable rules can differ.
The document should state who it applies to, which business activities it covers and who approves changes to the procedure.
2. Distinguish complaints from ordinary enquiries
A customer enquiry is not necessarily a complaint.
A request for a quotation, a question about opening hours or a request for product information can normally follow the standard enquiry process.
A complaint indicates that the customer believes something has gone wrong or that the service received is unsatisfactory.
Staff should be able to recognise the difference without requiring the customer to use a particular word.
For example:
- "Can you tell me when my order will arrive?" may be an ordinary enquiry.
- "My order was supposed to arrive yesterday, and nobody has told me what happened" may indicate a complaint.
If staff are uncertain, they should clarify the concern rather than dismiss it.
Do not create a process that makes customers prove that they are entitled to complain before the business is willing to listen.
The purpose of the initial conversation is to understand the issue and identify the appropriate next step.
3. Explain how customers can submit a complaint
A procedure should make the available channels clear.
Depending on the business, customers may be able to complain through:
- Email.
- Telephone.
- A website contact form.
- A written letter.
- An in-person conversation.
- An established customer service or messaging channel.
Choose channels the business can realistically monitor. Listing an address or telephone number that nobody checks creates an expectation the business cannot meet.
If a complaint is received verbally, staff can record the relevant information in the complaints register and confirm their understanding with the customer.
If the complaint arrives through a messaging platform, preserve the relevant business record in an approved location rather than relying exclusively on one employee's phone.
Explain what information would help the business investigate the issue, such as a transaction reference, order number, date or description of the service.
Do not make it unnecessarily difficult to submit a complaint merely because the customer cannot provide every supporting document immediately.
4. Acknowledge the complaint
Once a complaint is received, the business should confirm that it has been recorded and explain what happens next.
An acknowledgement can include:
- A reference number, where the business uses one.
- A brief summary of the issue as understood.
- The person or team responsible for the next step.
- Any additional information required.
- The expected next communication.
- An appropriate way to provide further information.
Set a realistic internal acknowledgement target. For example, a business may aim to acknowledge ordinary complaints within one or two business days, provided that target is appropriate for its capacity and operating arrangements.
This is an illustrative service standard, not a universal statutory deadline.
If the business cannot meet its normal target, it should communicate the delay and provide a revised expectation rather than allowing the customer to wonder whether anyone is dealing with the complaint.
Acknowledgement does not mean that the business has accepted responsibility. It means that the concern has been received and will be considered.
5. Record the facts consistently
Good complaint handling depends on reliable information.
A complaints register can be a controlled spreadsheet or another suitable system. The right level of detail depends on the business and the sensitivity of the information involved.
A basic register may include:
| Field | Purpose |
|---|---|
| Complaint reference | Identify the case |
| Date received | Establish when the issue was reported |
| Customer or transaction reference | Locate the relevant business record |
| Complaint category | Identify the type of problem |
| Description | Summarise the customer's concern |
| Responsible person | Identify who owns the next step |
| Evidence required | Record information still needed |
| Current status | Track progress |
| Agreed next action | Make responsibilities clear |
| Target review date | Prevent cases from being forgotten |
| Outcome | Record the resolution or escalation |
| Closure date | Show when the process ended |
Keep the record factual and professional.
Avoid subjective labels such as "difficult customer" or speculative comments about the customer's motives. Record what was reported, what was investigated and what action was taken.
If the complaint involves a disputed statement, distinguish the customer's account from the business's verified findings.
6. Assign responsibility for investigating the issue
Every complaint should have a clear owner.
In a small business, this might be the owner, manager or person responsible for the relevant service.
The person handling the complaint should have enough authority to investigate the issue, communicate with the customer and recommend an appropriate response.
Where possible, avoid asking someone to make the final decision on a complaint about their own conduct without independent review.
The procedure should identify when a complaint must be referred to a manager or another authorised person.
Examples include:
- A significant financial dispute.
- Alleged misconduct.
- A safety concern.
- A complaint involving potential legal exposure.
- A repeated failure to deliver an agreed service.
- A case where the proposed remedy exceeds the handler's authority.
Clear responsibility prevents a complaint from being passed between staff without anyone taking ownership.
7. Investigate before deciding
Do not assume that the first account of an event tells the complete story.
The investigation should establish what was agreed, what happened and what evidence is available.
Depending on the issue, review:
- The quotation or contract.
- Relevant invoices or receipts.
- Delivery or service records.
- Correspondence.
- Photographs or other supporting material.
- Internal notes.
- The customer's explanation.
- Relevant supplier information.
Give the customer an opportunity to clarify important details where necessary.
Distinguish between a confirmed fact, an allegation and an unresolved question.
For example, a customer may state that a service was not delivered as agreed. The business should review the agreed scope and available evidence before deciding whether the complaint is justified.
The procedure should also specify how staff handle missing evidence and what to do when the facts remain uncertain.
An investigation should be proportionate to the issue. A minor administrative error may require a simple check, while a significant dispute may need a more formal review.
8. Decide on a fair and practical resolution
After reviewing the evidence, identify the available options.
Depending on the circumstances and the agreement, a resolution might involve:
- Correcting an administrative error.
- Completing an outstanding part of the service.
- Repeating or repairing work where appropriate.
- Providing a clear explanation.
- Agreeing on a revised delivery arrangement.
- Considering a refund, credit or other remedy where justified.
- Referring the issue for further review.
Do not promise a remedy before checking the relevant facts, authority and contractual or legal requirements.
The resolution should address the actual concern rather than simply closing the case.
Explain the decision in plain language. Where appropriate, state what was established, what action will be taken and when the customer can expect it.
If the business does not uphold the complaint, explain the reasoning respectfully and identify any available review or escalation route.
A fair process does not require the business to agree with every complaint. It requires the business to consider concerns consistently and make decisions on an appropriate basis.
9. Set realistic response and resolution targets
A complaint procedure becomes difficult to manage when it says only that issues will be handled "as soon as possible".
Define internal targets for acknowledgement, initial assessment, progress updates and resolution where those targets are practical.
The targets may differ according to complexity.
For example:
| Stage | Illustrative internal target | Purpose |
|---|---|---|
| Acknowledgement | Within 1-2 business days | Confirm receipt |
| Initial assessment | Within 3-5 business days | Identify the issue and required evidence |
| Progress update | By the agreed review date | Explain the current position |
| Resolution proposal | According to complexity and applicable requirements | Communicate the proposed outcome |
| Escalation | When the case meets defined criteria | Obtain a higher-level review |
These are examples for planning, not legal deadlines or recommended universal standards. A business should select targets appropriate to its operations and confirm any statutory or contractual time limits that apply.
Some complaints can be resolved quickly. Others require supplier input, technical investigation or specialist advice.
If the business needs more time, communicate the reason and provide a realistic update date. Do not promise a deadline simply to end an uncomfortable conversation.
10. Protect customer information
Complaints can involve personal information, financial details, correspondence or other confidential material.
Restrict access to people who need the information to perform their responsibilities. Keep records in approved business systems and avoid spreading details through unnecessary email chains or informal messaging groups.
The Protection of Personal Information Act and other applicable requirements may affect how the business collects, uses, stores and retains complaint records.
The Information Regulator's privacy notice describes principles relating to the retention and secure disposal of personal information. Businesses should review the requirements applicable to their own processing rather than treating another organisation's privacy notice as a complete compliance template.
Practical measures include:
- Recording only relevant information.
- Using controlled access to complaint records.
- Keeping supporting documents in appropriate storage.
- Avoiding unnecessary duplication of sensitive information.
- Applying an appropriate retention schedule.
- Disposing of records securely when retention is no longer justified and no hold or legal requirement applies.
A complaint should be handled discreetly. Staff should not discuss a customer's case with people who have no legitimate role in resolving it.
11. Provide an escalation route
Some complaints remain unresolved after the initial investigation.
Your procedure should explain how a customer can request a review and who will conduct it.
An escalation may be appropriate when:
- The customer disputes the findings.
- New evidence becomes available.
- The proposed remedy is rejected.
- The original handler lacks authority.
- The complaint concerns a serious issue.
- The initial process has not resolved the matter.
The reviewing person should examine the record, the decision and any new information rather than automatically repeating the original response.
The procedure should also explain that external options may be available in appropriate cases.
South Africa's National Consumer Commission complaints guidance explains how consumers can submit complaints alleging contraventions of the Consumer Protection Act. The Commission encourages complainants to provide transaction details, proof of purchase, steps already taken to resolve the matter and relevant communications.
The Commission's service standards describe its complaint-handling process and the importance of supporting documentation.
A business should not claim that its internal procedure replaces statutory consumer rights or prevents a customer from using a lawful external route.
Applicability and available remedies depend on the circumstances and the law.
12. Close the complaint properly
A complaint should not be marked as resolved merely because the business has sent a message.
Record the outcome and any agreed actions.
Before closing the case, check:
- Was the decision communicated to the customer?
- Were promised actions completed?
- Were relevant supporting records retained?
- Was the final status recorded?
- Does the case require follow-up?
- Is any further review or hold necessary?
Where appropriate, ask the customer to confirm that an agreed practical action has been completed. However, do not make closure depend on receiving a response in every case if the business has completed its obligations and the procedure permits administrative closure.
If the issue remains unresolved, record that status accurately and explain the next step.
Good closure records help the business understand what happened and identify recurring problems.
Mogen's Business Documentation
If your business needs a written complaint procedure, supporting forms or a consistent document system, explore Mogen's Business Documentation service.
13. Use complaints to improve operations
Complaint records can reveal patterns that are difficult to see when every issue is handled informally.
Review the register periodically to identify:
- Repeated delivery problems.
- Common misunderstandings about quotations.
- Inconsistent communication.
- Frequently disputed charges.
- Recurring product or service defects.
- Delays in responding to customers.
- Problems that require clearer internal procedures.
Focus on recurring causes rather than blaming individual customers.
If several complaints arise because a quotation does not explain exclusions, improve the quotation template. If customers repeatedly misunderstand a booking process, review the instructions. If enquiries are delayed because nobody monitors a shared inbox, assign ownership.
Record significant corrective actions and review whether they worked.
The aim is to make the business more reliable over time, not simply to count complaints.
14. Train staff to use the procedure
A written procedure is useful only if people know how to apply it.
Explain the process to staff who interact with customers. Give them examples of how to acknowledge a complaint, record facts, protect confidential information and escalate an issue they cannot resolve.
Make the latest approved version easy to find.
Avoid giving every employee authority to promise refunds or other remedies without clear boundaries. At the same time, ensure that the process does not prevent staff from addressing straightforward issues within their responsibilities.
Review the procedure when the business changes its services, customer channels, internal structure or applicable requirements.
A small business may begin with a concise procedure and a register. More complex operations may need additional forms, approval rules, service standards and specialist review.
A simple complaint procedure outline
A first version of the document can use the following structure:
- Purpose and scope.
- Definitions and complaint categories.
- Approved complaint channels.
- Roles and responsibilities.
- Acknowledgement and recording.
- Investigation and evidence handling.
- Decision-making authority.
- Resolution and customer communication.
- Response targets and progress updates.
- Escalation and review.
- Privacy and record keeping.
- Closure and corrective action.
- Monitoring and review of the procedure.
- Document owner, approval date and version history.
This outline is a starting point, not a prescribed legal format. Adapt it to the business's operations and have the relevant requirements checked before formal approval.
Frequently asked questions
Does every small business need a formal complaints policy?
The specific obligations depend on the business and applicable law. Even where a particular document is not expressly required, a written process can help staff handle issues consistently and retain an accurate record of decisions.
How quickly must a business resolve a complaint?
There is no single response time that should be assumed to apply to every complaint and business situation. Check the relevant legal, regulatory and contractual requirements, then set realistic internal targets and communicate delays.
Should a business admit fault when acknowledging a complaint?
Acknowledgement means the concern has been received, not that liability has been established. Staff should record the concern accurately, investigate it and communicate the findings and appropriate next steps.
What should be included in a complaints register?
At minimum, record the date, issue, responsible person, status, next action and outcome. Add supporting references and review dates where useful, while limiting unnecessary personal information.
Discuss your documentation requirements
If you need help structuring a customer service procedure, internal policy or supporting form, contact Mogen to discuss the intended use and scope.
Conclusion
A practical customer complaint procedure helps a business respond consistently, investigate concerns fairly and record what was done to resolve them.
Start with clear responsibilities and accessible complaint channels. Acknowledge issues, collect relevant evidence, set realistic response targets and explain the available resolution or escalation steps.
Then review complaint records for recurring problems that can be prevented through better communication, improved service delivery or clearer documentation.
For growing South African businesses in Maboloka, Soshanguve, Centurion and surrounding areas, a proportionate written process can support better customer relationships without creating unnecessary administration.
Confirm the legal and contractual requirements relevant to your business, and make sure the procedure reflects the way the business actually operates.