claude.ai/oncall.
On-call is available on the Team and Enterprise plans. Who can open claude.ai/oncall and run setup depends on your plan.
- Team plan: any member of your organization. A change that affects the whole organization saves only if your account has permission to make it.
- Enterprise plan: an Owner or a Claude Tag admin, meaning a member whose custom role sets Claude Tag Admin to Can manage. Other members, including those with the built-in Admin role and channel managers, don’t see On-call in the Code sidebar and can’t open setup.
What an on-call is
Your organization’s on-call is an Access bundle carrying the connections, repositories, and skills Claude uses for incident work. The bundle attaches to the channels you pick during setup, and any routines you schedule in those channels, like a morning incident digest, run alongside it. Setup builds the bundle, and after you deploy you edit it like any other bundle in Give Claude access. Setup offers two ways for Claude to work, and you can use either or both.- Watch your alerts. Claude watches your monitoring tools and posts what it finds in a channel you choose.
- Join incident channels. Claude joins the incident channels you pick and investigates alongside your team, without waiting to be tagged. A channel-name prefix, like
incident-, has Claude join new public channels that match.
Run setup
Go toclaude.ai/oncall, or open Code in claude.ai and click On-call in its sidebar. The page shows one on-call for your whole organization, so anyone else who can open it sees the same settings.
The page opens on setup cards for your organization’s shared on-call. The cards cover what Claude needs for incident work, such as connecting monitoring and alerting tools, granting repositories, and picking the Slack channels Claude works in. Act on each card, then click the Deploy on-call button to put Claude on call in the channels you chose.
If you’d rather be interviewed than work through the cards yourself, click the Chat to set up on-call button. Claude asks how your team runs incidents and sets up the on-call from your answers.
Channels Claude joins
During setup you pick the Slack channels where Claude does its on-call work. You can name channels directly, set a channel-name prefix, or both.- Pick channels. Choose the channels Claude should work in. To add a private channel, type
/invite @Claudein that channel in Slack. - Set a channel-name prefix. A prefix, like
incident-, has Claude join matching channels automatically, so a channel opened mid-incident gets Claude without anyone adding it.
Let your team know
Setup includes an option to have Claude introduce itself to your team after you deploy. Leave it on, and Claude sends a direct-message introduction to each member of your Slack workspace who has a Claude account in your organization, and to no one else. Each of those members gets the introduction once, as up to three messages, with no follow-ups, and the messages don’t count toward your usage. Turn the option off to skip the introductions. Members can use Claude either way once the on-call is live.After you deploy
Claude is on call in the channels you chose, and, if you set a channel-name prefix, it joins new public channels that match as they’re created. The on-call’s connections, repositories, and skills make up its Access bundle. To change the on-call later, go toclaude.ai/oncall. Outside setup, these roles manage the on-call’s Access bundle:
- Owner: edit the bundle in Give Claude access, set per-channel access, and change the monthly spend limit
- Claude Tag admin, on the Enterprise plan: edit the bundle and set per-channel access
Related resources
- Set up Claude Tag: the standard setup steps, and how to verify your setup afterward
- How agent identity works: why Claude gets its own accounts in your tools
- Watch monitors and alerts: what Claude’s monitoring work looks like in a channel