Service Level Terms and Conditions

‍

Version 2.0. Effective date: 18 November 2026

These Service Level Terms and Conditions ("SL T&Cs") contain the provisions on availability, maintenance, support and response times for the Services. They form part of the SaaS Agreement between the Customer and bilabl Pte. Ltd. (UEN 202415315N) (the "Service Provider"). Capitalised terms that are not defined here have the meanings given in the General Terms and Conditions.

‍

1. Subject Matter


The SL T&Cs apply to the Services provided by the Service Provider under the SaaS Agreement. The Service Provider will use reasonable efforts to operate a secure and available bilabl Network in order to give the Customer and its Service Users access to the Services. The SL T&Cs also set out the Customer's sole remedy if the Service Level Target below is not met.

‍

2. Service Availability Commitment


2.1 Definitions

"Business Days" means Monday to Friday, excluding public holidays in Singapore.

"Downtime" means the total number of minutes in a calendar month during which the Services are unavailable to all of the Customer's Service Users, as confirmed by the Service Provider's monitoring records, excluding Scheduled Maintenance and the events listed in Section 2.3.

"Scheduled Maintenance" means planned or emergency maintenance or service procedures that may limit or disrupt access to the Services, as described in Section 4.1.

"Service Availability" means the percentage of time in a calendar month during which the Services are available, calculated as: (total minutes in the month, less Scheduled Maintenance, less Downtime) divided by (total minutes in the month, less Scheduled Maintenance), multiplied by 100.

"Service Level Credit" means a credit applied against a future invoice of the Customer after the Service Provider has confirmed a Service Level Failure.

"Service Level Target" means the target for Service Availability stated in Section 2.2.

2.2 Service Level Target and Credits

The Service Level Target for Service Availability is 99.9% in each calendar month.

If the Service Provider confirms that it did not meet the Service Level Target in a calendar month (a "Service Level Failure"), the Service Provider will:

  1. investigate the underlying causes of the Service Level Failure;
  2. take the steps it considers appropriate to prevent the failure from recurring. If those steps include activities that the Customer or its vendors must carry out, the Customer will complete them or use reasonable efforts to ensure that its vendors complete them; and
  3. give the Customer, on a valid claim under Section 2.4, a Service Level Credit equal to the percentage in the table below, multiplied by the Subscription Fees attributable to that month (calculated pro rata on a straight line basis where Subscription Fees are paid in advance).
Service Level Credit Percentage
Equal to or greater than 99.5% but less than 99.9% 10%
Equal to or greater than 99% but less than 99.5% 20%
Less than 99% 30%

‍

The Service Level Credits for any calendar month will not exceed 30% of the Subscription Fees attributable to that month. Service Level Credits have no cash value, are not refundable and may only be applied against future invoices for the Services. The Service Level Credit is the Customer's sole and exclusive remedy for any Service Level Failure and for any other unavailability or performance failure of the Services, as stated in Section 9.8 of the General Terms and Conditions.

2.3 Exclusions

The Service Provider is not responsible for, and Downtime does not include, any unavailability or failure to meet the Service Level Target to the extent that it is caused or contributed to by:

  1. a reduction of service or resources directed or approved by the Customer;
  2. outages or reduced performance of any Customer Equipment, Customer Systems or Customer Managed Storage Location, or of the Customer's Internet connection;
  3. errors or defects caused by any modification, revision or alteration of software that was not made by the Service Provider;
  4. an act or omission of the Customer, its Affiliates, its Service Users, or the Customer's vendors, third party providers or agents, including use of the Services in breach of the SaaS Agreement or contrary to the Documentation;
  5. a Third Party Application, an AI feature or optional module provided by a third party, or any other third party service that is not operated by the Service Provider;
  6. Internet or telecommunications failures outside the bilabl Network;
  7. a Force Majeure Event;
  8. Scheduled Maintenance;
  9. a suspension of the Services that is permitted by the General Terms and Conditions; or
  10. any Free Access Period, trial, or feature identified as beta, preview or early access.

