# Case severity and initial response times

How quickly your support cases are addressed depends on the assigned severity. You assign the severity of the issue when you open the case. With your agreement, the support team adjusts the assigned severity if an incorrect severity level is selected. For more information about Support plans and pricing, see [Economy, Business, and First](/platform/pricing/support.md) Support plans.

The following table lists some common examples of support issues, suggested severity levels, and the initial response time objectives. The initial response time objectives are used to describe our goals only and don't represent a performance guarantee.

### Severity Level Definition

<table><thead><tr><th width="150">Severity</th><th width="150">Priority</th><th width="510.2">Details</th></tr></thead><tbody><tr><td>1</td><td>Critical</td><td>Represents a business-critical incident or scenarios like a complete loss of service or a significant feature that is completely unavailable, and no workaround exists.</td></tr><tr><td>2</td><td>Normal</td><td>Represents a non-business-critical incident and intermittent issues and reduced quality of service. A workaround may be available.</td></tr><tr><td>3</td><td>Low</td><td>Represents general service-related questions, feature requests, and other requests for information.</td></tr></tbody></table>

### Initial Response Time Objectives

Initial response time means the maximum time for a technical support team member to get back to the customer. Initial response time objectives do not apply to any billing, invoice, or sales-related inquiry or cases.

#### Economy Support Plan

<table><thead><tr><th width="150">Priority</th><th>Business Hours°</th><th>Non-Business Hours°¹</th></tr></thead><tbody><tr><td>Standard<br>(Best effort)</td><td>Usually response time<br>within 12 hours</td><td>Usually response time<br>within 48 hours</td></tr></tbody></table>

#### Business Support Plan

<table><thead><tr><th width="150">Priority</th><th>Business Hours°</th><th>Non-Business Hours°¹</th></tr></thead><tbody><tr><td>Critical</td><td>Within 2 hours</td><td>Within 4 hours</td></tr><tr><td>Normal</td><td>Within 4 hours</td><td>Within 12 hours</td></tr><tr><td>Low</td><td>Within 12 hours</td><td>Within 24 hours</td></tr></tbody></table>

#### First Support Plan

<table><thead><tr><th width="150">Priority</th><th>Business Hours°</th><th>Non-Business Hours°¹</th></tr></thead><tbody><tr><td>Critical</td><td>Within 30 minutes</td><td>Within 1 hour</td></tr><tr><td>Normal</td><td>Within 2 hours</td><td>Within 6 hours</td></tr><tr><td>Low</td><td>Within 6 hours</td><td>Within 12 hours</td></tr></tbody></table>

° Business Hours\
Monday till Friday, 08:00 - 18:00 CET/CEST (excl. Saturday, Sunday, and common holidays)\
\
°¹ Non-Business Hours\
Monday till Friday, 18:00 - 08:00 CET/CEST (incl. Saturday, Sunday, and common holidays)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.flow.swiss/platform/support/case-severity-and-initial-response-times.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.