What you can build
Channel delivery
Agents post updates into the account’s internal or shared channel — never a channel they picked themselves.
Guide verification
A guide closes an outcome on a fresh read of a pinned channel — what the customer’s team actually said.
External approvals by DM
Approval requests reach people outside Thread as Slack DMs with a working approve link.
Customer portal experience
Use Slack as the day-to-day surface; the portal as the source of truth.
Connect Slack
1
Open Connectors → Slack → Connect
Go to Connectors → Slack in Thread, click Connect, and sign in to Slack to approve the workspace install. Thread requests permission to read your channel list and post messages — that’s it.
2
Invite the Thread app to channels
The Thread app only posts to channels it’s been invited into. In each shared/internal channel: type
/invite @Thread. Channel admins can do this in bulk via Slack’s app settings.3
Set up account channels
Configure your org’s internal alerts channel and each account’s internal/shared channels so
Thread knows where things go. Agents post to these configured destinations — they can’t name
an arbitrary channel.
What Thread can do in Slack
Agent delivery. Agents post updates into server-resolved destinations — your org’s alerts channel, or the account’s internal or shared (external) channel. The destination is resolved from configuration, never chosen freehand by the agent; if a destination isn’t configured, the action refuses rather than falling back to another channel. Agents can also read channel history, look up users by email, and create channels — all bounded by which channels the Thread app is a member of. Guide verification. Attach the Slack tool to a guide and pin a channel (or leave it unpinned to see the channels the workspace invited the bot into). When the guide checks an outcome, it takes a fresh read of recent channel messages — and only messages from the customer it’s working with can count as evidence. The read lands in the watch log as a receipt. See Outcomes and verification. External approvals. When an agent needs a sign-off from someone outside Thread, the approval request can arrive as a Slack DM with a working, no-login approve link. See External approvals.Tips from the field
Use shared channels
A Slack Connect channel per customer makes Thread feel like a teammate, not a tool.
Keep messages short
Two lines plus a portal link beats a wall of text every time.
Don't @channel everything
Reserve
@here for rollout-blocking moments. Routine updates don’t need pings.Mirror, don't replace, the portal
The portal is the source of truth. Slack messages link back to it.
Troubleshooting
`channel_not_found`
`channel_not_found`
The Thread app isn’t in that channel yet. In Slack:
/invite @Thread, then re-run the action.Messages aren't posting
Messages aren't posting
Check the connection status in Connectors → Slack. If the workspace was reinstalled or the user who connected left, reconnect from a current admin account.
Customer can't see updates
Customer can't see updates
Confirm the account’s shared (external) channel is configured and that the message targeted it, not the internal channel. An agent posting to “the account’s channel” goes wherever your configuration points.
A guide's channel check finds nothing
A guide's channel check finds nothing
Check that the right channel is pinned on the guide’s Slack tool row and the Thread app is a member of it. Only messages from the enrolled customer count as evidence — activity from your own team doesn’t close their outcome.
Next steps
Outcomes and verification
How a channel read closes a guide’s outcome.
External approvals
Approve-by-DM for people outside Thread.