When New Zealand Businesses Need a Complaints Handling Policy

Alex Solo
byAlex Solo12 min read

A complaints handling policy often gets left until something goes wrong. A customer escalates an issue publicly, a regulator asks how complaints are managed, or a service contract requires a formal process and nobody can point to one. Common mistakes include relying on an informal inbox system, copying a policy that does not match how the business actually operates, and accepting another party's standard complaints process without checking who carries the risk.

For New Zealand businesses, a complaints handling policy is not just a customer service document. It can sit alongside your contracts, privacy practices, refund position, staff procedures and industry obligations. If your team deals with customer dissatisfaction, service failures, privacy concerns or product quality issues, the way you receive, record, investigate and resolve complaints matters.

This guide explains when a New Zealand business is likely to need a complaints handling policy, what the policy should cover, the legal issues to review before you sign a contract that refers to one, and the mistakes founders and SME owners commonly make.

Overview

A complaints handling policy sets out how your business receives, assesses, responds to and closes complaints. In practice, it helps you handle disputes consistently, reduce legal risk and show customers, partners and regulators that you take issues seriously.

For many New Zealand businesses, the real question is not whether complaints happen, but whether the business has a clear process before a problem escalates.

  • Check whether a customer contract, supplier agreement, franchise arrangement or procurement contract requires a documented complaints process.
  • Make sure the policy matches your actual operations, including response timeframes, decision-makers and escalation steps.
  • Review how the policy interacts with the Consumer Guarantees Act, Fair Trading Act and any refund, repair or service commitments you give customers.
  • Consider whether complaints may involve personal information, and align the process with your Privacy Act obligations and privacy notice.
  • Train staff so they know the difference between a general customer enquiry, a refund request, a formal complaint and a report of serious misconduct.
  • Check whether your industry has extra expectations around internal dispute resolution, record-keeping or external review options.

What Complaints Handling Policy Means For New Zealand Businesses

A complaints handling policy is a practical rulebook for what happens after a customer, client or business partner says something has gone wrong. It is usually an internal policy, but parts of it may also be published to customers or incorporated into contracts.

For a small business, this might be a short procedure that tells staff how to log complaints and when to escalate them to a manager. For a larger SME, it may be a more formal document that sets service standards, investigation steps, reporting obligations and links to regulatory requirements.

When a business usually needs one

Many businesses do not ask for a complaints handling policy by name until a contract, tender or compliance process puts it on the table. Even so, there are clear founder moments where having one becomes sensible.

You are more likely to need a written policy where:

  • you provide services directly to consumers and complaints about quality, timing or outcomes are common;
  • you handle sensitive customer information and complaints may involve privacy concerns;
  • you operate in an industry where clients expect formal dispute resolution processes;
  • you are responding to a procurement request or due diligence checklist that asks for customer complaint procedures;
  • you licence, distribute or white-label products or services and the contract allocates complaint management responsibilities;
  • you have multiple staff members dealing with customers and need consistency.

This is especially relevant before you sign a contract with a large customer or commercial partner. Their standard terms may require your business to maintain a complaints handling policy, meet specific response times or report complaint trends. If you accept those terms without checking your internal process, you may commit to standards you cannot realistically meet.

Why it matters beyond customer service

A complaints handling policy can affect legal risk in several ways. The first is consistency. If one customer is offered a refund immediately and another is ignored for weeks, you increase the chance of escalation, reputational damage and allegations of unfair treatment.

The second is evidence. When a complaint turns into a payment dispute, termination issue or threatened claim, a clear record of what was raised, when it was acknowledged and how it was addressed can make a big difference.

The third is compliance. New Zealand businesses often need to align complaint handling with broader legal obligations, such as:

  • the Consumer Guarantees Act 1993, where consumers may have rights relating to faulty goods or services not provided with reasonable care and skill;
  • the Fair Trading Act 1986, where misleading statements about remedies, returns or service standards can create risk;
  • the Privacy Act 2020, where complaints may involve access requests, correction requests or concerns about how personal information was used or disclosed;
  • contract law principles, where your customer terms or supplier agreement may promise a specific process or timeframe.

A policy does not replace these legal obligations. It helps your business respond to issues in a way that supports them.

What a useful policy usually covers

A good complaints handling policy should be easy for staff to follow under pressure. If it reads like a generic compliance document, people often ignore it when an angry customer is on the phone.

