Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
116 changes: 66 additions & 50 deletions advanced-support.mdx
Original file line number Diff line number Diff line change
@@ -1,99 +1,115 @@
---
title: "Advanced support"
description: "Get premium support with faster response times, a dedicated customer success manager, and priority assistance for your documentation site."
keywords: ["support", "CSM", "enterprise"]
keywords: ["support", "CSM", "enterprise", "SLA"]
---

## Support options
## Support tiers

- All customers receive support via dashboard or support@mintlify.com (24 hour response)
- Enterprise plan customers can add Advanced Slack support (24-hour response) or a dedicated CSM (4-hour response + strategic partnership)
Mintlify offers three support tiers. The right tier depends on the level of commitment, response time, and relationship you need.

### Standard support (included)

Included with all Pro and Enterprise plans. Submit tickets through the dashboard or email support@mintlify.com. First response within 24-48 hours.
Included with all Pro and Enterprise plans. Reach us through the dashboard or at support@mintlify.com. We do our best to respond and resolve issues quickly.

### Advanced Slack support (add-on)
### Advanced Slack Support (add-on)

Check warning on line 15 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L15

'Advanced Slack Support (add-on)' should use sentence-style capitalization.

Get a dedicated Slack channel with our support team for faster troubleshooting.
We set up a dedicated Slack channel for your team. An AI tool monitors the channel, detects support-related messages, and automatically routes them into our support inbox where our team responds.

**What you get:**
- Slack channel for your team and Mintlify support engineers
- 24-hour first response SLA
- Dedicated Slack channel connected to our support team
- Automatic AI-powered issue detection and routing to our support inbox
- Priority-based SLA response times (see table below)
- Expedited bug escalation to the Mintlify engineering team

**Best for:** Teams that need faster response times but don't require strategic partnership or scheduled check-ins.
**Best for:** Teams that need faster, structured response times without requiring a dedicated point of contact.

### Dedicated CSM (add-on)

Get an assigned Customer Success Manager who knows your team, setup, and goals.
You get an assigned Customer Success Manager who owns your dedicated Slack channel. Your CSM responds to questions directly and manually escalates issues to the support team when needed — enabling faster internal coordination and resolution by working alongside support in real time.

Check warning on line 29 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L29

Don't put a space before or after a dash.

**What you get:**
- Assigned CSM as your primary contact
- 4-hour first response SLA (9 AM-5 PM PST for US customers, 24 hours international)
- Dedicated Slack channel
- Monthly check-ins
- Quarterly business reviews
- Assigned CSM as your primary contact and channel owner
- Manual escalation to the support team with direct internal coordination
- Priority-based SLA response times (see table below)
- Monthly check-ins and quarterly business reviews
- Shared feature request tracker with direct product team escalation
- Priority bug and incident escalation

**Best for:** Teams that need fast responses, proactive guidance, and influence over the product roadmap.
**Best for:** Teams that need fast resolution, a named point of contact, and a strategic partner.

### SLA response times

Both add-ons include the same priority-based SLA commitments. Mintlify will use commercially reasonable efforts to meet the following service levels:

Check warning on line 43 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L43

Avoid using 'will'.

| Priority | Definition | Initial Response | Target Resolution |
|---|---|---|---|
| **P0 – Critical** | Complete service outage or security incident | 15 minutes | 1 hour |

Check warning on line 47 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L47

Don't put a space before or after a dash.
| **P1 – High** | Major functionality blocked with no available workaround | 1 hour | 3 hours |

Check warning on line 48 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L48

Don't put a space before or after a dash.

Check warning on line 48 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L48

Use 'capability' or 'feature' instead of 'functionality'.
| **P2 – Medium** | Partial degradation or functionality issue with a workaround | 6 hours | 48 hours |

Check warning on line 49 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L49

Don't put a space before or after a dash.

Check warning on line 49 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L49

Use 'capability' or 'feature' instead of 'functionality'.
| **P3 – Low** | Minor issues, cosmetic bugs, or general product inquiries | 12 hours | 96 hours |

Check warning on line 50 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L50

Don't put a space before or after a dash.

<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).

Check warning on line 53 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L53

In general, use active voice instead of passive voice ('are managed').

**P1–P3 response times apply during Mintlify business hours only: 9 AM–5 PM PT, Monday–Friday, excluding US holidays.**
</Note>

## FAQ

### Dedicated CSM

<AccordionGroup>
<Accordion title="What's the difference between a dedicated CSM and standard support?">
We deliver standard support via the dashboard or support@mintlify.com with a 24-48 hour response SLA. A Dedicated CSM includes both a primary point of contact and a dedicated Slack channel. The main differences are:

- **Response time:** 4 hours for US customers during business hours versus 24-48 hours for standard support
- **Relationship:** One person who knows your setup versus a support team rotation
- **Proactive engagement:** Monthly check-ins and QBRs versus reactive support
- **Product influence:** Direct escalation to the product team and input on the roadmap
- **Strategic planning:** Quarterly business reviews and success planning
</Accordion>
<Accordion title="What's the difference between a Dedicated CSM and Advanced Slack Support?">
Both tiers include the same priority-based SLA response time commitments. The difference is in how your issues reach our team:

<Accordion title="Why is a dedicated CSM priced at a premium?">
You're getting a person who knows your team, your setup, and your goals—not a support queue. This includes:
- **Advanced Slack Support** uses an AI tool to automatically detect and route support messages from your Slack channel to our support inbox.
- **Dedicated CSM** gives you an assigned CSM who actively monitors your channel, responds to questions directly, and manually escalates to the support team — enabling faster internal coordination and resolution.

The Dedicated CSM tier also includes monthly check-ins, quarterly business reviews, and a shared feature request tracker with direct product team access.
</Accordion>

- 4-hour response SLA (versus 24-48 hours for standard support)
- Monthly check-ins and quarterly business reviews
- Direct influence on what we build
- Priority escalation for bugs and incidents
- Curated feature updates and enablement materials
<Accordion title="What's the difference between a Dedicated CSM and standard support?">
Standard support (included with all Pro and Enterprise plans) is best-effort with no binding SLA commitments. A Dedicated CSM includes:

This is premium, high-touch service calibrated for teams where fast resolution and strategic partnership matter. If you want faster support without the full CSM relationship, our advanced Slack support option gives you a dedicated channel with 24-hour response times at a lower price point.
- **Binding SLA commitments** with defined priority-based response and resolution times
- **Dedicated Slack channel** with an assigned CSM as your primary contact
- **Proactive engagement:** Monthly check-ins and quarterly business reviews
- **Product influence:** Direct escalation to the product team and roadmap input
</Accordion>

<Accordion title="How does feature request tracking work?">
Every dedicated CSM customer gets a shared Google Sheet tracker where you can:
Every Dedicated CSM 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.

Check warning on line 82 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L82

In general, use active voice instead of passive voice ('are scoped').
</Accordion>
</AccordionGroup>

- Submit feature requests with context and priority
- See status updates as requests move through review and development
- Track which features have been shipped
- Provide feedback and additional details as features are scoped
### Advanced Slack Support

Check warning on line 86 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L86

'Advanced Slack Support' should use sentence-style capitalization.

<AccordionGroup>
<Accordion title="What's the difference between Advanced Slack Support and standard support?">
Standard support (included with all Pro and Enterprise plans) is best-effort with no binding SLA commitments. Advanced Slack Support includes:

Your CSM reviews this tracker regularly and escalates priority items directly to our product team.
- **Dedicated Slack channel** with AI-powered issue detection and automatic routing to our support inbox
- **Expedited bug escalation** to the Mintlify engineering team
</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.

Check warning on line 97 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L97

In general, use active voice instead of passive voice ('are captured').

Check warning on line 97 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L97

Did you really mean 'triaged'?
</Accordion>
</AccordionGroup>

### Advanced Slack support
### SLAs and coverage hours

Check warning on line 101 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L101

Did you really mean 'SLAs'?

<AccordionGroup>
<Accordion title="What's the difference between advanced Slack support and standard support?">
We deliver standard support (included with Pro and Enterprise plans) via the dashboard or support@mintlify.com with a 24-48 hour response SLA. Advanced Slack support includes:

- Dedicated Slack channel versus email/dashboard support
- 24-hour response SLA versus 24-48 hours for standard support
- Expedited bug escalation to the Mintlify engineering team
<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).

Check warning on line 105 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L105

In general, use active voice instead of passive voice ('is determined').

Check warning on line 105 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L105

In general, use active voice instead of passive voice ('are met').
</Accordion>

<Accordion title="Why is advanced Slack support priced separately?">
You're getting a dedicated Slack channel with our support team plus expedited engineering escalation for bugs and incidents—not email support with 24-48 hour response times. This is premium support for teams that need faster answers without the full strategic CSM relationship.
<Accordion title="What are Mintlify business hours?">
Business hours for P1–P3 SLA commitments are **9 AM–5 PM PT, Monday–Friday, excluding US public holidays.** P0 incidents are covered 24/7 and handled by Mintlify engineering.

Check warning on line 109 in advanced-support.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

advanced-support.mdx#L109

In general, use active voice instead of passive voice ('are covered').
</Accordion>
</AccordionGroup>

## Get started

Contact your Mintlify account team to add advanced Slack support or a dedicated CSM, or email gtm@mintlify.com.
Contact your Mintlify account team to add Advanced Slack Support or a Dedicated CSM, or email gtm@mintlify.com.
Loading