Legal

    Support Policy & Service Levels

    How to request support and our target response times.

    Back to Home

    This Support Policy & Service Levels document applies to all customers of FireCheckr, provided by Factor Technologies Ltd, where referenced in an Order Form or the General Terms.

    1. Scope

    This document describes:

    • how customers can request support for FireCheckr; and
    • our target response and update times for support requests.

    This document does not apply to:

    • professional services (including onboarding, training, implementation, or advisory services), which are governed by the relevant Order Form or statement of work; or
    • issues caused by customer systems, customer network/connectivity, or third-party services outside our reasonable control.

    2. Support Channels

    Support requests must be submitted via:

    • Email (Severity 2–4): support@firecheckr.co.uk
    • Phone (Severity 1 only): Customer administrators may call our provided support phone number for Severity 1 incidents only.

    3. Severity Levels (Classification)

    We classify support requests into the following severities using reasonable judgment. If a customer proposes a severity, we will take it into account, but the final severity classification is determined by us and may be adjusted as information changes.

    Severity 1 (Critical Incident)

    A critical incident that prevents the customer from progressing core work in FireCheckr for most users, for example where FireCheckr is unavailable or core workflows required to perform on-site work are not usable (such as capturing notes, drafting reports, or validating reports), and there is no reasonable workaround. A security emergency involving confirmed or strongly suspected unauthorised access to customer data, or a confirmed major data integrity issue, may also be treated as Severity 1.

    Severity 2 (Major Degradation)

    FireCheckr is available but a core workflow is severely degraded for a significant number of users, with no reasonable workaround.

    Severity 3 (Minor Issue / Limited Impact)

    Non-critical functionality is impaired, there is a workable workaround, or the impact is limited to a small number of users.

    Severity 4 (General Question / Request)

    How-to questions, configuration guidance, feature requests, or minor cosmetic issues.

    4. Support Hours

    Business Hours means 09:00 to 17:30 UK time, Monday to Friday, excluding UK public holidays. A Business Day is any day on which Business Hours apply.

    Support is available during the following hours:

    • Severity 1: 24 hours a day, 7 days a week (via the emergency channel in Section 2 for customer administrators)
    • Severity 2–4: Business Hours

    5. Service Level Targets (Response & Updates)

    The following are target response and update times. These are targets, not guarantees, and exclude time spent waiting for customer responses, third-party dependencies, or circumstances outside our reasonable control.

    When targets start. The service level targets below apply once we have received sufficient information to begin triage. If key information is missing, we will request it and the targets apply once that information is provided.

    Initial response means acknowledgement of the request, initial triage, and either initial diagnosis, a request for further information, or immediate mitigation steps.

    SeverityInitial Response TargetUpdate Cadence Target
    Severity 11 hourEvery 4 hours until mitigated
    Severity 24 business hoursDaily (business days)
    Severity 31 business dayWeekly (business days)
    Severity 43 business daysAs agreed / as needed

    Workaround means an alternative method that enables the customer to continue the relevant core workflow without unreasonable burden.

    Mitigated means the service is restored or a reasonable workaround has been provided.

    6. Information Customers Should Provide

    To help us resolve issues efficiently, customers should include:

    • customer name and workspace/tenant identifier (if applicable);
    • a description of the issue and business impact;
    • steps to reproduce (if relevant);
    • screenshots and timestamps (if available);
    • the names/email addresses of affected users (if relevant); and
    • device/browser details (if relevant).

    7. Escalation

    If a customer believes an issue is not being handled in line with the service level targets above, the customer may escalate by replying to the open support request with "Escalation requested" and a short summary of the impact. We will acknowledge escalation requests within one business day.

    8. Exclusions and Limitations

    The service level targets in this document do not apply, or may be affected, where the issue is caused by or relates to:

    • customer networks, devices, browsers, identity providers, or configurations;
    • customer misuse of FireCheckr, or use contrary to the Agreement or Documentation;
    • third-party services or outages outside our reasonable control (including telecoms or internet backbone issues);
    • scheduled maintenance notified in advance where reasonably practicable, or emergency maintenance to address security or stability issues;
    • beta/preview features labelled as such (unless stated otherwise in an Order Form); or
    • issues that require access that the customer does not provide (for example, where access is needed to reproduce or diagnose the issue).

    9. Maintenance and Emergency Work

    We may perform scheduled maintenance to improve or maintain FireCheckr. Where reasonably practicable, we will provide advance notice of scheduled maintenance. Emergency maintenance may be required to address security risks, stability issues, or urgent defects; we will provide notice where reasonably practicable.

    10. Security Incidents and Data Protection

    Security incidents involving customer data are handled in accordance with the Agreement and Data Processing Agreement (where applicable). Severity 1 security incidents are handled under the Severity 1 targets in this document.

    11. Changes to This Document

    We may update this Support Policy & Service Levels document from time to time. Updates will take effect in accordance with the change mechanism set out in the General Terms.