Claude in Slack: what the team channel should hand to AI, and what it should not
Putting Claude in a busy CX Slack channel: what it answers alone, what it drafts for a person, and what always stays human.
A busy operations channel can get 100 to 200 messages a day. Most of them are questions someone has answered before. Putting Claude in that channel is less about AI and more about deciding, in advance, where the line sits.
Three lanes
CheckPassesHeld for a person
Process questionsanswered from the team's own docswhen the doc is missing or out of date
Ticket summariesposted in the thread on requestwhen the ticket holds customer data that should not move
Customer repliesnever sent from Slackalways drafted for a person to send
How a question moves
01Tagsomeone tags Claude in the thread
02Readit reads the whole thread, not a pasted summary
03Answer or hand overby the lane rules above
04Logevery answer is kept for the weekly sample
What changed for the team
Before
- The same questions asked every week
- Whoever saw it first answered
- Answers lost in the scroll
- Leads interrupted all day
With Claude in the channel
- Answered in the thread in seconds
- The answer comes from the team docs
- Logged and sampled weekly
- Leads see only what was handed over
This sits next to the Slack dispatcher, which routes messages to the right channel in the first place.