Add Enterprise Support Policy page#515
Conversation
Adds a customer-facing support policy page to enterprise docs covering: - Severity level definitions (Sev 1-4) - First response SLA for Standard and Premium support tiers - How to report issues via the Support Portal Content sourced from the internal RFC, filtered to include only customer-facing information per team guidance. Internal resolution targets, internal routing details, and ticket statuses are excluded.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
| <CardGroup cols={2}> | ||
| <Card title="Severity 1" icon="circle-exclamation" color="#dc2626"> | ||
| **Production Down** | ||
|
|
||
| Product is down or seriously impaired and there is no workaround currently | ||
| available. | ||
| </Card> | ||
| <Card title="Severity 2" icon="triangle-exclamation" color="#ea580c"> | ||
| **Reduced Capacity** | ||
|
|
||
| Customer's system is functioning but in a reduced capacity, and there is no | ||
| workaround currently available or the workaround is cumbersome to use. | ||
| </Card> | ||
| <Card title="Severity 3" icon="circle-info" color="#ca8a04"> | ||
| **Minor Impact** | ||
|
|
||
| Does not prevent normal operation of the Customer's system, or where the | ||
| situation may be temporarily circumvented using an available workaround. | ||
| </Card> | ||
| <Card title="Severity 4" icon="message-question" color="#16a34a"> | ||
| **General Request** | ||
|
|
||
| Non-critical errors or issues, including general questions and requests for | ||
| enhancements to the product. | ||
| </Card> | ||
| </CardGroup> |
There was a problem hiding this comment.
I would like to see these definitions tightened up a bit so that we have more consistency across reporters around how the same issue is classified. Let's try to use more objective statements such as we have in the current definitions.
For example "seriously impaired" is less specific and more subjective than saying "a vital feature is broken with no way to bypass it. Affects multiple teams or the entire company."
I would like a more severe sounding title for Sev 2 than "reduced capacity" otherwise I think we'll get more Sev 1 requests than we want. We previously had "major block" for this category. I am fine with alternatives but let's use something that sounds really bad.
We had decided to group minor issues with general requests or concerns as Sev 4. I am fine with that, but let's not use the term minor impact for Sev 3. It should sound worse than that. We previously called that "partial failure." We should describe the impact more crisply and objectively, for example: "system behavior is degraded, disrupting work but users are able to complete tasks."
|
|
||
| ### Standard Support | ||
|
|
||
| Included with every Enterprise deployment. Coverage is Monday–Friday during |
There was a problem hiding this comment.
Business hours, meaning what? What timezone? What hours?
|
@chrisnelson-design Thanks for the great start on this! |
3 participants
Summary
Adds a customer-facing Support Policy page to the Enterprise docs section at
docs.openhands.dev/enterprise/support-policy.What's included
docs.jsonChanges
enterprise/support-policy.mdxdocs.jsonenterprise/support-policyto Enterprise navThis PR was created by an AI agent (OpenHands) on behalf of Chris Nelson.
@chrisnelson-design can click here to continue refining the PR