Customer Service Academy / Module 02
The Secret Customer Customer Service Academy
Module 02 | Version 1.0 | 16 November 2026
Identify what a customer is trying to achieve, examine the journey they actually experience and choose a supported improvement. Produce a customer-needs brief, an evidence register and a journey map that managers can use to develop service commitments and standards.
Who this module is for
Business owners, managers and service leaders improving a defined service across one or more channels or locations. Bring the Module 01 direction brief, a description of the current process and available customer feedback or operational records.
Learning outcomes
- Distinguish a customer goal, need, expectation and proposed solution.
- Separate observed evidence, customer reports and assumptions.
- Map a current journey with its channel changes, handovers and unresolved steps.
- Identify where a service failure affects the customer’s task.
- Choose an improvement with an owner and a check that tests the proposed result.
Your finished output
Complete the needs brief, evidence register and current-state map. Select one improvement and write a test plan. Start with one customer task and route; map materially different routes separately before combining findings.
Scope
This lesson teaches service discovery and journey design. The existing cross-channel mystery shopping guide explains how to assess a defined journey. A journey map based only on a workshop is a hypothesis until checked against evidence. Digital NSW recommends grounding maps in user research and separating the current and intended future experience. [1]
Harbour Home Repairs and all records in the examples are fictional. This learning module does not establish customer research findings for any real business or industry.
Define the need before choosing a solution
| Term | Working meaning | Fictional repair example |
|---|---|---|
| Customer goal | The task the person wants to complete. | Decide whether to approve a repair and plan around its completion. |
| Need | What the person requires to progress that task. | Understand the options, cost information and next update point. |
| Expectation | What the person believes will happen. | Receive the Friday update promised by the service adviser. |
| Proposed solution | A possible change to the service. | Add an update reminder and a handover acceptance field. |
Write a useful need statement
Use: when [situation], the customer needs to [understand or do something] so that [task outcome]. Example: when repair timing is uncertain, the customer needs to know when the next update will arrive so they can decide whether to make an alternative arrangement.
Choose a manageable boundary
State the starting event, finishing event, customer group, service, channels and locations. For this example, the map starts when an existing customer asks for repair progress and includes any repeat contact after a missed update and ends when the next step is clarified or the unresolved gap is recorded. It does not cover the technical quality of the repair.
Include variation deliberately
Consider people who abandoned the task, needed help or used a different channel. Recruit for relevant circumstances rather than inventing demographic stereotypes. A person with limited digital access may need a telephone route, but do not assume their preference without asking.
Ask about a recent experience
- What were you trying to achieve at that point?
- What happened next, and what did you have to do?
- What information was missing or difficult to understand?
- What did the business say would happen?
- How did you know the task was complete?
Avoid leading questions such as would a new app solve this. Do not promise that an interview will fix an individual case; provide an appropriate service route for an unresolved issue.
Build an evidence register
Keep a traceable record of what supports each need or failure. Use coded references in the map and retain underlying records only within the business’s approved access and retention arrangements. Collect what is needed for the task and remove identifying details from shared teaching or workshop copies.
| Reference and type | Fictional evidence | What it can and cannot show |
|---|---|---|
| E01 Customer account | A participant describes calling twice after a promised Friday update did not arrive. | Supports that person’s reported uncertainty. Does not establish the rate of missed updates. |
| E02 Operational record | One reviewed job has no accepted new owner and a due update with no delivery evidence. | Shows a recording or delivery gap for that job. Does not by itself prove no conversation occurred. |
| E03 Staff account | An adviser says ownership can be unclear when jobs move locations. | Suggests a possible cause to test. Does not prove every handover fails. |
| A01 Assumption | A shared reminder may reduce missed updates. | Proposed intervention. Needs a trial and evidence of results. |
Make the research coverage visible
Record the research period, selection method, channels and locations covered, participant or record counts and gaps. A small convenience sample can expose a problem worth investigating without estimating its prevalence. Keep non-response and unavailable records visible.
Reconcile conflicting accounts
A customer may report no update while a record shows a sent message. Check the recipient, channel, delivery status and message content before deciding what happened. Keep the customer’s reported experience and the system event as separate evidence.
Do not invent feelings
Record a feeling when a participant reports it. Otherwise describe the observed barrier, such as an unanswered timing question. A coloured emotion line drawn by staff is not customer evidence unless clearly marked as an assumption.
Choose proportionate methods
Combine relevant interviews or feedback with process observation and operational records. Mystery shopping can add evidence about a defined interaction; it cannot reveal every real customer’s needs. Use the existing program-design guide when planning that assessment. [2]
Read a completed fictional journey map
Harbour Home Repairs transfers a repair enquiry from its service desk to another location. This small example draws only on the invented E01 to E03 records. It is a teaching map, not a frequency estimate.
| Stage and channel | Customer task and need | Evidence and barrier | Current responsibility |
|---|---|---|---|
| Ask for progress by phone | Understand current status and the next update point. | E01 reports a Friday update was promised. | Receiving adviser records the enquiry. |
| Job moves between locations | Keep the enquiry progressing without restarting it. | E03 suggests ownership can be unclear. Cause unconfirmed. | Sending adviser refers the job; acceptance is not visible. |
| Wait for agreed update | Receive usable information at the promised time. | E02 has no delivery evidence for the due update. | No accepted new owner is recorded in this example. |
| Contact service desk again | Obtain an answer and know who will act. | E01 reports two repeat calls. Effort and uncertainty remain. | Desk adviser must locate the job and assign follow-up. |
Describe the failure precisely
The map identifies a gap in continuity between referral and accepted ownership. It does not show that an employee deliberately ignored the customer or that a particular software product is required. Check the actual handover record and discuss the work with both locations.
Write the intended future experience separately
Proposed future state: the sending adviser remains responsible until the receiving owner accepts the handover in the job record. The next update point is retained, and the customer is told who will act. A reminder supports the due update. This is a proposal, not an observed improvement.
Keep the whole task visible
A prompt telephone answer would not complete this customer task if the promised update still failed. Show contact-level performance beside whether the task progressed. The cross-channel assessment guide uses the same distinction when testing continuity. [3]
Write your needs brief and journey map
Customer and task
Service and customer group: [enter].
Customer goal: [task to complete].
Need statement: when [situation], the customer needs to [do or understand] so that [outcome].
Boundary: [starting event] to [finishing event]. Channels and locations: [enter].
Important variations and excluded routes: [enter with reasons].
Evidence register
| Reference | Finding and evidence type | Source and coverage | Limit or next check |
|---|---|---|---|
| [E01] | [Observation or customer report] | [Coded record, date, sample] | [What is still unknown] |
| [E02] | [Observation or operational record] | [Coded record, date, sample] | [What is still unknown] |
| [A01] | [Assumption or possible cause] | [Why it is plausible] | [How to test it] |
Current journey
| Stage and channel | Customer task and need | Evidence and barrier | Owner and handover |
|---|---|---|---|
| [Stage 1] | [Enter] | [Reference and finding] | [Enter] |
| [Stage 2] | [Enter] | [Reference and finding] | [Enter] |
| [Stage 3] | [Enter] | [Reference and finding] | [Enter] |
Add rows for loops, abandoned tasks and alternative routes. Preserve their sequence. Record the customer’s own description of effort or feelings only when supported.
Choose and test one improvement
Prioritise by consequence and evidence
Describe the customer consequence, the evidence strength, the work needed and who can decide. Address urgent material harm through the appropriate business process before routine improvement prioritisation. For ordinary service issues, select a change that can be tested without redesigning every channel.
Fictional improvement brief
Problem: progress enquiries can lose a recorded owner during a location transfer. Proposed change: require an accepted handover containing the outstanding action and due update time. Owner: service manager. Trial: the three fictional locations over the same eight-week pilot used in Module 04.
Check the percentage of due updates delivered on time with the required content, using the Module 04 definition. Also review repeat contacts and whether customers understood the next step. A rise in the update KPI alone would not establish reduced customer effort or prove causation.
Your test plan
- Proposed change and supported need: [enter].
- Decision owner and delivery owner: [enter].
- Trial scope, start and end: [enter].
- Comparable baseline and missing evidence: [enter].
- Primary check and customer consequence check: [enter].
- Review point and decision to retain, revise or stop: [enter].
Applied exercise
A workshop labels customers angry at the handover stage. There are no customer interviews. One job lacks an accepted owner, and two customers report having to repeat their enquiry. What can the map state, and what must be checked?
Check your reasoning
State the missing owner on the reviewed job and the two reported repeat enquiries, with their coverage. Mark anger and the cause of the repetition as unverified. Ask customers about the experience and inspect the relevant sequence of records. Do not infer a business-wide failure rate from these three records.
Assess the map and continue
| Criterion | Evidence needed |
|---|---|
| Defined task | A customer group, goal, start, finish and route are stated. |
| Traceable need | The need follows from evidence or is explicitly an assumption. |
| Current state | The map records the actual sequence, including handovers and loops. |
| Honest coverage | Sources, selection, counts and missing routes are visible. |
| Practical action | An owner and a test connect the proposed change to a customer consequence. |
| Separation of states | Current observations and future proposals are distinguishable. |
Ask a colleague to trace one finding from the map to its evidence. Revise unsupported statements before using them to set commitments. This checklist is an applied review aid, not a validated research instrument.
Continue your learning
Use the need statement to check the charter in Module 03 and objectives in Module 04. Carry the priority journey into service standards in Module 05 and procedures in Module 06. Refer to the existing cross-channel guide when you are ready to assess delivery.
Sources and editorial basis
The needs brief, evidence register, worksheets and Harbour Home Repairs 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. The sources below support general methods, not the fictional findings or a claim of representative research. Accessed 16 November 2026.
[1] Digital NSW. Customer journey mapping. https://digital.nsw.gov.au/delivery/digital-service-toolkit/resources/user-research-methods/customer-journey-mapping
[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. Cross Channel Mystery Shopping. https://www.secretcustomer.com.au/the-secret-customer-academy/cross-channel-mystery-shopping/
Source links
- Digital NSW customer journey mapping
- Designing a mystery shopping program
- Cross-channel mystery shopping
Continue your learning
View the full curriculum · Previous: Customer Service Vision, Purpose and Values · Next: Writing a Customer Service Charter
Download your editable module
Download Module 02 — Understanding Customer Needs and Service Journeys (Word document).
