Service levels for incident handling

1. An incident is a situation that negatively impacts the operation of the agreed services in the Agreement for Services (‘Incident').

2. Incidents can be reported at https://support.effectory.com/, directly at Effectory Helpdesk staff, or other Effectory employees.

3. An Incident involving personal data is handled according to data breach procedures agreed in the Data Processing Agreement.

4. Incidents (not involving personal data) are prioritized as follows:

Priority

Guideline

Resolution time

1 - Urgent

Effectory products or services are unusable.

ASAP, within 8 hours.

2 - High

Most users cannot use Effectory products and/or affected services are critical.

Within 1 work day (8 working hours).

3 – Medium

Some users cannot use Effectory products and/or affected services are non-critical.

Within 2 work day (16 working hours).

4 – Low

Few users cannot use Effectory products and/or affected services are supportive only.

Within 15 working days.

5. Resolution time counter starts after Effectory confirms the Incident and priority.

6. Effectory grants that 90% of Incidents are solved within indicated resolution times.

7. Examples to clarify prioritization of Incidents:

Priority 1 – Urgent:

  • All users cannot access Effectory applications.
  • All users cannot fill out survey questionnaires during response period.

Priority 2 – High:

  • Some users cannot fill out survey questionnaires during response period.
  • Feedback results cannot be accessed but should be able to.
  • Application crashes/ indefinite loops.
  • Incorrect function flow leading to unreliable feedback results.
  • One or several major functionalities cannot operate.

Priority 3 – Medium:

  • A single user cannot access feedback results but should be able to.
  • A single user cannot access Effectory system.
  • A single user gets application crashes/ indefinite loops.
  • Faulty or missing hints and error messages.
  • Missing validation rules for some questionnaire fields.
  • Wrong translations leading to functional mistakes.
  • Results do not seem to make sense, and requires investigation.

Priority 4 – Low:

  • User interface looks different than expected, but is functionally correct.
  • Poorly translated texts but still understandable.
  • Small problems which do not impair functionality.
  • Minor flaws in user interface styling.

Examples to clarify timelines of Incidents:

Priority

Confirmed on date, time

Resolution target date, time

1 – Urgent

Thursday 9 Jun, 11.00

Thursday 9 Jun, 19:00

1 – Urgent

Thursday 9 Jun, 21:00

Friday 10 Jun, 05:00

1 – Urgent

Saturday 9 Jun, 17:00

Sunday 10 Jun, 03:00

1 – High

Thursday 9 Jun, 11.45

Friday 10 Jun, 11:45

1 – High

Thursday 9 Jun, 21:15

Friday 10 Jun, 17:30

1 – High

Saturday 9 Jun, 15:15

Monday 11 Jun, 17:30

2 – Medium

Tuesday 5 Jun, 14:00

Thursday 7 Jun, 14:00

2 – Medium

Tuesday 5 Jun, 20:00

Thursday 7 Jun, 17:30

2 – Medium

Saturday 9 Jun, 14:00

Tuesday 12 Jun, 17:30

3 – Low

Monday 9 Jul, 10:05

Monday 30 Jul, 10:05

 

Was this article helpful?
3 out of 4 found this helpful

We're sorry to hear that!

Please tell us why.
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.