Support built for production.

Clear response goals, defined severity levels and direct access to the engineering team. No ticket queues. No runaround.

Premium Severity 1 response goal
6 hours
Premium coverage
24/7
Severity levels, each with a goal
4
Support language
English

Find your response goal.

Pick your subscription and how bad the issue is. See how fast we answer, when, and where to raise it.

Subscription

Severity

6 hours

Initial response goal for critical severity on Premium.

Severity 1: Production system down. No workaround available.

Hours
24×7×365
Raise it in
Email, Support portal, Slack Connect, Phone
Then
Contact Technical Support through the support portal right after you open the case, so the goal can be met.

Plans

CommunityFree
Hours
Community forums
Channels
GitHub Issues, Community Slack
Severity 1, critical
Best effort
Severity 2, high
Best effort
Severity 3, medium
Best effort
Severity 4, low
Best effort
StandardIncluded
Hours
Business hours, 9am to 6pm ET, Monday to Friday
Channels
Email, Support portal
Severity 1, critical
1 business day
Severity 2, high
3 business days
Severity 3, medium
5 business days
Severity 4, low
7 business days
PremiumAdd-on
Hours
24×7×365
Channels
Email, Support portal, Slack Connect, Phone
Severity 1, critical
6 hours
Severity 2, high
1 business day
Severity 3, medium
3 business days
Severity 4, low
5 business days

Critical

Production system down. No workaround available.

High

Major feature impaired. A workaround may exist but degrades operations.

Medium

Non-critical feature affected. Workaround available.

Low

General questions, feature requests, documentation issues.

Four severity levels, the most severe first. Every subscription sets an initial response goal for each one.

Customer obligations.

We need three things from you: detail on the issue, access to your environment, and help with the diagnosis.

Enable effective support

To enable hoop.dev to provide Support, you agree to: (i) provide reasonable detail of the nature of and circumstances surrounding the Issue or Error; (ii) provide reasonable access to your environment as necessary; and (iii) provide reasonable cooperation in the diagnosis and resolution of any Issues and Errors.

With your consent, hoop.dev may share information related to a particular support case with your other relevant service providers that are hoop.dev partners in order to troubleshoot and resolve the support case.

Critical severity protocol

You must contact hoop.dev Technical Support via the support portal immediately after opening a Severity Level 1 or Severity Level 2 support case to ensure the applicable Initial Response Goal is met.

severity     1, critical
issue        what fails, since when, what you see
environment  how we reach it
contact      who works the case with us

then contact Technical Support via the support portal
A case that covers all three points: the detail, the access and the person to work with. Severity 1 and 2 cases add the call to Technical Support.

Support limitations.

Support is only available in English. hoop.dev has no obligation to provide any Support to Customer in the following circumstances:

  • For any software, hardware, or other element of the Customer environment not provided by hoop.dev.
  • If Customer or a third party has altered or modified any portion of the Cloud Services.
  • If Customer has not used the Cloud Services in accordance with Documentation or instructions provided by hoop.dev, including failure to follow implementation procedures.
  • If Customer is running a version of the Cloud Services that has passed its end of life date.
  • For Beta Offerings.