mirror of
https://github.com/mintlify/docs.git
synced 2026-09-14 13:35:46 +08:00
017d7c7377
* fix: reduce Vale false positives via vocab and config updates - Make English-word vocab entries case-insensitive so sentence-start capitalization and normal prose usage stop flagging (agents, rest, cursor, setup, endpoints, etc.) - Add vocab entries for filenames and code identifiers that appear in frontmatter and JSX contexts (docs.json, llms.txt, CLAUDE.md, etc.) - Ignore openapi frontmatter lines, filenames, JSX attributes, email addresses, and internal link targets via TokenIgnores - Skip inline code scope and indented code fences - Add Headings exceptions for proper nouns (Claude Code, GitHub Actions, Route 53, GA4, etc.) - Disable linting for the all-code vercel-json-generator snippet Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix: resolve all Vale warnings and errors across docs Content fixes: - Reword sentences using 'will', first person, spaced em dashes, 'e.g.', Latin abbreviations, and hyphenated adverbs - Sentence-case headings that started with dotted filenames - Backtick literal API values instead of bolding them - Move periods inside quotation marks - Fix Oxford comma rule misfires by restructuring sentences False-positive suppression: - Vale toggles around example user questions, keyboard shortcut keys (Cmd+I), UI labels, and code samples in JSX contexts that Vale misparses - Exclude vale toggle comments from the brace Token/BlockIgnores so in-document commands actually reach Vale (the greedy brace pattern was also silently swallowing large regions; now lazy) - Vocab entries for code identifiers (internal_id, handleSubmit, etc.) - Per-file rule disables for component docs with dotted JSX names and files where link-target linting ignores in-document toggles Result: vale --minAlertLevel warning is clean repo-wide; only suggestion-level items (Passive, Semicolons, Acronyms) remain. mint broken-links passes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix: correct WordList rule instead of degrading prose - Restore sentence-start "Email" in advanced-support; the rule now only flags hyphenated e-mail/E-mail forms - Restore the idiom "above all else"; the above->preceding swap now exempts "above all" Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix: restore deliberate prose flagged by blunt rules - Restore spatial 'above the navbar' / 'above a page title' in custom-scripts; the above->preceding swap now exempts 'above the/a/an' - Restore the '= ...' in the react-components named-export example (the ellipsis is inside inline code) with an Ellipses toggle - Restore SLA phrasing 'will use commercially reasonable efforts' with a Will toggle - Restore the quoted developer question in the GEO guide intro with a FirstPerson toggle, matching the file's other example questions Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix: remove WordList swaps that flag legitimate English - Drop tablet->device and firewalls->firewall rules; both words are correct in ordinary prose - Narrow touch->tap to UI-instruction phrasing (touch the/a) so 'keep in touch' and 'touch devices' stop flagging Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix: reposition vale toggles to wrap whole blocks Toggle comments placed between list items split the lists (restarting ol numbering in deployments) and comments flush against tables risked breaking GFM table parsing. Wrap entire lists/tables with blank-line separation instead. Verified rendering with mint dev: single ol with two items, tables intact, no comments in visible DOM. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor: prune accept.txt to load-bearing entries Empirically removed 166 vocab entries (575 -> 409) whose removal causes no Vale flags across all 908 English pages: dictionary words that never needed listing (agents, setup, endpoints, webhooks, yaml), lowercase entries the speller already accepts, and filename entries made redundant by inline vale toggles. Kept every case-enforcing entry (API, JSON, GitHub, ...) so casing policy is unchanged, plus entries that double as capitalization exceptions for headings (mcp, md, auth, cursor, txt). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Update ai/mintlify-mcp.mdx * Update api/agent/v2/create-agent-job.mdx * chore: alphabetize Headings exceptions and accept.txt Case-insensitive sort, ignoring the (?i) prefix; also drops a duplicate Scala entry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix: re-apply OxfordComma rewrite lost in branch merge Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs: resolve Vale suggestions batch 1 (acronyms, semicolons, passive voice) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs: resolve remaining Vale suggestions (passive voice batch 2) Rewrite ~90 passive constructions to active voice across deploy, guides, migration-services, and organize docs. Toggle the deliberate passive examples in the style-and-tone guide ('by zombies' test). Add axios/lodash vocab entries for a repositioned code example. vale . is now fully clean: 0 errors, 0 warnings, 0 suggestions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
142 lines
7.6 KiB
Plaintext
142 lines
7.6 KiB
Plaintext
---
|
||
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"]
|
||
---
|
||
|
||
## Support tiers
|
||
|
||
Mintlify offers three support tiers. The right tier depends on the level of commitment, response time, and relationship you need.
|
||
|
||
| | Standard | Advanced Slack | Dedicated CSM |
|
||
|---|---|---|---|
|
||
| **Tier** | 1 (included) | 2 (add-on) | 3 (add-on) |
|
||
| **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 |
|
||
| **Feature request tracking** | No | No | Yes |
|
||
|
||
<CardGroup cols={1}>
|
||
<Card title="Tier 1 · Standard" icon="laptop" href="#tier-1-standard-support-included">
|
||
Included with all plans. Reach us via the dashboard. Best-effort response with no time target commitments.
|
||
</Card>
|
||
<Card title="Tier 2 · Advanced Slack Support" icon="slack" href="#tier-2-advanced-slack-support-add-on">
|
||
Dedicated Slack channel with AI-powered routing to our support inbox. Includes response time targets for P0–P3 issues.
|
||
</Card>
|
||
<Card title="Tier 3 · Dedicated CSM" icon="handshake" href="#tier-3-dedicated-csm-add-on">
|
||
An assigned CSM owns your channel, responds directly, and escalates to support internally. The highest level of hands-on support we offer.
|
||
</Card>
|
||
</CardGroup>
|
||
|
||
### Tier 1: Standard support (included)
|
||
|
||
Included with all Enterprise plans. Reach us through the dashboard or at support@mintlify.com. We do our best to respond and resolve issues quickly.
|
||
|
||
### Tier 2: Advanced Slack Support (add-on)
|
||
|
||
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:**
|
||
- Dedicated Slack channel connected to our support team
|
||
- Automatic AI-powered issue detection and routing to our support inbox
|
||
- Priority-based response time targets (see table below)
|
||
- Expedited bug escalation to the Mintlify engineering team
|
||
|
||
**Best for:** Teams that need faster, structured response times without requiring a dedicated point of contact.
|
||
|
||
### Tier 3: Dedicated CSM (add-on)
|
||
|
||
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).
|
||
|
||
**What you get:**
|
||
- Assigned CSM as your primary contact and channel owner
|
||
- Manual escalation to the support team with direct internal coordination
|
||
- Priority-based response time targets (see table below)
|
||
- Monthly check-ins
|
||
- Shared feature request tracker with direct product team escalation
|
||
- Priority bug and incident escalation
|
||
|
||
**Best for:** Teams that need fast resolution, a named point of contact, and a strategic partner.
|
||
|
||
### Response time targets
|
||
|
||
Tiers 2 and 3 include the same response time targets. {/* vale Mintlify.Will = NO */}
|
||
Mintlify will use commercially reasonable efforts to meet the following service levels:
|
||
{/* vale Mintlify.Will = YES */}
|
||
|
||
| Priority | Definition | Initial response | Target resolution |
|
||
|---|---|---|---|
|
||
| **P0–Critical** | Complete service outage or security incident | 15 minutes | 1 hour |
|
||
| **P1–High** | Major capability blocked with no available workaround | 1 hour | 3 hours |
|
||
| **P2–Medium** | Partial degradation or feature 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.** Mintlify engineering manages P0 incidents (complete service outage or security incident) directly. 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>
|
||
|
||
## FAQ
|
||
|
||
### Tier 3: Dedicated CSM
|
||
|
||
<AccordionGroup>
|
||
<Accordion title="What's the difference between a Dedicated CSM and Advanced Slack Support?">
|
||
Tiers 2 and 3 share the same response time targets. The difference is in how your issues reach our team:
|
||
|
||
- **Tier 2: Advanced Slack Support** uses an AI tool to automatically detect and route support messages from your Slack channel to our support inbox.
|
||
- **Tier 3: 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).
|
||
|
||
Tier 3 also includes monthly check-ins and a shared feature request tracker with direct product team access.
|
||
</Accordion>
|
||
|
||
<Accordion title="What's the difference between a Dedicated CSM and standard support?">
|
||
Tier 1 (Standard support, included with all Enterprise plans) is best-effort with no binding time target commitments. Tier 3 (Dedicated CSM) includes:
|
||
|
||
- **Defined response time targets** for initial response and resolution
|
||
- **Dedicated Slack channel** with an assigned CSM as your primary contact
|
||
- **Proactive engagement:** Monthly check-ins
|
||
- **Product influence:** Direct escalation to the product team and roadmap input
|
||
</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 during feature scoping. Your CSM reviews this regularly and escalates priority items directly to our product team.
|
||
</Accordion>
|
||
</AccordionGroup>
|
||
|
||
### Tier 2: Advanced Slack Support
|
||
|
||
<AccordionGroup>
|
||
<Accordion title="What's the difference between Advanced Slack Support and standard support?">
|
||
Tier 1 (Standard support, included with all Enterprise plans) is best-effort with no binding time target commitments. Tier 2 (Advanced Slack Support) includes:
|
||
|
||
- **Dedicated Slack channel** with AI-powered issue detection and automatic routing to our support inbox
|
||
- **Response time targets** for P0–P3 issues
|
||
- **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 we capture and triage your issues without requiring manual intervention.
|
||
</Accordion>
|
||
</AccordionGroup>
|
||
|
||
### Coverage hours
|
||
|
||
<AccordionGroup>
|
||
<Accordion title="What counts as a P0 incident?">
|
||
A P0 is a complete service outage or security incident affecting your Mintlify deployment. Mintlify determines P0 classification. We monitor our systems continuously and proactively open P0 incidents when our criteria match. 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.** Mintlify engineering covers and handles P0 incidents 24/7.
|
||
</Accordion>
|
||
</AccordionGroup>
|
||
|
||
## Get started
|
||
|
||
{/* vale Vale.Terms = NO */}
|
||
Contact your Mintlify account team to add Advanced Slack Support (Tier 2) or a Dedicated CSM (Tier 3), or email gtm@mintlify.com.
|
||
{/* vale Vale.Terms = YES */}
|