Skip to content
Interface language: English
Imperium / Signal

Customers helping customers: when a community answer becomes a company promise

Separate a user's advice from a company response on a customer forum: content status, moderation, escalation to support and whether a solution is current.

Article language: English

A woman holds the edge of a thick partition beside a relief map and a small niche with a teapot.
In this article

“It works for me” is an excellent beginning to an exchange of experience. As a complete answer from a company, it can be much less useful. On a customer forum, someone posts their own instructions, several people say thanks and a moderator marks the topic as solved. A month later another reader applies the advice to a different product version and asks why the company recommends something that does not fit their situation.

The boundary has shifted without a formal decision. One user's experience has been read as a general recommendation, and organising a discussion as approval of its content. The company needs to show clearly who is answering, what the advice applies to and where individual support begins. Rules placed far from the answer do not explain that to someone who arrives from a search engine directly in the middle of the thread.

Does a solved question mean an answer from the company?

Imagine a fictional forum for users of a catalogue tool. A customer describes a way of organising product variants that worked with her own data. Someone else looking for a way to update a catalogue sees the highlighted answer. They miss that the instructions concern an earlier version and manually prepared names. This is not yet evidence that the author was wrong; her description may have been correct in the stated context.

GitHub's documentation on moderating discussions describes marking a comment as an answer and undoing that mark. The feature makes an answer easier to find in a conversation. The button's name alone does not say whether a particular company treats the comment as instructions officially checked for its customers.

Discourse Solved lets the topic author and forum staff mark a reply as a solution. It can also show who applied the mark. This raises a practical design question for a community: can a reader tell whether the person who asked accepted the solution, or whether someone authorised by the company checked its content? Those are different messages.

Choose status names that correspond to real actions. “Helped the person who asked” can describe that person's own assessment. “Checked by the team for version ...” should require an appropriate check and a named version. “Official instructions” should lead to material maintained through an agreed process. Many decorative badges are unnecessary if none says what was actually done.

Make the author's role recognisable beyond the avatar as well. A username with a company logo may belong to an employee, an external moderator or a brand enthusiast. A label should explain the role in that community. The number of posts and profile popularity do not automatically grant authority to confirm the terms of a particular order.

How can advice retain its value without extending its meaning?

In the example, the author can add which version of the tool she used, what kind of data she had and what she managed to do. She does not need to document the entire product to share her experience. The company can make this easier with a short prompt when someone adds a question or answer. It should avoid a form so long that users stop helping one another.

The necessary context depends on the problem. To find an option, a version name and its place in the interface may be enough. For a data change, it may also matter what the instructions do not cover and when to ask support. Do not encourage people to post complete customer files, account data or access information publicly. An example can be limited to what is needed for the conversation.

The available abstract of a study of B2B customer participation in a problem-solving community, first published online in 2014, distinguishes asking questions and helping others from login frequency alone. For participants, asking questions and helping others were associated with lower use of traditional support, while more frequent logins were associated with higher use. This is not a promise that opening a forum will reduce support requests at every company. The number of visits alone does not describe the kind of help provided.

Do not directly transfer the rules of an internal community of practice. Its members may share access to knowledge and internal rules. A public forum brings together customers with different configurations and expectations. Shared experience helps someone frame a question, but does not give access to another user's individual order. The guide to internal communities of practice (in Polish) discusses how such a community works.

If advice works only in a narrow scope, keep that scope close to the answer itself. A note at the beginning may be more useful than a correction on the third page of a discussion. Someone arriving directly at a comment should see the important condition before acting. Do not make them read the forum's entire history to discover that the version has changed.

When should a moderator hand a case to support?

A moderator looks after the conversation and application of community rules. They may organise duplicates, ask for context and stop information that should not appear there from being published. They need not have the competence or authority to resolve a complaint, contractual terms or an individual exception. Explain these boundaries to people who perform several roles at once too.

In the catalogue tool, “where can I find export?” may stay on the forum. “Why don't I have the feature included in my order?” requires checking a particular account. The user should receive a route to support, information about what is needed and an explanation of what not to post publicly. “Please write privately” alone leaves too much uncertain: to whom and through which channel?