2.4 Claim Procedure

To receive a Service Level Credit, the Customer must:

  1. open a support ticket reporting the unavailability within five (5) Business Days after the end of the service interruption;
  2. have no invoice that is overdue; and
  3. provide in the ticket, within the same five (5) Business Days: the functional areas of the Services that were affected; the date and time the Downtime occurred; the user names and email addresses of the Service Users affected; and an estimate of the Downtime in minutes.

If the Customer does not meet these requirements, it is not entitled to a Service Level Credit for that Service Level Failure. The Service Provider's monitoring records are the basis for confirming any Service Level Failure.

‍

3. Support

3.1 Scope

Support gives the Customer and its Service Users technical support, training and help with the Services.

Support covers:

  1. service interruptions and outages;
  2. service updates and maintenance;
  3. behaviour of the Services that is not in line with the Documentation; and
  4. questions about functionality.

Support does not cover:

  1. requests from the Customer's or its Service Users' third party providers;
  2. networks, devices, servers and workstations managed by the Customer or its Service Users; or
  3. requests for configuration or customisation of the Services beyond the scope in the Order Form, which are handled as Professional Services.

When the Customer or a Service User asks for Support that requires access to Customer Data, the request is an instruction to the Service Provider under Section 6.4.2 of the General Terms and Conditions.

3.2 Channels and Support Hours

Support is available through the support channel inside the Services, by email to support@bilabl.io, and through the contact details stated in the Order Form.

Support is provided in English on Business Days from 9:00 a.m. to 6:00 p.m. Singapore time ("Support Hours"). Customers in other regions may contact their account manager or the support team about regional support hours.

3.3 Priorities and Target Response Times

The response time is the time from when the Customer enters a request in the Service Provider's ticketing system, or the Service Provider receives the Customer's email, until the Service Provider replies and starts working on the request. Response times are counted within Support Hours. The Service Provider assigns the priority when it evaluates the request.

Priority Description Response Time
High Core functions unavailable (e.g., login not possible, critical uploads fail) 4 hours
Medium Service impaired but basic functionality available (e.g., reporting issues, calculation errors) 8 hours
Low Minor issues not affecting results (e.g., performance lag, display issues) 16 hours

‍

The response times above are targets that the Service Provider will use reasonable efforts to meet. They are not guarantees of a response or resolution within any particular time, and a failure to meet them is not a Service Level Failure and does not give rise to a Service Level Credit or any other remedy.

‍

4. Maintenance, Backup and Incidents


4.1 Scheduled Maintenance.
The Service Provider may carry out maintenance of the Services from time to time. The Service Provider will notify the Customer in advance of planned maintenance that is expected to disrupt access to the Services. Emergency maintenance needed to protect the security, integrity or stability of the Services may be carried out at any time, with such notice as is reasonably practicable.

4.2 Backup and Recovery. The Service Provider performs automated backups as described in the Security Protocols and Infrastructure. The Service Provider does not guarantee that the Services or any Customer Data can be restored within any particular time or to any particular point in time. Export of Customer Data is governed by Section 7.4 of the General Terms and Conditions.

4.3 Security Incidents. Notification of data breaches affecting Customer Data is governed by Section 6.4.5 of the General Terms and Conditions.

‍

5. General

‍
5.1
The SL T&Cs may be updated in accordance with Section 10.7 of the General Terms and Conditions.

5.2 If the SL T&Cs conflict with the Order Form or the General Terms and Conditions, the order of precedence in Section 10.15 of the General Terms and Conditions applies.

5.3 The SL T&Cs are governed by the laws of Singapore, and disputes are resolved as set out in Sections 10.9 and 10.10 of the General Terms and Conditions.

‍

Want to learn more?
Book a demo with our experts today. Discover how bilabl can help your team in 40 minutes.
See the product. Ask any question.
Learn how our solution will save you time and money