Why did my custom name for CultureBot revert, and how do I change it back? (for Slack users)

If you previously set up a custom name for your bot in Slack (e.g., "Kudos Bot" or "[Company Name] Bot") but noticed it recently reverted back to the default "CultureBot" name, don't worry! This is a known Slack behavior and is very easy to fix.

Why did this happen?

From time to time, we push updates to CultureBot to bring you exciting new features, such as new slash commands or capabilities. When these structural updates are released, Slack often requires workspaces to re-sync to the newest version of the app.

During this synchronization process, Slack occasionally pulls down our global "App Manifest" to make sure everything is up to date, which has the side effect of overwriting any local workspace customizations you may have made to the bot's display name or icon.

On CultureBot's end, we cannot control Slack from re-syncing your workspace to the newest version of the app but we do our best to provide support when this happens. Luckily, this doesn't happen often and does not affect any of your features or functionality; it just reverts the custom name back to "CultureBot" and is an easy fix.

How to change it back

A Slack Workspace Admin can immediately rename the bot back to your preferred custom name. To do this, you must be a Slack Admin with permissions to install and configure apps.

Step-by-step instructions:

  1. Navigate to the CultureBot page in the Slack App Directory (you can access at the link, or in your workspace's app directory by going to Settings & Administration -> Manage Apps).
  2. Click on the Configuration tab.
  3. Scroll down until you find the Bot User section.
  4. Click Edit. This will allow you to immediately rename the bot to the name of your choosing.
  5. Save your changes!

Please let us know if you have any questions or encounter any problems with this by contacting support@getculturebot.com, we'd be more than happy to help troubleshoot!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.