53 Use case library
Shapes of work teams hand Claude Tag in Slack, each with prompts to paste. See triage, catch-up, docs and tickets, project tracking, data, deals, monitoring, and bug fixes.
export const BetaNote = () => Claude Tag is in public beta. Features and behavior described here may change before general availability.;
Each use case below links to a page with prompts to paste, what it needs connected, and how to set it up to run on a schedule or watch the channel instead of asking each time.
If @Claude doesn’t autocomplete in your workspace, your admin hasn’t enabled Claude Tag. Send them the setup guide.
53.1 All use cases
| Use case | Who it’s for | What Claude does | Connections needed |
|---|---|---|---|
| Catch up | Anyone | Summarizes a thread, a channel, or what’s waiting on you | Nothing |
| Work from your own channel | Anyone | Answers scratch questions, digests channels you don’t follow, and chases what you said you’d do | Nothing (issue tracker or GitHub optional) |
| Triage requests | Support, ops, IT, any intake channel | Answers what it can, flags duplicates, routes the rest, rolls up themes | Nothing (issue tracker optional for filing) |
| Turn threads into docs and tickets | Anyone | Produces a decision doc, status memo, ticket, send-ready reply, or hosted web page from a discussion | Nothing (Drive or issue tracker optional) |
| Track projects and chase approvals | PMs, leads, anyone running a project channel | Posts standing status digests; follows up on stalled sign-offs | Nothing (issue tracker optional) |
| Find answers in your docs | Anyone | Looks up policies, runbooks, prior decisions; replies with the source | Google Drive, Notion, or Confluence |
| Review documents against a checklist | Ops, compliance, anyone reviewing against criteria | Checks documents in a connected tool against a checklist or policy; posts findings per item | Google Drive, Notion, or Confluence |
| Answer data questions | Analysts, data-adjacent teams | Runs warehouse queries, returns charts; or charts from Slack history alone | BigQuery, Snowflake, or Redshift (charts from Slack need none) |
| Fix bugs | Engineering | Reproduces the bug, opens a draft PR, follows CI to green | GitHub (Datadog, Sentry optional) |
| Work with GitHub | Engineering, anyone with repository questions | Answers repository questions in-thread, watches pull requests for you, turns postponed chores into draft PRs | GitHub |
| Watch monitors and alerts | On-call, SRE | Checks dashboards on a schedule; investigates alerts before anyone asks | Datadog, Sentry, or PagerDuty |
| Pull deal and account state | Sales, customer success | Answers account questions in-thread; pre-call briefs; weekly pipeline digest | Salesforce, HubSpot, or Gong |
| Claude Tag for marketing teams | Marketing | Answers policy questions from team docs, drafts from campaign threads, checks lead state, posts a weekly metrics digest | HubSpot or Salesforce, plus Google Drive or Notion; BigQuery or Snowflake for the metrics digest (varies by recipe) |
53.2 Use cases by connection
A connection is a tool an admin linked for the channel. Each one adds a category of work; ask @Claude what can you access from this channel? to see which your channel has.
| Connection | Examples | What it adds |
|---|---|---|
| Knowledge and docs | Google Drive, Notion, Confluence | Find answers in your docs |
| Issue tracking | Linear, Jira, Asana | Turn threads into tickets, track projects |
| Data warehouse | BigQuery, Snowflake | Answer data questions with charts |
| Go-to-market | Salesforce, HubSpot, Gong | Pull deal and account state |
| Monitoring | Datadog, Sentry, PagerDuty | Watch monitors and alerts |
| Code | GitHub | Fix bugs, open pull requests, follow CI |
If a connection your work needs is missing, an admin can add it.