How to Set Up an Anonymous Suggestion Box for Your Community

An anonymous suggestion box gives community members a way to propose improvements without putting their name beside the suggestion. To make it useful, define what you are asking about, provide a simple submission link, assign someone to review responses and tell members how decisions will be communicated.

The most important design choice is not the colour of the box. It is what happens after someone sends an idea. A collection channel without a review routine can create an expectation of being heard that the organiser never fulfils.

Give the box a specific purpose

Start with a decision area you can influence: community events, onboarding, learning resources or communication. Do not ask for suggestions about a policy you have no authority to change without explaining that limitation.

For example, “Help us make monthly meetups easier to attend” is more useful than “Tell us anything”. The focused version can lead to changes in timing, format and preparation. The broad version may attract support requests, complaints and unrelated personal messages that need different handling.

Make the intended audience clear. This guide concerns adult creator and community groups, not regulated whistleblowing, safeguarding or emergency reporting. Those processes need appropriate specialist arrangements.

Choose a simple collection format

Use a single dedicated question when you need one suggestion per answer. Use a short feedback form when a little context will help you decide. A general inbox is suitable for ongoing open-ended messages, but it gives you less structure.

In UnsaidBox, a form can combine text, single-choice and rating questions. Start with the community suggestions template or a blank form. Keep the first version short; a longer form is not automatically a better listening process.

A practical suggestion form

1. What would you like us to improve? A short text answer naming one issue.
2. What would be different if we solved it? An optional text answer describing the benefit.
3. What change would you suggest? Optional, because a person can notice a problem without knowing the solution.

If you genuinely need a category, add a single-choice question with plain labels such as events, resources, communication and something else. Do not ask for role, location and attendance history unless they are needed; combinations of details can make people recognisable in a small group.

Keep complaints about individuals out of a public suggestion process. Provide a separate, suitable route for concerns that need an identified conversation, evidence or confidential handling.

Explain privacy and publication separately

Use this box to suggest improvements to [community activity]. No name or account is needed to respond. Please leave out names and identifying details. We will review submissions privately every [cadence] and share decisions about themes, not individual messages. This is not an urgent support channel.

Use private-only collection if that is your promise. If you intend to quote messages, request appropriate sharing permission and still review for identifying details. “Anonymous” does not make every story safe to publish. See UnsaidBox’s safety explanation before writing your own assurance.

Test before announcing

Open the link in a signed-out browser. Check that the introduction is clear, required questions are justified and submitting does not require an owner account. Send a labelled test suggestion and verify it appears in the correct results page.

For forms, check the question structure and sharing setting before publication because these lock once published. If your first trial reveals a wording problem, create a corrected version rather than mixing answers to different questions into the same results.

Use a fair review process

Review suggestions against three practical questions: does this address a real obstacle, is it within the community’s purpose, and can we reasonably do something about it? These are editorial decision aids, not an automated scoring system.

Separate the need from the suggested fix. “Run every event twice” may reveal that the current time excludes some members. A recording, rotating schedule or occasional alternative session might address that need with less work.

Do not treat repeated anonymous submissions as verified votes from different people. Use them as a signal to investigate. Similarly, an idea mentioned once may deserve attention if it reveals a serious access barrier.

Close the loop with three clear outcomes

Give each theme a decision: doing now, investigating, or not doing with a reason. You can keep this in private notes and publish a short summary; the product does not need to expose every submitted idea.

We heard that newcomers struggle to find the introductory resources. We are adding a single getting-started page this week. We are also reviewing the meetup time. We will not open a second chat group for now because it would split support across two places.

That update demonstrates consideration without claiming every request will be accepted. Avoid identifying details or exact quotes when you promised private-only feedback.

A worked example: improving attendance without guessing identities

Imagine an adult learning community whose monthly online meetup attracts fewer participants than expected. The host opens a suggestion form about attendance barriers, not a complaint box about particular members. In this hypothetical collection, responses mention short notice, an inconvenient time and uncertainty about whether beginners can attend. Those are three different problems, even though each might initially be summarised as “people are too busy”.