Most policies should cover:

  • what counts as a complaint, and what does not;
  • how complaints can be made, such as email, phone, web form or in person;
  • who is responsible for receiving and recording complaints;
  • when staff must escalate a complaint to a manager or specialist team;
  • expected acknowledgement and response timeframes;
  • how investigations are conducted and documented;
  • what remedies may be available, such as repair, re-performance, replacement, refund or apology;
  • how privacy issues are handled if personal information is involved;
  • when the business may refer the customer to an external scheme, regulator or dispute process if relevant;
  • how complaint records are stored and reviewed.

The right level of detail depends on your size, industry and contracts. A sole trader consultancy may not need a 20 page manual. A healthcare-adjacent service provider, finance-related operator or business serving vulnerable customers will usually need a more structured approach.

Internal policy or contractual commitment?

This is where founders often get caught. A complaints handling policy can sit in different places, and each creates different obligations.

Sometimes it is purely internal, used by staff as a procedure manual. Sometimes parts of it are published in customer-facing terms, onboarding documents or service agreements. Sometimes a business promises in a B2B contract that it has, and will maintain, a complaints process meeting certain standards.

That distinction matters because once a policy is incorporated into a contract, failing to follow it may become a breach of contract, not just a messy internal process problem. Before you sign, check whether the policy is:

  • informational only;
  • an internal governance document;
  • a contractual commitment with service levels or reporting obligations;
  • part of a regulated compliance framework.

Before you sign a contract that mentions complaints handling, make sure the promised process is one your business can actually deliver. The main risk is accepting broad wording that sounds harmless, then discovering it creates strict response obligations, record-keeping duties or liability exposure.

Does the contract require a formal policy?

Some contracts simply say each party must maintain an effective complaints handling process. Others go further and require a written policy, annual review, staff training, reporting and audit rights.

Before you accept the provider's standard terms or a customer's procurement contract, check:

  • whether the policy must be documented in writing;
  • whether it needs to follow a prescribed format or standard;
  • whether you must provide a copy on request;
  • whether the other party can audit your compliance;
  • whether failure to maintain the policy is a material breach.

If the contract uses vague words like prompt, appropriate or best practice, ask what those mean in practice. Vague drafting can cause arguments later.

What response times are you promising?

Timeframes are often where a reasonable sounding clause becomes risky. A term requiring acknowledgement within 24 hours and resolution within 5 business days may be manageable for minor issues, but not for technical faults, third-party supply problems or complaints that require factual investigation.

Before you sign, match any promised timeframes against how your team actually works. Think about weekends, leave, public holidays, contractor dependencies and after-hours complaints. If the timeframe is unrealistic, negotiate it before you rely on a verbal promise that the other party will be flexible.

How does the policy fit with customer rights?

Your complaint process should support, not water down, legal rights customers may already have. A business cannot use a policy to sidestep obligations that arise under consumer law.

That means you should review whether your policy and related contracts are consistent with:

  • repair, replacement or refund rights that may apply to consumers;
  • any service guarantees or express warranties your business offers;
  • statements in your quotes, proposals, ads or sales scripts;
  • your limitation of liability clauses, where those are legally effective.

If your policy says all complaints will be dealt with by store credit only, for example, that may not line up with legal rights in every case. If your marketing says no questions asked refunds but your internal procedure makes refunds almost impossible, that inconsistency can also create trouble.

Will complaints involve personal information?

Many complaints include names, contact details, purchase history, call recordings, CCTV footage, staff notes or sensitive factual allegations. That brings privacy and data protection obligations into the picture.

Before you sign, check how your policy deals with:

  • collecting only the information reasonably needed to assess the complaint;
  • storing records securely;
  • limiting internal access to people who need to know;
  • responding if the complainant asks for access to complaint records;
  • retaining and deleting records in line with your broader document practices.

If the complaint process is outsourced or managed through a third-party software platform, review the service terms and privacy position as well. The legal issue is not just operational convenience, it is whether personal information is handled lawfully and transparently.

Who carries the risk in multi-party arrangements?

If you distribute someone else's product, provide white-label services, subcontract work or operate under a franchise or marketplace model, complaint handling can become blurred. Customers may complain to you about a problem caused by someone else. Your upstream contract may then decide who investigates, who pays, who communicates with the customer and who bears the cost of refunds or remediation.

Before you sign a contract in that setting, look closely at:

  • which party is the first point of contact for complaints;
  • whether you must follow another party's script or approval process;
  • who decides remedies;
  • who pays the cost of rework, refunds or credits;
  • whether indemnities apply if complaint handling is mishandled;
  • what reporting obligations apply between the parties.

This is one of the most common pressure points in commercial contracts because the customer sees one brand, while the legal responsibility may sit elsewhere.

