Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Preview links (active after the
|
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
The On-Call offboarding guide covers removing schedules, escalation policies and notification preferences, but never mentions unassigning the user's seat. Following the guide end to end leaves the seat assigned and still billable.
A customer did exactly that after winding down an On-Call POC and kept 3 billable seats for five weeks. Raised it with Simone Tafaro on the On-Call side, who confirmed it is worth adding.
Adds a short
Unassign the seatsection, one line to the intro list, and a link to the Incident Response billing page.Merge readiness
AI assistance
Used Claude Code to draft the section and open the PR.
Additional notes
Kept small on purpose. The guide also opens with "Datadog charges for users who are actively configured in On-Call", which does not line up with the seat-based model described in the Incident Response billing doc. Worth a separate follow-up rather than bundling it here.
🤖 Generated with Claude Code