If you're evaluating anonymous feedback tools for Slack, you've probably come across Abot. It's the most established option in the category — used by over 1,000 teams, well-reviewed, and straightforward to set up.
The question worth asking before you choose isn't which tool has more features. It's what "anonymous" actually means in each one — and whether that holds up when it matters most.
Why the technical implementation matters more than the marketing claim
Every anonymous feedback tool promises anonymity. The question is what backs the promise.
For low-stakes feedback — team suggestions, poll votes, "which office snack should we order" — the distinction doesn't matter much. For anything sensitive — a concern about a manager, a pay disparity, a compliance issue — the implementation is the thing.
Two tools can both describe themselves as "anonymous" and have very different answers to the question: could someone find out who sent this message, if they really wanted to?
Abot
Abot is a general-purpose anonymous communication tool for Slack. It handles anonymous channel messages, direct messages, polls, emoji reactions, and threaded discussion — all anonymously. It's highly configurable: admins can restrict which channels allow anonymous posting, limit it to specific user groups, and moderate messages.
It's a good tool for teams that want a broad, flexible anonymous communication layer. The HR-channel use case (routing sensitive feedback to a private channel) is explicitly supported, and it works well for that.
On the technical side, Abot's approach is transparent. Their FAQ states directly: "Just like in the case of all the other 'anonymous' apps on Slack, Abot's anonymity guarantees are constrained by the Slack logging system. Content of the messages is never stored on Abot servers, and the metadata is regularly removed."
Their privacy policy confirms that what is stored is the user's Slack identifier — the original ID, not a hash.
Here's where it gets specific. Abot's FAQ goes on: "If you're on Slack Free or Pro plan, no one from your team (including admins) can track who sent which message. However, if your team is using Business+ plan or Enterprise Grid, then admins could determine the sender from the optional private messages export logs."
This is Abot being honest — and they deserve credit for that disclosure. But the implication is real: if your organization is on Slack Business+ or Enterprise Grid, anonymity in Abot depends on whether your Slack admin chooses to pull the export. It's a policy protection, not a technical one.
Abot is the right choice if: You want a flexible, feature-rich anonymous communication tool, your team is on Slack Free or Pro, and your use case goes beyond HR routing — polls, anonymous reactions, threaded discussion, moderation controls.
HonestBot and OpenSay
HonestBot takes the opposite approach to Abot: extreme minimalism. The website is minimal, the feature set is narrow — anonymous messages through the bot, with optional 1:1 anonymous dialogue. They've claimed in public forums that they don't store any message data on servers at all, making identification technically impossible even if hacked. There's no published privacy documentation to verify this in detail, but the positioning is consistent. It's the right tool for teams that want simplicity above everything else.
OpenSay leans toward compliance and moderation. It adds AI-powered sentiment filtering, message flagging, karma systems, and whistleblowing workflow support. It's more feature-heavy than the others and explicitly positions around psychological safety frameworks and regulatory compliance. No detailed technical anonymity documentation is publicly available.
HushAsk
HushAsk takes a different architectural approach. When a message is sent, the sender's Slack user ID is immediately passed through SHA-256 — a one-way cryptographic hash — combined with a private salt unique to the deployment. The result is a 64-character string. The original ID is discarded and never written to disk.
This means HushAsk's database doesn't contain the sender's Slack identifier. Not stored, then removed later — never stored. The distinction matters because there's no point at which an admin, the vendor, or a Slack export could recover it.
HushAsk's Slack caveat is narrower than Abot's: on Enterprise Grid plans (not Business+), Slack's audit log API records bot interactions independently of what HushAsk stores. This is disclosed in HushAsk's privacy documentation. For teams on Free, Pro, or Business+, it doesn't apply. On Business+ plans, a Slack admin can request a DM export — but since HushAsk never stores the original Slack user ID, there's no data on HushAsk's side that connects a DM to a specific routed message. The hash exists; the identity doesn't.
HushAsk is more focused than Abot. It doesn't do polls, anonymous emoji reactions, or arbitrary channel messaging. It does two things: route sensitive questions to HR anonymously, and route general questions to a public channel where they can be answered and archived to Notion. That's the design.
HushAsk is the right choice if: Your primary use case is anonymous HR routing and knowledge capture, you want cryptographic identity protection rather than policy-based anonymity, and your team is on a standard Slack plan (or you're on Enterprise Grid and the audit log caveat is acceptable).
The honest summary
| Abot | HonestBot | OpenSay | HushAsk | |
|---|---|---|---|---|
| Identity stored | Slack ID (original) | Claims none | Not documented | 64-char hash only |
| Business+ exposure risk | Yes (Slack export) | Unclear | Unclear | No |
| Enterprise Grid risk | Yes (Slack export) | Unclear | Unclear | Slack audit log only |
| HR routing | ✓ (configurable) | Limited | ✓ | ✓ (built-in) |
| Polls / reactions | ✓ | ✗ | ✓ | ✗ |
| Notion integration | ✗ | ✗ | ✗ | ✓ |
| Cryptographic hashing | ✗ | Not documented | Not documented | ✓ SHA-256 + salt |
The right tool depends on what you're trying to solve. If you want broad anonymous communication with good configurability and you're on Slack Free or Pro, Abot is solid and well-established. If you want the strongest technical anonymity guarantee for HR-specific feedback — and you want answered questions to build a searchable knowledge base — HushAsk is built for that.