After the handoff, do not announce a public resolution merely because a ticket exists. You can say that further checking is taking place in support without revealing details. If a general issue is later confirmed, the team can publish information prepared for everyone else. It does not need to copy private correspondence to bring the public context to a close.

Aeneia conceptual photography

When a customer returns with the same question, check whether the forum actually pointed to a feasible next step. Sending someone from the forum to a form and from the form back to the forum creates a cycle of contacts without a solution. The person responsible for help should see the entire route, not just the number of closed threads. The article on customers returning with the same question (in Polish) considers why the earlier answer did not resolve the need.

Decide what happens to an unanswered question. The community is not automatically a team on duty. If the company promises a particular response time, it needs a way to meet it in the appropriate channel. Even without that promise, clearly indicate when to use official support rather than leaving a customer hoping someone will notice the post.

What happens to an old answer that still attracts readers?

An answer can become outdated after a change in version, feature or rules of use. The publication date helps, but does not by itself say whether the material still works. The forum owner should have a way to report outdated advice and assign it for review. Popularity should not prevent a correction.

If the way variants are identified has changed in our example, the team can add a visible notice beside the accepted answer and a link to current material. A valuable discussion need not be deleted if it explains the history of the problem. It is necessary, however, to prevent the old instructions being read as a current answer for the new version.

In archiving company knowledge, status and a route to newer material matter. A public thread needs a similar distinction, as well as respect for the author's contribution. If the company develops its own instructions from a conversation, it should not quietly alter someone else's words to make them look like the original, official answer. The article on archiving company knowledge (in Polish) explains how to distinguish older and current material.

Record a material editorial change and who made it. A reader needs to understand whether the author corrected an example, a moderator removed data or the product team added a new position. Those events mean different things. A single generic “edited” label may be too unclear at an important point.

Also check arrivals from search engines and links. The topic-list heading may show the correct status while the answer itself does not. A phone may hide a role description or date. Do not judge clarity only from the forum homepage, where all explanations appear together.

Before changing labels, prepare three short reading exercises. The first person arrives at a solution accepted by another customer. The second sees an employee's answer that only asks for more context. The third opens official instructions after a product update. Ask each person to identify the author, scope of application and next step. If all three appear to readers as equally approved company positions, change the names and where they appear.

Do not ask only whether labels are understandable. Show a concrete situation and ask whether the person would apply the advice to their own case and, if so, what they would check first. In our example, someone may recognise the same feature name but miss the product version. A better role icon alone will not fix the whole problem. The condition for applying the instructions must be clear beside them.

Also check whether users confuse a high number of thanks with the company having substantively approved an answer. There is no need to hide appreciation for a helpful person. It can be shown separately from the content's verification status, with a name describing the actual behaviour. “Helpful answer” and “checked by the team” should not have identical meanings in the design.

When reviewing help, retain cases that returned to support after a highlighted answer. The advice may have helped the original poster but not other configurations. Or the user may have needed confirmation about their own order. Those are different reasons for further contact, and neither automatically justifies taking credit away from the person who provided the solution. The company should improve context where it was actually missing.

How should a service describe this kind of help?

On the help page, show three things: what people can look for in the community, when to contact the team and how to recognise official material. The distinction should be clear without studying the company's internal structure. Do not present the forum as a substitute for every form of contact if it does not handle individual cases.

When first using the result of a service, a community can suggest an example of use. The company remains responsible for explaining its own scope and route to help. With a service under a partner's brand, it is also necessary to establish who may speak as a brand representative and who recognises a question requiring the provider. For the transition after delivery, see the article on first use of a service result (in Polish). Roles behind a partner brand are discussed in the guide to services under a partner’s brand (in Polish).

Aeneia Design can help design content architecture and answer labels in a digital customer journey. Implementing an extensive community platform and ongoing moderation require a separate scope. Real roles, example questions and decisions about their next handling are the starting point.

A forum should give people a place for useful exchange even when they do not know every answer. Clear labels protect that value: a customer can share a solution without accidentally becoming the author of a promise from the whole company. And the company can appreciate good advice without pretending that a green badge checked it under every possible condition.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear