> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tied.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Work a conversation from any channel without opening the dashboard — reply in the thread, and it goes straight back to the customer.

The usual Slack integration is a one-way mirror: a copy of the conversation lands in a channel, and if anyone replies there, it goes nowhere — a notification feed, not a place to work. Tied's Slack integration replies back. Post in the thread Tied created for a conversation, and that reply is delivered to the customer immediately, over whichever channel they actually messaged you on.

<Info>
  **This is an account-level connection, not a per-inbox one.** Connect Slack once, point it at a single
  channel, and every conversation from every inbox — email, WhatsApp, web chat, all of it — threads into
  that one place.
</Info>

## What it takes

| Requirement | |
| - | - |
| **Plan** | All plans |
| **Slack workspace** | Admin ability to install an app and pick a channel |
| **Time** | Minutes |

## How it works

<Steps>
  <Step title="Connect your Slack workspace" icon="plug">
    A standard OAuth grant — Tied asks for permission to post messages, read channel and user info, and
    upload files.
  </Step>

  <Step title="Choose the channel" icon="hash">
    Pick one Slack channel to receive conversations. Every conversation, from every inbox, threads there.
  </Step>

  <Step title="Reply from the thread" icon="reply">
    Type **in the thread** — a top-level message posted to the channel itself is not picked up, only a
    threaded reply is. Tied posts it back to the customer as a reply on that conversation. Tied matches
    you by email — the address on your Slack account has to match the address on your Tied login for
    the reply to be attributed to you. If it doesn't match, the message still goes to the customer; it
    just goes out unattributed.
  </Step>
</Steps>

<Note>
  **Prefix a thread reply with `note:` or `private:` to keep it off the customer's phone.** Either
  keyword, case-insensitive, files the message as an internal note on the conversation instead of
  sending it — useful for coordinating in the same thread without every aside going out as a reply.
</Note>

<Warning>
  **Slack is where your team works a conversation, not where a customer starts one.** A customer can't
  message your business on Slack the way they can on Instagram or Telegram — every conversation still
  arrives through one of Tied's other channels. What Slack gives you is a second place to *answer* it, not
  a new front door.
</Warning>

## No channel fee

Slack carries no carrier cost and no Tied channel fee. See [Channel fees](/pricing/channel-fees).

## Next

<CardGroup cols={2}>
  <Card title="The inbox" icon="inbox" href="/inbox">
    Where conversations live when you're not answering from Slack.
  </Card>

  <Card title="Channel fees" icon="radio" href="/pricing/channel-fees">
    Slack costs nothing to deliver on — see what does.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.