Common Mistakes With Complaints Handling Policy

The biggest mistake is treating a complaints handling policy as a box-ticking document. If the policy does not match real workflows, staff capacity and contract terms, it can create more risk than having no policy at all.

Using a generic template without tailoring it

Plenty of businesses start with a borrowed policy. The problem is that copied wording often includes escalation paths, statutory references or remedy options that do not fit the business.

A café, software provider, childcare-related service and logistics company do not handle complaints the same way. The right process depends on what you sell, who you sell to, and how often complaints involve safety, privacy, service failure or third-party suppliers.

Confusing complaints with ordinary support requests

Not every unhappy email is a formal complaint, but staff need a clear line. If your team treats serious complaints as routine support tickets, issues can sit unresolved until the customer escalates publicly or stops paying.

Your process should distinguish between:

  • general enquiries;
  • technical support requests;
  • requests for refunds or credits;
  • formal complaints about conduct, quality or service failure;
  • serious incidents that require immediate legal or management review.

Without those categories, businesses often underreact to the issues that need escalation and overcomplicate the issues that do not.

Promising outcomes you cannot guarantee

Some policies are drafted with customer-friendly language that goes too far. Statements like every complaint will be resolved within 48 hours or all dissatisfied customers will receive a refund can create contractual, commercial or legal problems.

It is better to promise a fair process than an outcome your business cannot always deliver. You can commit to acknowledgement, review, communication and appropriate resolution without locking yourself into automatic concessions.

Ignoring record-keeping

If a complaint later turns into a chargeback, contractual dispute or regulatory query, poor records become an immediate weakness. Verbal discussions, undocumented promises and scattered email trails make it much harder to show what happened.

Your business should decide:

  • where complaints are logged;
  • what minimum information must be recorded;
  • who can update or close a complaint file;
  • how outcomes are approved;
  • how long records are kept.

This does not have to be complicated, but it does need consistency.

Leaving staff without training or authority

A policy on paper does not help if frontline staff do not know it exists or are not authorised to apply it. This is especially common in growing businesses where founders still handle escalations personally but customer-facing staff are expected to absorb complaints day to day.

Staff should know when they can offer a simple fix, when they need approval, and when a matter should go straight to management or legal review. Before you spend money on setup for a new system, make sure the people using it understand the process.

A complaints handling policy rarely stands alone. Problems arise when the policy says one thing, customer terms say another, and refund scripts say something else again.

Review the policy alongside:

Alignment matters. If documents conflict, staff are left guessing and customers receive mixed messages.

FAQs

Is a complaints handling policy legally required for every New Zealand business?

No. Not every business is expressly required by law to have a written complaints handling policy. But many businesses need one in practice because of customer volume, industry expectations, privacy risk, procurement requirements or contract terms.

Can a small business use a short complaints procedure instead of a detailed policy?

Yes, if it still covers the essentials. A short, clear process that staff actually follow is usually more useful than a long policy that sits unread. The document should still match your contracts, customer rights and privacy practices.

Should our complaints handling policy be public or internal only?

It depends on the business. Many businesses keep a full internal procedure and publish only the customer-facing parts, such as how to make a complaint and expected response times. If a contract requires disclosure, check exactly what must be shared.

Can a complaints handling policy limit refunds or liability?

Not by itself. A policy cannot override legal rights or make misleading statements about available remedies. If you want to manage liability or clarify remedies, that usually needs to be handled properly in your contracts and customer terms.

Legal review is sensible before you sign a contract that refers to complaint handling, when complaints often involve privacy or consumer issues, or when your current policy does not match how the business operates. It is also worth reviewing if complaints are becoming frequent, expensive or hard to close consistently.

Key Takeaways

  • A complaints handling policy helps New Zealand businesses deal with issues consistently, reduce escalation risk and support compliance with customer, privacy and contract obligations.
  • You are more likely to need one where complaints are frequent, personal information is involved, contracts require it, or multiple staff deal with customers.
  • Before you sign a contract, check whether complaint handling obligations are documented, time-bound, auditable or tied to breach and liability clauses.
  • Your policy should fit with the Consumer Guarantees Act, Fair Trading Act, Privacy Act and the promises your business makes in contracts and customer communications.
  • Common mistakes include copying a generic template, promising unrealistic outcomes, failing to keep records, and leaving staff unclear about escalation.
  • The most useful policy is one your team can actually follow when a complaint lands, not one that only looks good during procurement or due diligence.

If you want help with contract review, customer complaint procedures, privacy issues, or refund and remedy wording, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.

Need legal help?

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Keep reading

Related Articles

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.