Skip to main content

​
How triage prompts work

This page is for any team with an intake channel, like #ask-it, #design-requests, or #legal-help, where people post questions and someone has to route or answer each one. The two prompts below are Slack messages you paste in the request channel, in order. Together they set up a standing role: when someone tags @Claude on their request, it replies in-thread, answering what it can, flagging duplicates, and routing the rest. The weekly rollup lands as a top-level post in the same channel and sweeps anything that wasn’t tagged.

​
Check the channel’s connections

Check that the channel has the connections below. Ask @Claude what can you access from this channel? to check; an admin can add a connection the channel is missing.

​
Prompts to paste

Add Claude to the channel with /invite @Claude if it isn’t there, then two messages set it up.
1

Give the channel a standing role

“Remember for this channel” saves the role to channel memory, so it applies to everyone’s threads, not just yours. Tell requesters to include @Claude when they post; pin the convention or add it to the channel topic.
2

Add a weekly rollup so nothing is missed

“Including posts that didn’t tag you” turns the recap into a sweep, so requests that arrived without a mention are still caught. To list or cancel scheduled work later, see Manage standing work.
Answers draw on what the channel has already settled, meaning its memory and its own past threads, and routing gets more accurate as corrections land in channel memory.

​
Hand a request to the team that owns it

When a request belongs to another team, fork its thread into that team’s channel from inside the thread. Claude starts a new thread there with the request as background and leaves a link in the original thread, so the requester can follow the work without being re-asked for details.
The channel you name must be public, with both you and Claude in it. See Fork a thread for the other rules.

​
Give Claude a runbook of standing answers

When 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. To have Claude answer from the runbook, put the standing guidance in the Channel instructions field on the channel’s Configure page. 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, so name the cases to leave alone as explicitly as the answers. For a runbook kept as a document, Claude can read it when an admin has connected the app that holds it and the connection’s account can see the document. The instruction then points at the document:
The team keeps editing the document where it already lives, and the instruction reaches every new session in the channel. A team that wants each change reviewed as a pull request can keep its runbook as a skill in a skills repository, 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. When 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.

Set up routines

How the weekly rollup runs on a schedule

What Claude Tag remembers

How the standing role persists and improves