Abot will never post a message by itself. You can use the following commands:
/abot direct - open direct feedback dialog
/abot channel - open channel feedback dialog
Alternatively you can send anonymous messages directly from the command line:
/abot #general Last meeting was too long. Maybe we could start timeboxing all the presentations? - anonymous channel message. Anyone from target channel can reply to an author without knowing who sent it or discuss anonymously, directly in the thread.
/abot @tom Your last presentation was really good but... - anonymous direct message (disabled by default). Target user can reply without knowing who sent it.
/abot intro #general - send an anonymous message explaining how to use Abot to a target channel or user. You can send it to yourself to see how it looks beforehand by typing /abot intro @me
/abot help - display help
To submit an anonymous poll to Slack channel you just need to type
Other team members will be able to vote for it, and leave anonymous comments unless this option is disabled by team admins.
If you are on a Free or Standard Slack plan your messages are guaranteed to be anonymous. Teams with Corporate Export enabled (optional Slack Plus Plan feature) would be able to determine the sender of the message from export logs. Messages sent before activating Compliance Exports are not included into it, so everything you send before remains anonymous.
Without Corporate Export features even Slack admins and workspace owners cannot track the message and poll authors. Messages and survey questions content is not stored in the database and filtered out from the application logs so it cannot be accessed and used to determine the identity of the sender.
We understand that anonymous communication is a sensitive matter for most teams. Slack team admins can customize Abot settings (e.g. enable direct messages, pseudonyms, set whitelisted channels or disable replies or thread and survey comments) by going to the settings page. Additionally, Abot Enterprise customers can limit bot usage or receiving direct anonymous messages to a predefined group of users.
The app requests the minimal permission scope needed for it to function correctly.
When adding the app to your team, you will see the following permissions confirmation screen:
Those permissions are necessary for the Abot bot user to perform actions like reading the names of channels it is a member of and sending anonymous messages and polls initiated by users.
Can the app read my team's public messages?
Reading your team's messages by the app is not possible because it does not use the conversations.history permission scope required to do that.
Can the app access email addresses of my team members?
App does not use the users:read.email permission scope so it cannot read email addresses from the Slack API.
Please reach out to support email if you have more questions related to the app's permissions and security.
You can reply anonymously only if the author of the feedback message does not know who you are. If someone sends you a direct feedback you cannot reply anonymously because he already knows your identity. You also cannot reply anonymously if you replied as you to one of the previous messages to this user.
Direct replies can optionally be disabled by your team admins in a settings panel.
Whenever someone sends an anonymous channel message you can either send a direct reply to an author or continue the anonymous discussion in a thread. Every anonymous thread comment author can receive direct anonymous and signed replies from people in the channel.
You can post to private channels as long as bot user is a member of this channel. Just type /invite @anonymous-bot to add him. You cannot send messages to user groups unless you convert them into private channels first.
You just need to remove the Abot app from your Slack, and subscription will automatically cancel within a couple of hours.
All the purchases are fully refundable within the first two weeks, no questions asked.
Sensitive information like messages content and user nicknames are filtered out from the logs and not stored in the database. Slack API access tokens with minimal scope permissions are stored in an encrypted form. Messages metadata is regularly removed. See terms for more info.