> For the complete documentation index, see [llms.txt](https://docs.clearfeed.ai/clearfeed-help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearfeed.ai/clearfeed-help-center/account-setup/whitelabel-clearfeed.md).

# Whitelabel ClearFeed

You can white-label ClearFeed to enhance your brand visibility on Slack. This feature allows you to replace the ClearFeed app's name and logo with your own, ensuring a consistent brand experience for customers and employees.

{% hint style="info" %}
If Child Accounts share the same Slack workspace with your Primary Account, then the white-label configuration of the Parent Account will be inherited.
{% endhint %}

## **How to White-label ClearFeed?**

1. From the left-nav bar, go to Settings -> [Additional Settings](https://web.clearfeed.app/settings/additional-settings)
2. Under the `White-label ClearFeed` section, you will see an option to `Edit`.
3. Enter a new `Display Name`.
4. Under the `Profile Photo` section, enter the exact URL of the image.
5. Click on **Save**, and the selected image will appear in the display window.

### Image Guidelines

* Support image extensions: .png, .jpeg, .jpg.
* To upload the image, first host it publicly.
  * **Free option:** Use [Postimages.org](https://postimages.org/) — a simple, free service for hosting images publicly. Just upload your image and copy the direct URL to use here.
  * **Alternative:** Use an S3 bucket or any public image hosting service.
  * Google Drive URLs for images are not supported.
  * If images are hosted on a public site, ensure you verify their expiration dates as the URLs may become invalid afterwards.
* Ensure the image URL ends with a proper image file extension. (e.g. <https://www.example.com/image.png>).

### Examples

Once you complete the above process to white-label the ClearFeed app, the updated name and logo will be visible in the below-mentioned scenarios:

1. Messages sent by ClearFeed workflows
2. ClearFeed's GPT-Powered automated answers shared on Slack
3. Ticket details shared on the request channel thread
4. Agent replies shown on customer-facing request surfaces, if reply anonymization is enabled for your account
5. Other ephemeral messages shared by ClearFeed when a user files a ticket or is auto-assigned a request

## Anonymizing agent replies with your white-labeled bot

ClearFeed can also use your white-labeled bot identity for agent replies that are sent to requesters. When this account-level setting is enabled, requesters see the reply as coming from your configured white-labeled display name and profile photo instead of the individual responder's name and avatar.

This applies to requester-facing replies sent from agent workflows such as the Triage Channel, WebApp, quick replies, observer replies, API replies, and public comments synced back from external integrations. Supported requester-facing surfaces include request channels such as Slack, MS Teams, and Discord, as well as Email, Web Chat, and Portal conversations.

Your internal team still sees the actual responder in agent-facing surfaces such as the Triage Channel and WebApp, so ownership and collaboration remain clear internally.

{% hint style="info" %}
This setting is not self-serve. Contact the ClearFeed support team via your Slack Connect channel or <support@clearfeed.ai> to enable anonymized agent replies for your account. The setting uses the same white-labeled display name and profile photo configured above and applies at the account level.
{% endhint %}

## **White-labeling for multiple accounts**

* If you have created child accounts that share the same Slack workspace, the white-labeling settings will be available in the parent account itself and the child accounts will inherit these settings.
* If the child accounts share a different Slack workspace, then each of these accounts can have a separate white-labeling configuration which can be enabled by reaching out to the ClearFeed team via Slack or on <_support@clearfeed.ai>.\_

## **Renaming the ClearFeed Bot**

While white-labeling allows users to see a different bot name and logo when ClearFeed posts messages as a bot, if they want to tag the bot - they still need to tag `@ClearFeed`. Slack administrators can rename the ClearFeed bot in their workspace so users can tag a different bot name instead. This is a good complement to white-labeling - allowing personalization for commands where bot tagging is required.

**Note:** Renaming the ClearFeed bot is a Slack workspace-level operation. If you have multiple ClearFeed accounts attached to the same Slack workspace, the renamed bot will apply to all of them.

### How to rename the ClearFeed Bot

1. Visit the Slack admin page: <https://slack.com/signin?redir=%2Fadmin#/signin>
2. Open your workspace from this page (if multiple workspaces are shown)
3. From the Left Nav - open `Integrations` and then click on `Manage Integrations`
4. This takes you to the "Installed Apps" page where you can see all the Apps installed in your Slack workspace.
5. Find the `ClearFeed` app - and click on the `...` next to it and click on the `View in Slack Marketplace Link`

<figure><img src="/files/RIyOmEdyg4Q089yppuoq" alt="" width="563"><figcaption><p>Click on "..." next to ClearFeed and select "View in Slack Marketplace Link"</p></figcaption></figure>

6. This would take you to a link that looks like `https://<your_workspace_name>.slack.com/marketplace/A02RHUFQ2UR-clearfeed`
7. Find the "Bot User" section, click the Edit button and enter a new name for the Bot.

<figure><img src="/files/4FdXvr36SiDrUeQIXRgt" alt="" width="563"><figcaption><p>Edit the Bot User name in the "Bot User" section</p></figcaption></figure>

After this step - users can tag or use the new bot name - instead of `@ClearFeed` - where bot tagging is required (for example to create tickets or invoke AI Agents using Bot Tagging or when inviting the bot to channels using Slack commands (`/invite`)). The new bot name is also visible in the list of integrations in a request channel (i.e. on customer channels - customers see the new bot name as being the app installed in the channel).

{% hint style="warning" %}
**Important:** The ClearFeed bot image cannot be updated in this manner - only the name can be edited. To customize both the bot name and logo, use the white-labeling feature described above.
{% endhint %}

## Visibility

ClearFeed's icon will continue to appear in a few places even after white-labeling. These scenarios include:

* **Collapsed message threads in Slack:** Whenever you are viewing a collapsed message thread in Slack, messages synced from external ticketing systems or other channels (via ClearFeed) will still display the ClearFeed icon, as shown below:\\

  <figure><img src="/files/tYhxPmERFOA1MUzxOVlB" alt="" width="563"><figcaption></figcaption></figure>
* **Sender profile on synced messages:** For example, in a triage channel, if you hover over the profile of someone whose reply was synced from the request channel, the ClearFeed app icon will appear instead of your white-labeled icon.\\

  <figure><img src="/files/FzxvEAmrDjpr0ThFFyDS" alt="" width="381"><figcaption></figcaption></figure>
* **Adding ClearFeed to a channel:** Using `/invite @clearfeed` will always show the ClearFeed app icon rather than the white-labeled one.
* **Messages posted with a user's Slack identity:** If an agent connects Slack OAuth and chooses to post as themselves, Slack posts the reply using that user's identity. This overrides white-labeled reply anonymization for that Slack reply.
* **Messages with attachments:** Due to Slack API limitations, ClearFeed cannot impersonate users when posting messages with attachments. This affects workflows involving attachments, such as replying with attachments or posting announcements with attachments. In these cases, attachment handling can differ from the text reply and may show the ClearFeed bot or the posting user depending on the reply path.

To display your custom icon across all relevant surfaces, you can use a Custom App setup. Enabling it requires backend configuration by the ClearFeed team along with a few steps on your end. To get started, reach out to our support team via your Slack Connect channel or email <support@clearfeed.ai>

White-labeling for the Microsoft Teams app is also supported through a Custom App setup. If you'd like to enable this, please contact our support team through Slack Connect or at <support@clearfeed.ai>

{% hint style="danger" %}

### Custom App Setup Limitations

When you move from the standard ClearFeed app to a Custom App setup, Slack and MS Teams treats the new custom app as a completely separate application. As a result:

* The new custom app **cannot edit or delete** messages that were originally sent by the old ClearFeed app (including triage messages and messages synced between request and triage channels).
* Only messages sent by the new custom app (after it is installed) or by human users themselves can be edited or deleted going forward.

This behavior is enforced by Slack & MS Teams and applies to all apps: one app cannot manage messages created by a different app.
{% endhint %}