The host can publish dates earlier, explain the intended level and trial one alternative time. They do not need to ask respondents for names, employers or precise locations. If timezone information is necessary for choosing a meeting time, explain the purpose and consider broad options rather than combining several identifying details. Keep any individual request for accommodation in a separate appropriate support process.

The follow-up should name the experiment: “For the next two sessions we will publish the agenda a week ahead and include a beginner-friendly opening. We are also trying a different time.” At the end of that trial, ask whether those changes removed the original barriers. Do not claim the experiment succeeded simply because people liked the announcement.

Prioritise fairly when several ideas compete

Make a small decision note for each theme with four headings: obstacle, people or activity affected, feasible response and review date. You do not have to create a complex scoring model. The point is to avoid choosing only the easiest idea or the loudest wording. A suggestion that would remove an access barrier may matter even when it appears only once.

Use effort and likely benefit as discussion aids, not invented scientific measurements. “Create a clearer getting-started page” might be a small, reversible improvement. “Run every event twice” might require more staffing than you can provide. Acknowledge the underlying need even when you cannot accept the requested solution. Explain that you are testing an alternative instead of dismissing the suggestion as unrealistic.

A decision record you can copy

Theme: newcomers cannot find the first resource. Evidence: descriptions in the responses received, not verified votes. Decision: create one starting page and link it in the welcome message. Responsible person: [owner]. Review: [date]. What we will check: whether the next group can find the starting point without asking for directions.

Keep identifying excerpts out of that record when they are unnecessary. A useful administrative note should explain a decision without becoming another uncontrolled copy of private feedback.

Set a review rhythm that survives busy weeks

Separate reading from responding. A short first pass can flag anything that needs careful handling; a later planning session can decide which ordinary suggestions are actionable. Do not leave the collection open indefinitely while announcing an immediate response time you cannot meet. If you pause, explain the pause and give a realistic update rather than silently abandoning the invitation.

For a small community, a monthly themes update may be enough. For a short event series, review between sessions so feedback can influence the next one. Choose the interval around the decisions you make. The suggested rhythm is a manual operating practice; UnsaidBox does not automatically assign tasks to your team or schedule community announcements.

Use the product tools without changing the original promise

UnsaidBox's templates help you begin with a short form, while separate collections keep onboarding feedback apart from event suggestions. Pro offers more active forms and a larger response allowance for owners managing several programmes. Check the dashboard for current availability and limits before opening a new round; a bigger plan still needs a manageable review process.

If a collection explicitly permits sharing, eligible responses can be exported through Pro CSV tools for your own careful organisation. Private-only feedback remains excluded. Public sharing is also selective: an eligible message can become a share card or approved public content, but the suggestion box is not automatically an open voting board. For most operational suggestions, a clear thematic update is better than displaying everyone's raw words.

Know when a suggestion box is the wrong channel

A request such as “I cannot access my paid course” needs account-specific support. A serious complaint about an identifiable person needs an appropriate process, not a public popularity contest. Put those alternatives in the introduction so contributors do not have to discover the limitation after submitting. Avoid asking them to identify themselves inside an anonymous response merely to make follow-up possible.

Finally, distinguish a suggestion from a commitment. You are inviting input, not promising that every idea will be implemented. The meaningful promise is that you will consider relevant feedback using consistent criteria and communicate decisions at a useful level of detail. That is a stronger foundation for trust than approving everything and delivering very little.

Keep the box healthy over time

Review the invitation when the community changes. Remove outdated deadlines, pause collection when you cannot review it, and keep the alternative support route visible. If submissions become repetitive, publish the current decision before asking for more ideas.

A small, well-maintained suggestion box can be more useful than a large unmoderated public board. Start with one decision area, three questions and a date for your first update. Our feedback form setup guide covers the collection steps in more detail.