Customer Service Academy / Module 05
The Secret Customer Customer Service Academy
Module 05 | Version 1.0 | 16 November 2026
Turn customer needs and charter commitments into clear service behaviours. Write a standard that staff can apply, managers can support and reviewers can assess consistently. Keep the required result clear while allowing appropriate language and channel choices.
Who this module is for
Owners, managers and service leaders defining expectations for a team or network. Bring the customer-needs brief from Module 02, the charter from Module 03 and the KPI definitions from Module 04.
Learning outcomes
- Distinguish a standard, target, procedure and assessment question.
- Specify the trigger, action, owner, timing and evidence for a service behaviour.
- Adapt a standard across channels while retaining its customer purpose.
- Define exceptions, missing evidence and not-applicable cases.
- Pilot a standard with staff and calibrate its interpretation.
Your finished output
Produce a service standards register, one completed standard specification and a pilot review record. Begin with a small set of standards addressing significant moments in the chosen journey.
Scope
These are operational customer service standards, not claims of certification or conformity to a published technical standard. Business Queensland recommends realistic and clear expectations supported by staff skills and review. [1] Module 06 covers the steps and authority needed to deliver them.
All Harbour Home Repairs standards, targets and sample records are fictional teaching examples. No universal Australian response-time benchmark is proposed.
Write a standard that can be applied
| Document or measure | Question it answers | Fictional example |
|---|---|---|
| Charter commitment | What can the customer expect? | We provide the agreed progress update by its due time. |
| Service standard | What must happen in the interaction? | The job owner provides status, next action, responsible team and the next update point where relevant. |
| Procedure | How does staff deliver it? | Check the job, prepare the message, send it and record the evidence. |
| KPI and target | How will delivery be monitored? | Percentage of compliant due updates; illustrative pilot target at least 90%. |
| Assessment question | What will a reviewer check? | Did the update identify the next action? Record the relevant wording. |
Use a complete specification
Write: when [trigger], [responsible role] does [observable action] by [defined point], using [approved information], with [evidence]. Add the exception route and decision authority. Split unrelated behaviours so a failure can be located.
Replace vague wording
Be helpful is too open to interpretation. For a repair progress enquiry, a clearer requirement is: check the job reference, explain the recorded status and tell the customer the next action and update point. Accuracy depends on current information, so provide a route to verification when the record is unclear.
Avoid a rigid conversation script
Require the information and outcome needed for the task. Allow natural wording and appropriate communication support. A prescribed phrase should only be mandatory when the business has a specific reason to require it. Do not score smiles, eye contact or an exact greeting as universal evidence of understanding.
Test feasibility
Identify staffing, information, system access and authority needed. If a requirement depends on a tool staff cannot access, record the dependency and assign an owner before rollout. Keep a missed standard visible rather than changing the definition after the event.
Read a completed fictional standard
Standard HHR S01 Progress updates
| Field | Fictional specification |
|---|---|
| Customer need and link | Know what happens next. Supports the Module 03 progress-update commitment. |
| Trigger and scope | Each agreed repair progress update due at the three service locations. |
| Responsible role | Named job owner. Sending owner retains responsibility until a receiving owner accepts a handover. |
| Required action | Provide current status, next action, responsible team and the next update point where relevant. Explain uncertainty rather than guessing. |
| Timing | By the agreed due timestamp in the servicing location’s local time. Retain timezone and original due time. |
| Evidence | Unique update reference, due time, actual send or contact time and message or factual contact note. |
| Exception route | If technical information is unavailable, send a useful interim update by the due point. If the communication route fails, record the failure and seek an approved alternative. |
| Review and ownership | Service manager owns the standard. Review delivery weekly during the illustrative eight-week pilot. |
Keep the requirement and target distinct
This standard applies to each due update. The Module 04 pilot target of at least 90% is a proposed aggregate improvement target; it is not permission to miss one in ten commitments. Investigate missed or incomplete updates even if the overall target is reached.
Preserve the original commitment
A changed due point must be agreed and recorded before the original deadline, with a reason. Retain the original time and revision history. Review repeated extensions so that rescheduling cannot quietly conceal missed commitments.
Define a failed contact
An attempted call without a delivered update does not establish that the customer received the required information. Record the attempt, agreed channel and next action. Apply the published KPI definition consistently and report failed-contact exceptions separately.
Adapt standards across service channels
Keep a common customer purpose, then define evidence appropriate to the channel. A phone call does not have an email attachment, and an email does not require a spoken summary. Do not force every interaction into the same script.
| Purpose | Telephone or in person | Email or written message |
|---|---|---|
| Understand the request | Ask or confirm the relevant need and summarise material details. | Address the stated questions; seek relevant missing information. |
| Explain the next step | State the action, responsible team and timing; check understanding appropriately. | Make the action, responsible team and timing easy to find. |
| Record a commitment | Enter the agreed due point and required handover details. | Retain the sent message and link it to the job record. |
| Handle uncertainty | Explain what needs checking and agree the next update. | Distinguish an acknowledgement from a useful initial response or update. |
Specify eligibility and exceptions
An update-content criterion is not applicable when no progress update was due in the assessment window. If an update was due but its content cannot be evidenced, record missing evidence; do not call the case not applicable. Record the reason for any legitimate exclusion.
Build assessment questions from the standard
Use separate observations for timeliness, current status, next action, responsible team and next update point where relevant. Record facts and context. If the business uses scoring, define how components combine before collecting results. This lesson does not prescribe arbitrary weights.
Keep capability and compliance separate
An employee can know the standard yet be blocked by an unavailable job record. Investigate the event before choosing coaching or a system change. The program-design guide explains how to turn expectations into observable assessment questions. [2]
For channel-specific assessment criteria, use the existing email guide. It retains assessment intent; this module supplies the standard-writing framework. [3]
Write your standards register
Create one row for each distinct behaviour. Use a stable identifier so revisions can be tracked. Keep the detailed specification with the register rather than writing long procedures into every cell.
| ID and customer need | Trigger and required action | Owner and timing | Evidence and exception |
|---|---|---|---|
| [S01 and need] | [When and what] | [Role and due rule] | [Record and escalation] |
| [S02 and need] | [When and what] | [Role and due rule] | [Record and escalation] |
| [S03 and need] | [When and what] | [Role and due rule] | [Record and escalation] |
Detailed standard specification
Standard ID, version and effective date: [enter].
Customer need and related charter commitment: [enter].
Scope, trigger and responsible role: [enter].
Required behaviour and current reference information: [enter].
Timing rule, calendar and timezone: [enter where timing is relevant].
Evidence and record location: [enter].
Legitimate exclusions and not-applicable rule: [enter].
Missing evidence treatment and exception route: [enter].
Staff support and unresolved dependencies: [enter].
Approver, implementation owner and review trigger: [enter].
Pilot review record
Test route and dates: [enter]. People testing it: [enter].
Disagreement or delivery barrier: [enter].
Revision, owner and retest date: [enter].
Pilot and calibrate the standard
Run a practical trial
Ask staff to apply the draft to normal examples, an incomplete-information case and a handover. Check that the required information is available and that the work can be recorded. Invite feedback about wording and operational barriers before expanding the rollout.
Compare interpretation
Give two reviewers the same de-identified records and the same specification. Ask them to assess independently, then compare the evidence behind disagreements. Revise unclear definitions and retest. Agreement on a few sample cases is useful calibration; it does not validate the whole measurement system.
Applied exercise
Three records are reviewed against HHR S01. Record A was sent on time but has no next action. Record B is an unanswered call attempt with no delivered update. Record C concerns a job for which no update was due. How should they be treated?
Check your reasoning
A is timely but incomplete, so it does not meet the full standard or enter the compliant-update numerator. B shows an attempted contact, not evidence of a delivered useful update. Keep it visible as an exception under the agreed measurement rule. C is outside the due-update population, provided the absence of a due commitment is verified. Do not treat A or B as not applicable.
Control revisions
Record the version, reason, approver and effective date. Keep historical results tied to the definition used at the time. Explain material changes before comparing performance. Supply staff with the current standard and remove superseded working copies from routine use.
Your rollout decision
Decide whether the standard is ready, needs revision or is blocked by a dependency. Record the owner and due date for any gap. A published standard without operational support is not evidence that service delivery has changed.
Assess the standards and continue
| Criterion | Evidence needed |
|---|---|
| Relevant behaviour | The standard supports a defined customer need and commitment. |
| Clear specification | Trigger, role, action, timing and evidence are explicit. |
| Consistent interpretation | Two reviewers can explain the same decision on test records. |
| Practical support | Information, systems, authority and cover are available or gaps assigned. |
| Fair exceptions | Not applicable, missing evidence and failed delivery are distinguished. |
| Version control | An approver, version, effective date and review trigger are recorded. |
Revise any requirement that staff cannot understand or apply. This checklist supports an applied review; it is not certification of service quality.
Continue your learning
Use Module 06 to write the procedure and escalation rules needed to deliver these standards, Module 07 for training and coaching, and Module 08 for the wider improvement review.
Sources and editorial basis
The specification method, templates, exercises and HHR S01 example are original proposed Academy teaching material. Prepared with AI assistance. Content reviewed and approved by Peter Martin, Secret Customer Australia, on 16 November 2026. General sources do not establish the fictional targets, a universal service benchmark or legal compliance. Accessed 16 November 2026.
[1] Business Queensland. Improving your customer service. https://www.business.qld.gov.au/running-business/marketing-sales/customer-service/improving
[2] Secret Customer Australia. Designing a Mystery Shopping Program. https://www.secretcustomer.com.au/the-secret-customer-academy/designing-a-mystery-shopping-program/
[3] Secret Customer Australia. Email Customer Service Assessment. https://www.secretcustomer.com.au/the-secret-customer-academy/email-customer-service-assessment/
Source links
- Business Queensland improving your customer service
- Designing a mystery shopping program
- Email customer service assessment
Continue your learning
View the full curriculum · Previous: Setting Customer Service Goals, Objectives and KPIs · Next: Customer Service Procedures, Complaints and Recovery
Download your editable module
Download Module 05 — Developing Customer Service Standards (Word document).
