Replace new SLA with old version (codefresh-io#1249)

* Replace new SLA with old version

Replaced new with legacy SLA as customers still have the older categorization; as per Vidhya

* Update sla.md

_docs/terms-and-privacy-policy/new-sla-on-hold.md

@@ -0,0 +1,85 @@
+---
+title: "Service Commitment"
+description: ""
+group: terms-and-privacy-policy
+toc: true
+---
+
+
+## ERROR PRIORITIES AND RESPONSE TIMES.
+
+Issues with the Codefresh Platform are classified based on severity of the issues and the required resources needed to resolve them. We will designate the severity and impact of the reported issue as defined below and will use commercially reasonable efforts to respond and commence working on the applicable issue in accordance with the time periods below.  The following are our objectives (and - for Premium support customers - our commitment) to responding to your support requests. While we will make our best effort to help, we cannot guarantee any specific results, such as fixing or solving your problem, as this is dependent upon factors outside of our control including your particular software, infrastructure, configurations, and your ability to implement any rectification works such as installing updates or reconfiguring your environment and your own timeframes for doing so.
+
+For Premium support customers, we commit to meeting these objectives as our SLA for our supported products. Please note that if you have multiple products or subscriptions, you must purchase Premium support for all your products and subscriptions. 
+
+
+These objectives apply only to actual outages, bugs, errors, or defects, in our supported products when used in supported ways. If you report an unsupported issue - for example, the issue lies with an unsupported product (including out-of-date versions of otherwise supported products) or use of a supported product in an unsupported way - these objectives do not apply, but we may provide suggestions on how you can take your own independent steps to remedy your issue. 
+
+
+
+### 1.1. Response Time Objectives. 
+
+Our response may include:
+
+* an acknowledgment of receipt of your issue; 
+* a request for further information or assistance in order for us to implement or propose a remedy to your issue; 
+* implementation or proposal of a remedy for your issue; 
+* etc.
+
+The following timeframes are calculated from the time that we receive sufficient information from you in order to designate the severity and impact of the reported issue., through to the time of our response to your support request (or any follow-up reply). 
+
+{: .table .table-bordered .table-hover}
+
+| **Priority**  | **Professional**        | **Enterprise** | **Premium**  |
+|-----------|---------------------|-----------|----------|
+| **Urgent**    | 2 Business Hours[1] | 1 Hour    | 30 minutes |
+| **High**      | 6 Business Hours    | 2 Hours   | 1 Hour   |
+| **Normal**    | 1 Business Day[2]   | 4 Hours   | 2 Hours  |
+| **Low**       | None                | 2 Business Days | 8 Business Hours |
+
+[1] **Business Hours** means the hours of 9am to 5pm on Business Days in the registered time zone for your supported product.  
+[2] **Business Day** means weekdays (excluding public holidays) in your registered time zone.
+
+
+
+If our response time objective exceeds the remaining time available on that Business Day, our response time is paused at the end of the Business Day and shall resume on the next Business Day (where applicable). However, we may respond outside of these hours. 
+
+
+### 1.2. Priority Definitions.
+
+{: .table .table-bordered .table-hover}
+| **Priority Level** | **Description** |
+|--------------------|---------------|
+| **Urgent**  | A major service outage, e.g.: {::nomarkdown}<ul><li>Your Codefresh instance is completely unavailable or unable to deploy.</li><li> Your production use of our products for mission-critical systems has stopped or is so severely impacted that you cannot reasonably continue work.</li></ul>{:/} <br><br> Critical impact problems could have the following characteristics:{::nomarkdown}<ul><li>System hangs or crashes</li><li>Data loss or data corruption</li><li>Critical functionality not available</li><li>No reasonable workaround</li></ul>{:/} |
+| **High**  | Significant impairment to your ordinary usage, e.g.: {::nomarkdown}<ul><li>Disabled functionality, errors that result in a lack of significant functionality in the services which prevent you from accomplishing your deployments with no workaround provided.</li><li>Important product features are unavailable with no acceptable workaround. Your implementation or production use of our product in a primary business service, major application(s), or mission-critical system(s) are functioning with limited capability or are unstable with periodic interruptions. The product may be operating but is severely restricted.</li></ul>{:/} <br><br> High-impact problems could have the following characteristics: {::nomarkdown}<ul><li>Product error or failure forcing a restart or recovery.</li><li>Severely degraded performance</li><li>Functionality unavailable, but the system can operate in a restricted fashion.</li></ul>{:/} |
+| **Normal**  | Non-critical errors that do not significantly impair your ordinary usage, e.g.: {::nomarkdown}<ul><li>Errors that cause previously-working non-critical features to malfunction.</li><li>Product features are unavailable, but a workaround exists, and the majority of product functions are still usable. Minor function/feature failure that the customer can circumvent or avoid.</li><li>Your work has minor loss of operational functionality.</li> </ul>{:/}<br><br>Normal impact problems could have the following characteristics:{::nomarkdown}<ul><li>Error message with a workaround</li><li>Minimal performance degradation</li><li>Incorrect product behavior with a workaround</li></ul>{:/} |
+| **Low**  | Minor problem or question that does not affect product functionality, e.g.:{::nomarkdown}<ul><li>How-tos</li><li>Documentation</li><li>General questions</li><li>Enhancement requests</li></ul>{:/} <br><br> There is no or low impact on customer operations. <br><br> Low-impact problems could have the following characteristics:{::nomarkdown}<ul><li>General requests for advice on product usage</li><li>Questions on product functionality or configuration during implementation</li><li>Clarification on product documentation or release notes</li><li>Minor UI bugs</li><li> Nice-to-have product enhancement requests</li></ul>{:/}|
+
+
+### 1.3. Support Channels. 
+
+{: .table .table-bordered .table-hover}
+
+| **Channel**                          | **Professional**        | **Enterprise** | **Premium**  |
+|--------------------------------------|------------------------|---------------|-------------|
+| **Community Slack**                  | ✅                      | ✅            | ✅         |
+| **Support Email**                     |  ✅                     | ✅           | ✅         |
+| **Support Hours**                     | During Business Hours[1] | 24 x 7      | 24 x 7      |
+| **Primary Support Engineer**          |                        |               | ✅          |
+| **Video Conferencing***               |                        |               | ✅          |
+| **Phone****                           |                        |               | ✅          |
+| **Dedicated Support Slack Channel*****|                        |               | ✅          |
+| **SLA**                               |                        |               | ✅          |
+
+
+
+
+***Video Conferencing**: Real-time troubleshooting utilizing Microsoft Teams or Zoom. Available to Premium Support customers.
+
+****Phone**: An initial reply by our answering service who will open a support ticket immediately which will be prioritized accordingly. This does include the 'Live support'/co-piloting/on boarding features offered by our Professional Services.
+
+*****Dedicated Support Slack Channel**: For Low Priority requests only; not to be used for business-impacting issues.
+
+**Primary support engineer**: Your dedicated primary support engineer is your primary contact for any support issues. They have deep knowledge of Octopus, and knowledge of your infrastructure, business, and deployment needs. They work closely with our global support team and engineering teams in APAC to resolve your issues as quickly as possible.
+
+