Team & Settings

Set Up Multiple Brands

2 min readUpdated 2026-09-16

If you support more than one product or company from a single team, brands keep the work separated inside one workspace. A brand can be attached to a chat widget, to a teammate, and to tickets, and each brand gets its own inbound email address.

Create a brand

  1. Go to Settings, then Brands under General.
  2. Select Create Brand.
  3. Enter a name and a slug (a short, URL-friendly identifier).
  4. Optionally add a description and upload a logo.
  5. Save the brand.

What you can change afterwards

Select a brand from the list to open its details. From there you can:

  1. Rename the brand.
  2. Upload or replace its logo.
  3. Set a Jira project key, which filters Jira issue searches for that brand's tickets.
  4. Delete the brand.
Note

Brand colors exist in the data but there is no screen for editing them, so every brand uses your workspace colors from Settings, then Company Info. Deleting a brand is permanent, and TixTalk blocks the deletion while a chat widget is still attached to it — reassign or delete the widget first.

Brand inbound email

Every brand is given a unique inbound email address the moment it is created. Mail sent to that address becomes a ticket under that brand.

  1. The address is in the form your-brand-slug-1a2b3c4d@tickets.tixtalk.com — your slug plus a short random suffix that keeps it unique.
  2. Forward your existing support address to it to start routing mail into TixTalk.
Important

The address is not displayed anywhere in the dashboard. Ask Drip support for your brand's inbound address, and ask them if you ever need it turned off or regenerated — those controls exist in the API but have no screen yet.

Assign teammates and widgets to a brand

  1. When inviting a teammate, pick a brand to tie them to, or leave it blank for access to every brand.
  2. When creating or customizing a chat widget, choose the brand it belongs to.
Note

A teammate's brand is recorded on their team membership but does not restrict what they can see, in the same way the permission checkboxes do not yet restrict access.

Was this article helpful?

Let us know so we can improve our docs