Skip to main content

Slack

Slack support routes approved Slack activity into the same Woes inbox as live chat, email, and Discord. Use it when customers, partners, or internal teams ask support questions in shared Slack channels or direct messages.

What Slack Adds

  • OAuth install for a Slack workspace.
  • Workspace-level Slack intake controls.
  • Direct-message support when enabled.
  • Per-channel intake modes for app mentions, every message, or ticket emoji.
  • Safe file metadata capture when file handling is enabled.
  • AI and operator replies posted back into the original Slack thread.
  • Optional operator Slack notifications through each operator’s notification settings.

Setup Flow

1

Connect Slack

Go to Workspace Settings -> Integrations -> Slack and click Connect.
2

Enable Slack intake

Open Settings -> Channels -> Slack and turn on Slack intake for the workspace.
3

Choose intake surfaces

Decide whether Woes should accept direct messages, file metadata, and selected channel messages.
4

Configure channels

Refresh the channel list, then choose the ticket mode for each enabled channel.
5

Choose the answering agent

In assignment settings, choose the agent that should handle Slack conversations.
6

Test a thread

Send a test app mention, direct message, or ticket emoji in an enabled Slack surface and confirm it appears in the Woes inbox.

Intake Modes

Slack Replies

When a Slack message becomes a Woes conversation, operators work from the Woes inbox. AI replies and operator replies are posted back into the original Slack thread when the Slack connection and channel rules allow it.

Data And Privacy

Slack is a customer conversation channel, not a Context Library source. Woes uses Slack metadata to route and display conversations, but private file URLs and raw connection credentials are not exposed to customers. Only enable channels where support messages belong in Woes. For broad community channels, app mentions or ticket emoji usually create a cleaner support flow than every-message intake.

Troubleshooting

Last modified on July 4, 2026