When you connect a channel to Unthread, we’ll automatically track new conversations as tickets in your Unthread Inbox and dashboard.

Ticket tracking happens behind the scenes, meaning customers will not see the Unthread app when a new ticket is created.

Tickets will automatically be tracked as long as:

  • The Unthread app is connected to the channel (it should appear in your “Customers” list in the dashboard)
  • A user who is not a part of your Slack workspace submits a message in the channel
  • Automated tracking is not turned off in your settings
  • The message isn’t a pleasantry like “Thanks” or “Hello”

Customers vs. Agents

In every channel, you will have Customers (people who create tickets when they post) and Agents (people who can respond to tickets).

For shared Slack Connect channels, anyone who is outside of your email domain will automatically be marked as a customer, and anyone in your Slack workspace will be an agent.

For internal support channels, anyone who is an “admin” of that channel profile will be an agent, and anyone else will be an internal customer.

You can override these settings to change someone to an agent or a customer by going to the “Members” tab, and editing their role, as seen in the gif below:

Handling Threads vs. Top-Level Messages

We know that some customers love threads and some despite them! Fortunately, Unthread is able to group conversations together regardless of whether messages come in threads or the top level of the channel.

  • Top-level messages are grouped into conversations based on a time interval between messages from the same user. This defaults to 1 hour but you can change this in your Slack settings under the “Group top-level messages” setting
  • Threads are always tracked as individual conversations
  • If you have a conversation happening on the top level, you can thread off of a message to automatically split and create a new conversation out of that thread
  • If you have multiple conversations that you’d like to combine, you can also merge conversations


In this example where Sam is the customer and Tom is the support agent, the top-level messages will be grouped into a single conversation. If you choose to create a new thread off of one of those individual messages, that will automatically become its own separate conversation. Any replies in the top level with remain tracked to the initial conversation.


Once you start tracking conversations, you’ll want to take a look at some of the automations that you can configure: