INCIDENT PRIORITISATION Sample Clauses
INCIDENT PRIORITISATION. Client shall promptly, following discovery, notify Supplier of any Error via the Helpdesk and provide Supplier with reasonable detail of the nature and circumstances of the Error. Each Party shall categorise Errors as follows:
4.1. Urgent (P1) Priority Support Service Incidents means incidents that prevent the use of the Subscription Services including but not limited to an inability to log-in and critical loss of Data;
4.2. High (P2) Priority Support Service Incidents means incidents that need to be dealt with quickly but do not prevent the use of the Subscription Services, including but not limited to incidents that prevent the use of a product feature; and
4.3. Normal (P3) Priority Support Service Incidents means incidents that are not urgent which can be dealt with on a first come first served basis including but not limited to minor incidents that do not prevent use of a feature; and
4.4. Low (P4) Priority Support Service Incidents means incidents that are not urgent which can be dealt with on a first come first served basis including but not limited to cosmetic incidents that do not prevent use of a feature or function.
INCIDENT PRIORITISATION. Each Incident is given a priority of 1, 2 or 3 (“Priority”) based on the severity of the Incident and the Services being provided. Each Incident will be assigned an initial Priority by the Customer. This initial Priority will then be validated by Help Desk personnel who will notify Customer in the case of any proposed change of priority.
INCIDENT PRIORITISATION. Client shall promptly, following discovery, notify Supplier of any Error via the Helpdesk and provide Supplier with reasonable detail of the nature and circumstances of the Error. Each Party shall categorise Errors as follows:
