Per-workspace Slack branding

What it is

When Ochre posts into a Slack channel — agent replies, CSAT surveys, interactive notifications — the message goes out under your workspace's logo and brand name, not a generic "Ochre" identity. To the customer in a Slack Connect channel, it looks like the message came from your company.

This matters because Slack Connect is a customer-facing surface. A message from "Acme Inc." reads as "the company I bought support from." A message from a generic "Ochre" bot reads as "some third-party tool I have to figure out." Same content, different perceived sender.

Where the brand comes from

Ochre uses two pieces of your workspace settings:

• Workspace name. Becomes the Slack username on outbound posts.
• Workspace logo. Becomes the icon_url on outbound posts.

Both are set in Settings → Workspace. If your workspace doesn't have a logo configured, posts fall back to the default Ochre app identity — there's no broken-image state.

Which posts wear the brand

• Agent replies sent from the inbox into a Slack Connect thread.
• CSAT survey blocks posted into a resolved Slack thread (see CSAT per channel).
• AI-drafted replies that auto-send.
• Status sync messages from linked integrations (e.g. "Linear: Done") if you've configured those to post in Slack.

Slash command responses (/ochre status, /ochre search) and admin-only ephemeral notifications stay under the Ochre app identity, since those are tools for your team rather than messages to the customer.

Setup

There's nothing to configure on the Slack side beyond the normal install. The chat:write.customize scope is requested as part of the Slack OAuth flow (Slack integration). Without that scope, posts fall back to the default Ochre identity.

To check it's working:

1. Set a logo on Settings → Workspace if you haven't.
2. Reply to a Slack Connect thread from the Ochre inbox.
3. Look at the post in Slack — username should be your workspace name, avatar should be your logo.

Multiple workspaces

If you operate multiple Ochre workspaces (for example, one per business unit), each one keeps its own logo and name. A post from Workspace A wears A's logo; a post from Workspace B wears B's. They don't bleed into each other.

Why we built it

We shipped per-workspace branding because the alternative — every customer-facing Slack message being labelled "Ochre" — was actively misleading. Customers in shared Slack channels expect to see the company they're talking to, not the support tool that company picked.

Permissions

The Slack chat:write.customize scope is requested at install time, alongside the standard chat:write and channels:read. See Integration permissions. No further configuration required.

What's next

• See Slack integration for the rest of the Slack feature set.
• Set your logo on Settings → Workspace if you haven't.
• See CSAT per channel for how Slack-channel CSAT surveys also wear your brand.