Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
One change · claude-docs

Triage requests changed

claude-tag/users/use-cases/triage-requests

Nearest release: v2.1.268, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+24added
Lines−5removed
From line 1 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits3to this page, all time

## Give Claude a runbook of standing answers

The whole hunk

from line 1, old and new numbered
/
lines
from line 1
11# Triage requests
22 
3> Claude Tag triages a Slack request channel with two setup messages. See in-thread answers, duplicate flags, owner routing, weekly theme rollups, and optional ticket filing.
3> Claude Tag triages a Slack request channel with two setup messages. See in-thread answers, duplicate flags, owner routing, weekly theme rollups, optional ticket filing, and runbooks of standing answers.
44 
55export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
66 
from line 16
1616 
1717Check that the channel has the connections below. Ask `@Claude what can you access from this channel?` to check; an admin can [add a connection](/docs/claude-tag/admins/add-connections) the channel is missing.
1818 
19| Connection | Examples | Why it matters here |
20| :------------- | :----------- | :-------------------------------------- |
21| None | — | Works on Slack content alone |
22| Issue tracking | Linear, Jira | Optional. Files routed items as tickets |
19| Connection | Examples | Why it matters here |
20| :----------------- | :------------------- | :---------------------------------------------------------------------------------------------------------------- |
21| None | — | Works on Slack content alone |
22| Knowledge and docs | Google Drive, Notion | Optional. Reads a [runbook](#give-claude-a-runbook-of-standing-answers) or past decisions the team keeps in a doc |
23| Issue tracking | Linear, Jira | Optional. Files routed items as tickets |
2324 
2425## Prompts to paste
2526 
from line 55
5455```
5556 
5657The channel you name must be public, with both you and Claude in it. See [Fork a thread](/docs/claude-tag/users/commands#fork-a-thread) for the other rules.
58 
59## Give Claude a runbook of standing answers
60 
61When people keep posting the same questions in a channel, give Claude the team's settled answers instead of leaving it to derive an answer from the channel's history each time. A runbook is the team's own document of those answers, kept in whatever form the team already uses, such as a Google Doc. It can say which requests have a standard answer, which route to an owner, and which the team answers itself.
62 
63To have Claude answer from the runbook, put the standing guidance in the **Channel instructions** field on the channel's [Configure page](/docs/claude-tag/users/good-habits#configure-claude-for-a-channel). The field needs no connection, and a short runbook can go in it whole. Claude [reads a channel's untagged messages and replies to some of them on its own](/docs/claude-tag/users/when-claude-responds), so name the cases to leave alone as explicitly as the answers.
64 
65For a runbook kept as a document, Claude can read it when an admin has [connected the app that holds it](/docs/claude-tag/admins/add-connections) and the connection's account can see the document. The instruction then points at the document:
66 
67```text wrap theme={null}
68Answer requests in this channel from the team's triage runbook: <link to the runbook doc>. Read it before answering. If a request isn't covered there, mention <your on-call person's handle> so they can pick it up.
69```
70 
71The team keeps editing the document where it already lives, and the instruction reaches every new session in the channel.
72 
73A team that wants each change reviewed as a pull request can keep its runbook as a skill in a [skills repository](/docs/claude-tag/admins/skills-repo), a git repository an Owner registers and attaches to the channel; a merged pull request syncs the update to your organization automatically, and anyone in the channel can ask Claude to draft that pull request.
74 
75When an answer changes, update the runbook where it lives. Edit the document, edit and save the **Channel instructions** field, or merge a pull request in the repository. However you ship the update, check the changed answer in a fresh thread. A thread already underway keeps the instructions and skills it started with.
5776 
5877## Related resources
5978