Skip to content

Add Enterprise Support Policy page#515

Draft
chrisnelson-design wants to merge 1 commit into
mainfrom
add-support-policy
Draft

Add Enterprise Support Policy page#515
chrisnelson-design wants to merge 1 commit into
mainfrom
add-support-policy

Conversation

@chrisnelson-design
Copy link
Copy Markdown

@chrisnelson-design chrisnelson-design commented May 20, 2026

Summary

Adds a customer-facing Support Policy page to the Enterprise docs section at docs.openhands.dev/enterprise/support-policy.

What's included

  • Severity Levels (Sev 1–4) — Definitions aligned internally, covering Production Down through General Request
  • First Response SLA — Standard (M–F business hours) and Premium (24/7 for Sev 1, M–F for Sev 2–4) response time commitments
  • How to Report an Issue — Directs customers to the Support Portal, with a note clarifying SLA times are first-response commitments, not resolution times
  • Navigation update — Adds the page to the Enterprise sidebar in docs.json

Changes

File Change
enterprise/support-policy.mdx New page (severity levels, SLA tables, reporting instructions)
docs.json Added enterprise/support-policy to Enterprise nav

This PR was created by an AI agent (OpenHands) on behalf of Chris Nelson.

@chrisnelson-design can click here to continue refining the PR

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.
@mintlify
Copy link
Copy Markdown

mintlify Bot commented May 20, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
all-hands-ai 🟢 Ready View Preview May 20, 2026, 8:22 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants