Service level agreement (SLA)

ERPoida · Document

An annex to a service contract: availability, support hours, response and resolution times by priority, maintenance windows and service credits.

Service Level Agreement

Provider: Service provider · Client: Client · Date: Date

This annex belongs to the service agreement between the parties and covers the service Service.

1. Availability

The Provider makes the service available Availability per month (%) % of each calendar month. Planned maintenance and events outside the Provider's control do not count as downtime.

2. Support

Support is available Support hours. Requests come in by email, phone, portal.

3. Response and resolution times

Priority Meaning First response Target resolution
1 Critical Service is down, no workaround 1 hour 4 hours
2 High Main function limited 4 hours 1 working day
3 Normal Minor problem, workaround exists 1 working day 5 working days
4 Low Question or wish 2 working days as planned

Times run only within the support hours.

4. Maintenance windows

Planned maintenance happens day, time and is announced number days ahead.

5. Service credits

If availability in a month is below the agreed value, the Client receives a credit on the next invoice: e.g. 5 % of the monthly fee per full percentage point missed, up to 25 %. The credit must be claimed in text form within 30 days.

6. Reporting and escalation

The Provider sends a monthly report on availability and tickets. Escalation: contact level 1, then contact level 2.

Provider Client
Place, date
Signature

This template is a starting point, not legal advice. Have it reviewed before use.

Need something we don’t have?

Describe it to the ERPoida assistant and build on the objects, fields and flows in your workspace. Or tell us what you need.