Service level agreement (SLA)
This is an English translation provided for convenience. If it differs from the Arabic version, the Arabic version governs.
Introduction
This Agreement sets out the operational service levels that Smart Voice Communications and Information Technology Company (the “Company” or “Hatif”) undertakes to make reasonable efforts to achieve when providing its services, including service availability indicators, technical support mechanisms, response and restoration times, incident and maintenance management, and the mechanism for calculating service credit (when it is due), in accordance with the provisions of this Agreement.
This Agreement forms an integral part of the Service Agreement and Terms and Conditions and the Privacy Policy, and is to be read and interpreted together with them as a single whole.
In the event of any conflict:
1. The provisions of the Privacy Policy prevail with respect to the processing of personal data.
2. The provisions of the Service Agreement and Terms and Conditions prevail with respect to contractual and commercial matters.
3. This Agreement is limited to setting the operational performance levels of the service.
Article 1: Definitions
For the purposes of this Agreement, the words and expressions used in it have the meanings set out in the Service Agreement and Terms and Conditions, unless the context requires otherwise, and the following terms have the meanings below:
1. Service Availability: the percentage of time during which the core services are available for use.
2. Incident: any fault or failure that affects the operation of the service or causes its performance to degrade or the service to stop.
3. Ticket: a request for technical support, or a report of a failure or fault, submitted by the Customer through the approved channels.
4. Response Time: the time between receipt of the ticket and the start of its handling by the technical support team.
5. Restoration Time: the time needed to return the service to normal operation or to provide a temporary workaround.
6. Resolution Time: the target time for resolving the ticket or providing a suitable solution or alternative, depending on the nature of the problem.
7. Scheduled Maintenance: technical work planned in advance, of which customers are notified, to improve the performance of the service or update it in accordance with this Agreement.
8. Emergency Maintenance: maintenance work that requires immediate intervention to preserve the security or stability of the platform or to address serious failures.
9. Business Hours: the period during which the technical support team provides its regular services, as announced by the Company on the platform or through the approved channels. Business Hours may be amended from time to time, with notice to customers through the approved means.
10. Service Credit: a non-cash credit that the Company grants when the eligibility conditions set out in this Agreement are met, which is added to the Customer’s account to be used to pay future service fees, and which may not be refunded in cash, transferred to others, or claimed for its monetary value.
Article 2: Scope of the Agreement
This Agreement applies to the cloud services provided by the Hatif platform under the plan to which the Customer subscribes. This Agreement does not cover:
1. Trial services.
2. Services provided independently by third-party providers.
3. Failures caused by the Customer’s devices, network or internet connection.
4. Failures caused by the Customer’s misuse of the service.
5. The excluded cases set out in this Agreement or in the Service Agreement and Terms and Conditions.
Article 3: Term of the Agreement
This Agreement comes into force on the date the Customer’s subscription is activated, remains in effect throughout the subscription term, and ends when the subscription expires or is terminated, without prejudice to the rights and obligations that by their nature survive termination, including the obligations relating to confidentiality of information, data protection, fees due and the data retention provisions.
Article 4: Service availability level
Hatif undertakes to exercise reasonable professional care to provide the service at a target monthly availability of not less than (99.5%). The following cases are not included in the calculation of availability:
1. Scheduled maintenance, notified whenever possible.
2. Emergency maintenance needed to protect the platform or its stability.
3. Failures caused by providers of communications, internet or cloud services, or by any third party.
4. Failures caused by the Customer’s devices, network or internal systems.
5. Service interruption due to the Customer’s breach of the terms and conditions or misuse of the platform.
6. Force majeure or circumstances beyond control.
The availability percentage referred to above is not an absolute guarantee that the service will continue without interruption. It represents the target operational level that the Company seeks to achieve in accordance with best technical practice. Monthly availability means the percentage of time during which the core services are available for use during the calendar month, after excluding the excluded downtime periods set out in this Agreement, and it is calculated according to the formula adopted by Hatif on the basis of its technical monitoring records and systems.
Article 5: Maintenance
1. Scheduled maintenance: Hatif may carry out periodic maintenance, updates or improvements to the platform, and may, whenever possible, notify the Customer in advance before carrying them out, taking care to choose the times with the least impact on use of the service.
2. Emergency maintenance: the Company may carry out urgent maintenance without prior notice where necessary to preserve the security of the platform, protect customers’ data, or address serious failures that may affect the stability of the service.
Article 6: Technical support
1. The platform operates twenty-four (24) hours a day, seven (7) days a week, except during periods of scheduled or emergency maintenance and the cases excluded under this Agreement.
2. Technical support is provided during the Business Hours announced on the platform or through the approved channels, through the following:
a. The ticketing system.
b. Email.
c. Live chat.
d. Phone support.
3. The Company may provide emergency support outside official Business Hours according to the contracted plan or as announced by the Company.
4. Technical support services do not include software development, custom configurations, training, technical consulting, solution redesign or custom integrations, unless these are agreed under a separate agreement or price quotation.
Article 7: Incident classification
The Company classifies technical tickets according to the degree of their impact on the service, and this determines the priority of their handling and the target response and resolution times, as follows:
First: Ticket classification
| Priority | Description | Examples |
|---|---|---|
| P1 Critical | A failure that causes a complete outage of the service or a breakdown of one of the core functions, preventing the Customer from using the service entirely, with no temporary workaround available. | The whole platform is down, all incoming and outgoing calls have stopped, or all users are unable to log in. |
| P2 High | A failure that materially affects one of the main functions of the service, while the rest of the platform’s functions remain usable. | One of the digital channels has stopped, or the main application programming interface (API) has failed. |
| P3 Medium | A failure of limited impact, or one that affects a limited number of users or a non-core function, while the service as a whole remains usable. | The call recording service has failed, reports are slow, some settings have failed, or intermittent error messages appear. |
| P4 Low | User inquiries, requests for help, development or improvement requests, or failures that do not affect the operation of the service. | A request to explain a feature, a development suggestion, a change to account settings, or a technical inquiry. |
Second: Target response and resolution times
| Priority level | Initial response time | Target resolution time |
|---|---|---|
| P1 Critical | Within one hour | Continuous work until the service is restored or a temporary workaround is provided as soon as possible. |
| P2 High | Within four (4) business hours | Within two business days where possible, or a suitable workaround is provided until the root cause is addressed. |
| P3 Medium | Within one business day | Within five (5) business days, or in the first suitable update or release, depending on the nature of the failure. |
| P4 Low | Within two business days | According to the Company’s technical support plan or approved development schedule, depending on the nature of the request or inquiry. |
Third: Rules for calculating response and resolution times
1. Response time is calculated from the date and time the ticket is received through one of the approved technical support channels.
2. Response time means the time needed to begin handling the ticket and to contact the Customer. It does not mean that the ticket has been resolved or closed.
3. Target resolution time means the time within which the Company aims to resolve the ticket or provide a suitable workaround. It is an operational indicator and does not constitute an obligation guaranteeing that all tickets will be closed within the specified time.
4. Resolution times do not include periods resulting from:
a. Delay by the Customer in providing the Company with the information or data needed to resolve the ticket.
b. Failures or outages attributable to providers of communications, internet or cloud services, or to any third party.
c. Force majeure or circumstances beyond the Company’s reasonable control.
5. The Company may reclassify a ticket if, after examination, its degree of impact turns out to differ from the initial classification, and will notify the Customer of this where appropriate.
6. The resolution times referred to above are operational targets and do not constitute an obligation guaranteeing that all failures will be fixed within the specified times if the cause of the failure is outside the Company’s control, is linked to a third party, or requires substantial technical updates.
Article 8: Escalation procedure
The Customer may request escalation of a ticket when the target response or resolution times set out in this Agreement are exceeded. Escalation is made through Hatif’s approved channels, according to the following escalation levels:
| Escalation level | Responsible party | When to escalate | Contact method |
|---|---|---|---|
| Level 1 | Technical Support Supervisor | If there is no response to the ticket within one hour after the target response time ends for critical tickets (P1), or within four (4) business hours for high-priority tickets (P2). | Phone: 920018278 Email: support@hatif.io |
| Level 2 | Technical Support Manager | If the ticket continues without material progress or without the service being restored within four (4) hours of the first escalation for critical tickets (P1), or within two business days for high-priority tickets (P2). | Name: Talal Alrafei Mobile: 966553305649 Email: Talal@hatif.io |
| Level 3 | Head of Information Technology | If the outage continues for critical tickets (P1) after the second escalation, or if the incident is found to affect the continuity of the service or a large number of customers. | Name: Yousef Alkhalifah Mobile: 966566777416 Email: yousef@hatif.io |
| Level 4 | Chief Executive Officer | If the outage continues for critical tickets (P1) after the third escalation. | Name: Muath Alkhulaifi Mobile: 966551587621 Email: muath@hatif.io |
Escalating a ticket does not change the response or resolution times or give rise to any additional service credit. The purpose of escalation is to raise the level of administrative and technical follow-up, to ensure that the ticket is handled quickly and that appropriate action is taken.
Hatif reserves the right to change the escalation levels, the parties and officers responsible for them, or their contact channels, according to its organizational structure or operational requirements, provided that any update is announced on the platform or through the approved channels, and without this affecting the service levels set out in this Agreement.
Article 9: Customer obligations
The Customer undertakes to:
1. Provide a clear description of the failure.
2. Provide the support team with the information requested.
3. Cooperate with the support team during diagnosis.
4. Not make changes that could hinder the resolution of the ticket.
5. Provide a suitable internet connection for using the service.
The Company may suspend the handling of a ticket if the Customer does not respond to the support team’s requests within a reasonable time.
Article 10: Incident management
When an incident with an impact on the service occurs, Hatif undertakes to:
1. Log the incident.
2. Classify it by priority level.
3. Begin resolving it.
4. Update the Customer on its status where appropriate.
5. Close the ticket after the service is restored or a suitable workaround is provided.
Hatif may classify certain tickets as security incidents where they are found to have a potential impact on the security of systems, the integrity of data or the continuity of the service. In such cases, it may take preventive measures, or restrict or temporarily suspend certain services, to the extent necessary to address the risks, notifying affected customers whenever possible and without prejudice to legal obligations. The Company may also merge multiple tickets relating to the same failure into a single ticket for follow-up and resolution purposes, without this affecting the ticket’s priority or the Customer’s rights.
Article 11: Service credit
If the monthly availability of the service falls for reasons within Hatif’s responsibility, the Customer may request a service credit to be added to its account, according to the following table:
| Monthly availability | Service credit |
|---|---|
| Below 99.5% and down to 99% | 5% of the monthly subscription fee |
| Below 99% and down to 98% | 10% of the monthly subscription fee |
| Below 98% | 15% of the monthly subscription fee |
To be eligible for a service credit:
a. The subscription must be active.
b. The Customer must submit its request within thirty (30) days of the end of the month to which the claim relates.
c. Hatif’s records must prove that the outage occurred.
d. The cause of the outage must not be one of the excluded cases.
The total service credit due for any month may not exceed the monthly subscription fee for the month to which the claim relates. The Customer’s right, when a service credit is due, is limited to receiving a service credit in accordance with the provisions of this Agreement, and this gives rise to no right to claim cash compensation, compensation for loss of profit, indirect or consequential damages, or any other claims.
The Customer is entitled to a service credit only if the drop in the service level results directly from a breach by Hatif of its obligations set out in this Agreement. Eligibility and the value of the service credit are determined on the basis of the records and technical monitoring systems adopted by Hatif, as the technical reference for calculating availability percentages and outage durations, unless the Customer proves otherwise with credible technical evidence.
No more than one service credit may be claimed for the same event, and the service credit, once due, is the exclusive compensation for that event. The Customer may not claim any other compensation or consideration arising from that event, without prejudice to any rights established by applicable laws that may not be waived by agreement.
Granting a service credit does not constitute an admission by Hatif of a contractual breach or of legal liability beyond what is set out in this Agreement. Its effect is limited to addressing the drop in the service level according to the mechanism set out in this Agreement.
The Customer may not make any set-off or deduction against, or suspend payment of, the fees due on the basis of its claim for a service credit, unless Hatif agrees to this.
In this Agreement, a month means a calendar month, unless the plan or subscription provides otherwise.
Article 12: Performance measurement and service monitoring
1. Hatif relies on automated monitoring and operations systems to measure the availability of the services, track the performance of the platform and detect failures.
2. The technical records produced by Hatif’s monitoring systems are the primary reference for calculating availability percentages and outage times, unless a material or technical error that affects them is proven.
3. Measurement results obtained by the Customer using third-party tools or software may differ from the measurement results adopted by Hatif, and this does not in itself give rise to any compensation or mean that the service is deemed unavailable.
4. Hatif retains the technical records relating to service level measurement for a reasonable period in accordance with its internal policies, and these records may be referred to in order to verify any claim for a service credit.
Article 13: Exclusions
Hatif bears no responsibility for failing to achieve the service levels if this results from:
1. Force majeure.
2. Failures of communications providers.
3. Failures of third-party service providers.
4. Internet outages on the Customer’s side.
5. Errors in the Customer’s configuration.
6. Misuse of the service.
7. The Customer’s updates to its own systems.
8. Decisions of regulatory or judicial authorities.
9. Suspension of the service due to the Customer’s breach of the Agreement.
Article 14: Information security
Hatif undertakes to apply appropriate technical and organizational controls to protect the services, in line with the Privacy Policy and the relevant laws.
This Agreement is not a substitute for the Privacy Policy. Hatif makes reasonable technical and organizational efforts to maintain the security and continuity of the services. However, this Agreement does not constitute a guarantee that no security incident or cyberattack will occur, where the Company has taken appropriate security measures that comply with the relevant laws and regulations.
Article 15: External services and dependencies
Some of the platform’s services depend on third-party service providers, including communications providers, internet service providers, cloud computing services, WhatsApp Business services, electronic payment gateways and other supporting technical services. Periods of downtime, outage or delay caused by those parties are not included in the calculation of the service level where the cause of the outage is beyond Hatif’s reasonable control.
Article 16: Data retention after the service ends
Hatif retains the Customer’s data throughout the subscription term. When the subscription expires or is terminated, Hatif is not obliged to hand over the data to the Customer or enable the Customer to retrieve it, except on the basis of an order or decision issued by a judicial authority or a competent official authority. After the subscription ends, Hatif may retain the data or delete it from its operational systems in accordance with the Privacy Policy and the laws and regulations in force in the Kingdom of Saudi Arabia, without prejudice to any legal obligation that requires certain data to be retained for a specified period.
Article 17: Backup and disaster recovery
Hatif applies backup and disaster recovery procedures in accordance with its internal operational policies, in a way that achieves business continuity and data protection. This does not constitute a guarantee that all data can be restored in all cases, particularly where its loss results from the Customer deleting it or from causes beyond the Company’s reasonable control.
Article 18: Order of precedence of documents
The order of precedence of the documents is as follows:
1. The laws and regulations in force in the Kingdom of Saudi Arabia.
2. The Service Agreement and Terms and Conditions, with respect to contractual and commercial provisions.
3. The Privacy Policy, with respect to the processing of personal data.
4. The Service Level Agreement (SLA), with respect to operational service levels, without prejudice to the provisions of the documents with higher precedence.
Article 19: Review of service levels
Hatif may review the performance indicators or update this Agreement when operationally or legally necessary, and customers are notified of the amendments through the approved channels before they take effect, where required. Hatif reserves the right to review the performance indicators, availability percentages or technical support mechanisms whenever operational, regulatory or technical requirements so require, provided that customers are notified before any material amendment takes effect, in accordance with the Service Agreement and Terms and Conditions.
Article 20: Notices
All notices and claims relating to this Agreement are made through Hatif’s approved channels, including the email address registered in the Customer’s account, the platform, or the technical support system. Notices take effect from the date they are sent through those means, and the Customer undertakes to keep its contact details up to date.
Article 21: Final provisions
This Agreement takes effect from the date of its publication or from the date it comes into force for the Customer’s subscription, as the case may be, and remains in force throughout the subscription term.
Smart Voice Communications and Information Technology Company hatif.io