Add escalation process for support issues#48867
Conversation
Added a section on how to escalate a support issue using Unthread, including steps and tagging for visibility.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - Customer impact and urgency | ||
| - What has already been investigated (including logs, repro steps, and findings) | ||
| - The specific help needed (for example: CSA input, on-call engineering support, or infrastructure review) | ||
| 3. Tag Kathy Satterlee for visibility and coordination. |
There was a problem hiding this comment.
@ksatter I think we should keep this generic instead of calling you out by name. “Tag the CSE Team Lead.” I believe this is consistent with how we refer to Zay and myself elsewhere in the handbook.
zayhanlon
left a comment
zayhanlon
left a comment
There was a problem hiding this comment.
Incorporate Dale's requested changes but otherwise LGTM
|
@ddribeiro @ksatter is this ready to merge? |
Added a section on how to escalate a support issue using Unthread, including steps and tagging for visibility.
Handbook only change