Clarify Slack as source in support tier comparison table

advanced-support.mdx

@@ -11,7 +11,7 @@
 | | Standard | Advanced Slack | Dedicated CSM |
 |---|---|---|---|
 | **Tier** | 1 (included) | 2 (add-on) | 3 (add-on) |
-| **How issues reach us** | Email or dashboard | AI routing | CSM escalates manually |
+| **How issues reach us** | Email or dashboard | AI routing from Slack | CSM escalates from Slack |
 | **Response time targets** | Best effort | P0–P3 | P0–P3 |
 | **Named contact** | No | No | Yes |
 | **Monthly check-ins** | No | No | Yes |
@@ -61,17 +61,17 @@
 
 ### Response time targets
 
 Tiers 2 and 3 include the same response time targets. Mintlify will use commercially reasonable efforts to meet the following service levels:
 
 | Priority | Definition | Initial response | Target resolution |
 |---|---|---|---|
 | **P0 – Critical** | Complete service outage or security incident | 15 minutes | 1 hour |
 | **P1 – High** | Major functionality blocked with no available workaround | 1 hour | 3 hours |
 | **P2 – Medium** | Partial degradation or functionality issue with a workaround | 6 hours | 48 hours |
 | **P3 – Low** | Minor issues, cosmetic bugs, or general product inquiries | 12 hours | 96 hours |
 
 <Note>
 **P0 is the only priority level with 24/7 response coverage.** P0 incidents (complete service outage or security incident) are managed directly by Mintlify engineering. We publish real-time status updates and incident progress at [status.mintlify.com](https://status.mintlify.com).
 
 **P1–P3 response times apply during Mintlify business hours only: 9 AM–5 PM PT, Monday–Friday, excluding US holidays.**
 </Note>
@@ -100,7 +100,7 @@
   </Accordion>
 
   <Accordion title="How does feature request tracking work?">
     Every Tier 3 customer gets a shared tracker where you can submit feature requests with context and priority, see status updates as requests move through review and development, and provide feedback as features are scoped. Your CSM reviews this regularly and escalates priority items directly to our product team.
   </Accordion>
 </AccordionGroup>
 
@@ -116,7 +116,7 @@
   </Accordion>
 
   <Accordion title="How does the AI routing work?">
     When you send a message in your dedicated Slack channel, our AI tool detects whether it's a support-related issue and automatically routes it to our support inbox. This ensures your issues are captured and triaged without requiring manual intervention.
   </Accordion>
 </AccordionGroup>
 
@@ -124,11 +124,11 @@
 
 <AccordionGroup>
   <Accordion title="What counts as a P0 incident?">
     A P0 is a complete service outage or security incident affecting your Mintlify deployment. P0 classification is determined by Mintlify. We monitor our systems continuously and proactively open P0 incidents when the criteria are met. Real-time status is always available at [status.mintlify.com](https://status.mintlify.com).
   </Accordion>
 
   <Accordion title="What are Mintlify business hours?">
     P1–P3 response time targets apply during **9 AM–5 PM PT, Monday–Friday, excluding US public holidays.** P0 incidents are covered 24/7 and handled by Mintlify engineering.
   </Accordion>
 </AccordionGroup>