Customer feedback through communities

A community can show where customers struggle, what they value and which questions need closer research. Treat discussions as leads and check them against other customer evidence before deciding.

Tell members what they can influence, how their input will be used and how you will report back.

Choose the level of influence

Before inviting input, decide how much influence members can have and state it plainly. The Victorian Government's summary of the IAP2 Public Participation Spectrum distinguishes informing people, consulting them, involving them throughout a process, collaborating on decisions and empowering the community to decide and deliver.

Informing gives the community no direct influence; consulting gives low to moderate influence; involving gives moderate influence; collaborating gives high influence; and empowering gives high influence and ownership.

IAP2 Public Participation Spectrum: Levels of Community Influence

Give feedback a clear route

A member may report a fault, ask for help, suggest a product change or describe a problem with the community itself. These need different owners.

Route an individual support issue to someone who can help the person affected. Send product requests to the product team for assessment. Give the community manager responsibility for concerns about the community experience.

Create a recognisable place for suggestions, but allow feedback to arise in ordinary discussions too. A moderator can acknowledge an observation and ask whether the member wants to discuss it further. Explain how posts may be summarised or shared internally.

An intake record can capture the problem, its circumstances, the source discussion, any follow-up needed and the responsible team. Keep the member's account distinct from their proposed solution.

Set out consistent procedures for the channels members use, such as comments, emails, live chats and feedback forms. Decide who responds, what response times the team can meet and how staff communications will be checked.

Queensland Government guidance suggests prominently stating contact options and expected timelines. A standard reply timeframe is 24–48 hours, but businesses should plan around their available resources.

For an APP entity, the OAIC says reasonable steps to notify a person about collection must be taken before or at the time personal information is collected, or as soon as practicable afterwards. The notice covers matters such as the entity's identity, why information is collected, usual disclosures and its privacy policy.

APP entities must also collect personal information by lawful and fair means. Organisations may collect it only where reasonably necessary for their functions or activities.

Steps to Handle Customer Feedback in a Community

Key Privacy and Engagement Guidelines for Australian Entities

Prepare the engagement before it begins

Reflect with the team on what you know about the community, what you may be assuming and what past engagement overlooked. Check existing organisational data, relevant engagement already happening and whether other organisations have trusted relationships with the community. Coordinating similar engagement can reduce repeated requests to the same people.

Preparing Engagement Before Launching Feedback Initiatives

Understand the problem behind the feedback

If structured questions would interrupt a peer discussion, offer a separate, voluntary research route. Explain who is asking, why, how responses will be used and what members can expect afterwards. Leave the ordinary thread available to people who came to exchange help.

Interpret the signal before prioritising it

Treat community feedback as a signal rather than a verdict. It can show that a problem exists and how it affects the people who raised it, but it may not show how common the problem is across all customers.

Separate the reported problem, evidence about its reach, consequences for affected customers and the team's constraints. A severe problem affecting a small group may deserve attention despite few posts. A popular suggestion may fail to solve the underlying task. Neither decision follows from votes alone.

Choose a way to gather evidence that fits the question rather than defaulting to a survey. The American Association for Public Opinion Research advises checking whether relevant data already exists and whether methods such as focus groups or content analysis would better answer the research question. A survey may need to be combined with other data, such as administrative records.

Pros and Cons of Using Surveys vs. Other Methods for Feedback Analysis

Close each loop at the right level

Acknowledge reports and tell members where they stand. Later, share what you heard, what you checked, what changed and what remains undecided. Explain a decision not to proceed where you can do so without exposing private information or confidential plans. Avoid delivery dates the responsible team has not approved.

Feedback about the community experience should also be acknowledged and closed at the right level, with any detailed change updates left to the relevant update process. If nothing changed, explain the constraint and how to raise a different proposal.

Review the process as well: are reports reaching the right owner, are members repeatedly asked the same questions, and do quieter customers have another way to be heard? Members should be able to see how their observations informed decisions, including decisions to wait.