Clarify Slack as source in support tier comparison table#6177
Conversation
…nd CSM escalation Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Summary
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only copy change with no product, API, or runtime behavior impact.
Overview
Updates the How issues reach us row in the support tier comparison table on
advanced-support.mdxso Tier 2 and Tier 3 explicitly name Slack as the intake channel.Tier 2 now reads AI routing from Slack (was AI routing). Tier 3 now reads CSM escalates from Slack (was CSM escalates manually). Standard (email or dashboard) is unchanged.
Reviewed by Cursor Bugbot for commit a26ebb6. Bugbot is set up for automated code reviews on this repo. Configure here.