Customer Service Academy / Module 06
The Secret Customer Customer Service Academy
Module 06 | Version 1.0 | 16 November 2026
Write a usable procedure for normal enquiries, missed service commitments and complaints. Give staff a clear sequence, an owner for outstanding work and a route to someone with the authority to decide. Keep communication, remedy decisions and verified completion distinct.
Who this module is for
Business owners, service managers and team leaders documenting day-to-day service delivery. Bring the journey from Module 02, charter commitments from Module 03 and standards from Module 05. Identify the business roles that can approve decisions and review disputed outcomes.
Learning outcomes
- Write a procedure with a trigger, sequence, decisions, records and end conditions.
- Distinguish an enquiry, complaint and service recovery action.
- Separate acknowledgement, useful response, resolution and closure.
- Define accepted handovers and escalation with authority.
- Prepare a complaint record and test exception cases before rollout.
Your finished output
Produce a service procedure, an escalation matrix, a complaint record template and a scenario test log. Adapt the ordinary service example to the business before use.
Scope
This is a general operating framework. Applicable rights, external complaint routes, mandatory time limits and reporting duties vary with the service and sector. Identify those requirements in the business procedure. Consumer guarantee rights cannot be removed by internal policy, and the ACCC does not resolve individual consumer guarantee disputes. [2]
The Harbour Home Repairs case and all timing arrangements are fictional. The module does not decide a customer’s legal entitlement or establish an accredited complaint-management system.
Design the procedure and decision rights
Start with the work staff must complete
A procedure turns a standard into actions. State its purpose, scope, starting event, required information, steps, decision authority, records and completion conditions. Identify the owner of the procedure and the person accountable for each open case.
| Situation | Working distinction | Operational response |
|---|---|---|
| Enquiry | A request for information or action. | Clarify the task and progress it with a clear next step. |
| Complaint | Dissatisfaction about the service requiring a response. | Record the issue, impact and requested outcome; investigate and respond. |
| Service recovery | Action after a failure or missed commitment. | Address the immediate problem and restore a workable next step. It may begin before a complaint. |
| Review request | A request to reconsider the handling or decision. | Refer through the defined review route with context and decision reasons. |
Set authority before frontline staff need it
Document which roles may correct information, arrange operational action, approve a discretionary gesture and decide a disputed remedy. Do not confuse an internal spending limit with the customer’s rights. Route a decision beyond staff authority to an authorised person without requiring the customer to restart.
Make handovers explicit
The sending owner retains responsibility until the receiving person or team accepts the case. Transfer the issue, relevant evidence, action taken, customer communication preferences and next update point. Record acceptance and tell the customer who will act next.
Write for actual use
Keep steps short and link to current reference information. A small business can assign several roles to one person, but should still provide a workable review route. business.gov.au recommends accessible complaint procedures, records of commitments and follow-up. [1]
Build the service and recovery workflow
| Stage | Action and decision | Required record |
|---|---|---|
| 1 Receive | Listen or read the request. Check immediate urgency and the appropriate service route. | Receipt time, channel, issue and initial owner. |
| 2 Clarify | Confirm the facts, customer impact and requested outcome. Ask only for relevant missing information. | Summary agreed or corrected by the customer where possible. |
| 3 Check | Review the job history and approved information. Identify whether the owner has authority to act. | Evidence checked, uncertainty and decision route. |
| 4 Act or refer | Complete an authorised action, or arrange an accepted handover to the decision owner. | Action, authority, receiving owner and acceptance. |
| 5 Update | Explain what has happened, what remains and the next update point. Keep the commitment even without a final answer. | Due time, actual contact and content. |
| 6 Verify and review | Check the promised action happened. Communicate the outcome, reasons and relevant review options. | Completion evidence, customer response and outstanding matters. |
Handle urgent exceptions through the right process
Route immediate safety, security, serious misconduct or other material risk to the business’s designated specialist or emergency process. The routine queue must not delay that action. Record the transfer and keep customer communication coordinated without promising an outcome outside the service team’s authority.
Handle missing information without losing ownership
Explain what is needed and why, provide a usable reply route and agree the next contact point. Follow the business’s applicable timing rules; do not assume every clock pauses when information is requested. Keep the original receipt and due points visible.
Preserve continuity during a system outage
Use the approved fallback record, protect access and reconcile it when the system returns. Record the customer commitment so the outage does not make the action disappear. Do not create an uncontrolled personal copy of sensitive case records.
Read a fictional recovery case
The missed update
A Harbour Home Repairs customer was promised a progress update by Friday at 3 pm local time. At 3.20 pm the job owner notices it was missed because the technical answer is still unavailable. The customer has not yet complained. Recovery begins with acknowledging the missed commitment and providing a useful next step.
The response
The job owner checks the record and contacts the customer through the agreed channel. They acknowledge that the update was late, explain that the technical check is still outstanding and propose an update by 11 am on Monday. The customer agrees. The owner records the original missed deadline, the new commitment and the responsible technical team.
Illustrative wording: I missed the update we agreed for 3 pm today. The technical check is still outstanding. I will contact you by 11 am on Monday with the result or a progress update. Would that update point work for you?
If the customer raises a complaint
The customer says the delay caused inconvenience and requests a refund. The owner records the request and impact. They do not refuse or approve a remedy merely because an internal policy has a spending limit. An authorised manager checks the relevant facts and obligations, then explains the decision and available review routes.
Record the outcome accurately
In this case, assume the Monday update is delivered at 10.30 am, but the repair remains open. The Monday update commitment is complete. The repair and any complaint remedy decision remain open until their own completion conditions are met. A timely new update does not erase Friday’s failure.
When no agreement is reached
If the customer cannot be reached, record the attempt and follow the approved alternative-contact route. Do not record acceptance of a proposed due point without evidence. An administrative closure rule must retain unresolved status, reason and a reopening route; it does not establish customer satisfaction.
Learn from the failure
Check why an unavailable technical answer prevented an interim update. A procedure may need to require a useful progress message even when the answer is pending. Test the change across similar cases before claiming the cause is widespread.
Write your service procedure
Procedure control
Procedure title and ID: [enter]. Version and effective date: [enter].
Owner and approver: [enter]. Services, channels and locations: [enter].
Trigger and required inputs: [enter]. End condition for each task: [enter].
Related charter, standard and current reference information: [enter].
Operational steps
| Step and trigger | Role and action | Decision or exception | Record and next point |
|---|---|---|---|
| [1 Receive] | [Enter] | [Urgency and route] | [Enter] |
| [2 Clarify and check] | [Enter] | [Missing facts or authority] | [Enter] |
| [3 Act or hand over] | [Enter] | [Acceptance and cover] | [Enter] |
| [4 Update and verify] | [Enter] | [Delay or failed contact] | [Enter] |
| [5 Close or review] | [Enter] | [Unresolved or disputed] | [Enter] |
Escalation and authority matrix
| Trigger | Decision owner | Frontline action | Acceptance and update |
|---|---|---|---|
| [Outside authority] | [Named role and cover] | [Record and refer] | [How accepted; who updates] |
| [Urgent material risk] | [Specialist route and cover] | [Follow applicable urgent process] | [Transfer evidence] |
| [Disputed decision] | [Review role] | [Provide context and route] | [Review timeframe and owner] |
Confirm applicable requirements, permitted decisions, external routes and timing rules before rollout. Record where the current approved details can be found.
Use a complete complaint record
Intake and investigation
Case ID and receipt time with timezone: [enter].
Service reference, channel and responsible owner: [enter].
Customer issue, impact and requested outcome: [enter separately].
Relevant evidence and missing information: [enter].
Communication preferences and support needed: [enter only relevant details].
Urgency, applicable requirements and specialist referral: [enter].
Decision and follow through
Decision owner, authority and reasons: [enter].
Action promised, action owner and due point: [enter].
Update commitments, actual contacts and failed attempts: [enter].
Handover acceptance and outstanding work: [enter].
Completion evidence for each action: [enter].
Customer response and unresolved disagreement: [enter].
Review route explained and case status: [enter].
Closure or administrative closure reason and reopening route: [enter].
Improvement issue, owner and check date: [enter].
Keep stages distinct
Acknowledgement confirms receipt. A useful response progresses the issue or explains the next step. Resolution concerns the issue and agreed or required action. Closure is the recorded case state under the procedure. The customer may remain dissatisfied after an action is complete, and a closed case is not automatically a successful resolution.
Restrict records to the information needed for handling and review, following the business’s approved access and retention arrangements. Do not put identifiable complaints into public learning examples or unrestricted team documents.
Test the procedure and assess the output
Scenario test log
| Test case | Expected behaviour | Evidence to retain |
|---|---|---|
| Owner unavailable | A cover role accepts the case and preserves the next update. | Accepted owner and due point. |
| Requested remedy outside authority | An authorised decision maker receives the facts without a premature refusal. | Referral, acceptance and reasoned decision. |
| Action completed but disputed | Outcome and review route are explained; disagreement remains visible. | Completion evidence and customer response. |
| No customer response | Attempts and unresolved work are recorded under the approved closure rule. | Reason, status and reopening route. |
Applied exercise
A case is marked resolved after an automated acknowledgement. The promised repair update has not been sent and no manager has accepted the requested remedy review. Identify the correction.
Check your reasoning: the acknowledgement establishes receipt only. Correct the case status, assign an owner to the update, arrange acceptance of the remedy review and contact the customer with a useful next step. Preserve the missed commitment. Do not backdate completion.
Assessment criteria
- The trigger, scope and separate end conditions are clear.
- Each open action has an owner, due point and evidence requirement.
- Decision authority and handover acceptance are explicit.
- Urgent, delayed, missing-information and disputed cases have workable routes.
- Test records show the workflow can be applied, with gaps assigned for correction.
Continue your learning
Use the procedure for the training and coaching work in Module 07. Module 08 will connect recurring issues to improvement reviews. The existing complaint-handling assessment guide explains how to observe delivery in a defined assessment. [3]
Sources and editorial basis
The workflow, templates and fictional case are original proposed Academy teaching material. Prepared with AI assistance. Content reviewed and approved by Peter Martin, Secret Customer Australia, on 16 November 2026. Sources support general complaint-handling practice and the limited consumer-rights context. They do not approve the procedure or prescribe its example deadlines. Accessed 16 November 2026.
[1] business.gov.au. Handle customer complaints. https://business.gov.au/people/customers/handle-customer-complaints
[2] ACCC. Consumer rights and guarantees. https://www.accc.gov.au/consumers/buying-products-and-services/consumer-rights-and-guarantees
[3] Secret Customer Australia. Complaint Handling and Service Recovery Assessment. https://www.secretcustomer.com.au/the-secret-customer-academy/complaint-handling-service-recovery-assessment/
Source links
- business.gov.au handle customer complaints
- ACCC consumer rights and guarantees
- Complaint handling and service recovery assessment
Continue your learning
View the full curriculum · Previous: Developing Customer Service Standards · Next: Customer Service Training, Coaching and Accountability
Download your editable module
Download Module 06 — Customer Service Procedures, Complaints and Recovery (Word document).
