Why the suggestion box became the thing nobody uses
Every office I have worked in has had some version of the suggestion box. The physical kind, with a slot in the lid. The Google Form linked from a wiki page no one bookmarks. The shared inbox that two people half-monitor. They all share the same fate: a slow trickle of three or four submissions a quarter, mostly about coffee, and then a stretch of silence that everyone reads as proof the system works.
It is not that people have nothing to say. It is that submitting a suggestion to a box you cannot see into feels like dropping a coin down a well. There is no signal that anyone is listening, no path back if a question needs clarifying, and no evidence that the last suggestion went anywhere. Add to that the small but real fear that whoever opens the box might recognize the handwriting, the IP, or the writing style, and the rational response is to keep your suggestion to yourself.
The classic fix is to make the box more anonymous. The better fix is to make the box responsive. Anonymity is necessary, but it is not what people are actually asking for when they hesitate. They are asking for the conversation to feel like a conversation.
What changes when the box lives in Slack
Two things change when the suggestion box is a Slack DM with a bot, rather than a form on a separate site.
Response velocity. A Google Form sits in a spreadsheet that someone has to remember to open. A Slack DM lands in the same inbox where the team already lives. The HR lead or founder reading suggestions sees them in the same flow as everything else, and acknowledges them in minutes, not weeks. "We saw this. We are looking into it" lands within the same workday the suggestion was submitted, which is most of what the submitter wanted to know.
Two-way thread. If the suggestion is unclear, you can ask a clarifying question and the original sender can answer, still anonymously, still in their existing DM with the bot. The most useful suggestions almost always need a follow-up question. With a form, the thread dies the moment it gets interesting. With a Slack-based anonymous channel, the thread can keep going until both sides understand what the suggestion actually is.
One honest caveat: on Slack Enterprise Grid plans, Slack's audit log records bot interactions, including DMs to a feedback bot. HushAsk cannot suppress what Slack itself records. For Enterprise Grid teams, the architectural anonymity HushAsk provides still applies to anything HushAsk stores, but the Slack audit layer is a separate question worth raising with your IT lead. For teams on Free, Pro, or Business+, this caveat does not apply.
Three suggestion-box patterns that work
The shape of the box matters as much as the technology behind it. Three patterns hold up in practice.
1. The general inbox. One channel, always open, no prompts. Anyone can drop a suggestion any time. The HR lead or founder reads them as they come in and posts a public summary every two weeks: what came in, what was acted on, what was acknowledged but not acted on, and why. The summary is the most important part. Without it, the inbox feels like the well again. With it, the inbox feels like a line you can stand in.
2. The weekly prompt. Every Monday morning the bot DMs every team member a single open-ended question — "What is one thing that slowed you down last week?" — and collects the responses anonymously. The prompt does the work of inviting the response, which doubles or triples submission rates compared with an always-on inbox. The downside is that you have to be willing to read fifty open-text responses each week and resist the urge to convert them into a chart. The signal is in the wording, not the count.
3. The manager-routed lane. Suggestions are tagged at submission time as "general" or "about my manager / team lead." General suggestions go to the all-hands inbox. Manager-related ones route to a separate channel that the named manager does not have access to — typically the manager's own manager, plus HR. This is the highest-trust pattern and the one that surfaces the feedback that companies most need and most rarely hear. It also requires the most discipline: if a manager finds out their team has a separate lane and pushes to read it, the whole pattern collapses. The decision to set this up has to be matched by the discipline to keep the routing intact.
Most companies start with the general inbox, add the weekly prompt within a month or two, and only set up the manager-routed lane once they have a track record of acting on the easy stuff.
Setup walkthrough: 5 minutes, no admin work
The setup for HushAsk's anonymous Slack channel is short by design. Most of the friction in feedback tooling is in the rollout, not the install, so the install should not be the place that takes the longest.
Click Add HushAsk to Slack from hushask.com and approve the OAuth scopes. The bot lands in your workspace. From there:
One: in any channel you want to designate as the suggestion-box destination, type /invite @HushAsk. That channel becomes where anonymized submissions land. You can use a private channel like #hr-feedback or a public one like #suggestions depending on the pattern you are running.
Two: pick the people who can read the channel and tell the team where suggestions go. Transparency about where suggestions land is what makes people willing to send them. "Goes to the HR lead and the COO, no one else, and we summarize publicly every other Monday" is a real commitment that earns submissions.
Three: send a kickoff message in the team's main channel that links to the bot and explains the process. Most teams that get this right include three things in the kickoff: who reads the messages, what the response cadence is, and an example of the kind of feedback that is genuinely welcome. The third one matters more than the first two, because it gives people permission to send the kind of message they were going to keep to themselves.
Five minutes from install to first message. The harder work is what you do with the suggestions afterward — and that is the part the tool cannot do for you.
If you are choosing between a Google Form, a generic poll tool, or a Slack-native anonymous bot, the question is less about technology and more about which one your team will actually use after the first week. The case against Google Forms specifically is worth a read if you are leaning that way. Otherwise, the simplest path is to install the bot, run the general-inbox pattern for a month, and decide whether you want to add the weekly prompt next.