Voice-of-customer programmes

A voice-of-customer programme is a repeatable way to hear what customers experience, interpret the feedback and act on it. Start with one service task and a decision the team can make. Collect feedback at relevant points, keep its limits visible and route issues to someone who can act.

Establish the programme purpose

Treat listening as part of a planned, developed and sustained customer service programme, rather than a one-off collection exercise. Business Queensland describes customer service as managing expectations so customers receive what they want, when they want it, in a way that meets those expectations.

Business Queensland identifies possible business benefits of good customer service, including repeat visits, referrals, favourable word-of-mouth and online recommendations, and increased customer numbers or spending per transaction. Use these as reasons to take customer feedback seriously, not as guaranteed outcomes of collecting it.

Define the decision

Choose a task such as changing an account address. Name the customer group, where the task begins and the outcome the customer needs. Then identify what the organisation could change: an instruction, a handover, a processing step or how the result is communicated.

Identify a decision owner before collecting responses. Keep requests for individual help separate from suggestions about the service. A customer whose address change failed may need an answer about their account while also providing evidence of a wider problem.

Support listening through service culture

A feedback programme depends on people treating service as part of their work. Business Queensland recommends training staff, valuing service in the business and embedding it in communication with staff and customers.

Leaders can reinforce that culture by modelling the service behaviour they expect. Listening to customers, understanding their needs and thanking them for feedback are practical behaviours identified in Business Queensland’s guidance. Make clear to staff how customer input contributes to the service decisions within their remit.

Listen across the task

Possible sources include an always available feedback route, a short question after a defined interaction, support records and conversations with people who did not finish. Each shows something different. A survey offered only after completion misses some people who left early. Unsolicited comments can reveal a problem without establishing how common it is.

Ask about what the customer can assess at that point. Immediately after submitting a request, they may know whether the form made sense. They may not yet know whether the change took effect. Check that outcome later.

Choose feedback routes that fit your customers and tasks. Include a way to report difficulty before completing the step that caused it.

Keep the context with the feedback

Record the task, channel, service stage, date, question shown and who was invited to respond. Retain customer accounts only in a form the organisation is authorised to use. Separate a reported event from an explanation of its cause: “I received no confirmation” does not establish whether a message failed, a request failed or the customer expected a different confirmation.

When reviewing a theme, show how many responses it draws on, where they came from and who may be missing. A tally of comments is not a rate for all customers. Compare feedback with relevant service records where access is permitted, and investigate disagreements between them.

Turn feedback into a checked decision

Route individual requests for help and possible service issues to an appropriate follow-up process. See the supporting article for detailed issue ownership.

Record whether the team will act, investigate, monitor or leave the service unchanged, and why. After a change, check the customer outcome; closing an internal ticket does not prove the task works.

Tell people whether submitting feedback will lead to an individual reply. Where appropriate, explain what changed or why a requested change was not made. An anonymous suggestion route should not promise a personal response.

Make feedback monitoring routine

Include regular checks of the organisation’s communication channels as part of programme operations. Business Queensland recommends monitoring channels for complaints or other feedback and responding in a timely manner; this is a reminder to keep routes active, not a substitute for a separate process to resolve an individual complaint.

Bring relevant observations into service planning and review. Keep the evidence and its limits visible so a comment is not treated as proof of a widespread problem.

Handle personal information carefully

Free-text responses may contain names, account details or sensitive information even when the form did not ask for them. Collect only what is needed, restrict access to identifiable responses and set a retention process. For organisations covered by the Australian Privacy Principles, collection and security duties depend on the information and circumstances. Review the proposed handling process before launch.

For entities covered by the Australian Privacy Principles, the Office of the Australian Information Commissioner says an organisation may collect personal information only where it is reasonably necessary for its functions or activities. An agency may collect it where it is reasonably necessary for, or directly related to, its functions or activities. Collection must be by lawful and fair means.

Sensitive information has additional conditions: it may be collected only when the relevant necessity conditions are met and the individual consents, unless an exception applies. Personal information should be collected from the individual concerned unless doing so is unreasonable or impracticable, subject to applicable exceptions.

APP 11 requires an APP entity to take reasonable steps to protect personal information it holds from misuse, interference, loss and unauthorised access, modification or disclosure. When the information is no longer needed for a permitted purpose, reasonable steps must be taken to destroy or de-identify it, unless an exception applies, such as a legal retention requirement or its status as a Commonwealth record.