Service Level Agreement


This Service Level Agreement (SLA) specifies the time frames in which we will endeavor to respond to incidents and resolve any telephone system issues.
Included in this SLA is the incident procedure, associated response level and escalation process.
Astricloud are committed to delivering a high level of service to ensure that the telephone system is an effective enabling tool for all of our customers.

Service Description

Astricloud is responsible for maintaining the Telephone System and directly associated service used for the company specified as detailed on the Sales Order. This is to ensure that the telephony service (“the service”) is available for use in accordance with the service levels described in this agreement.

Service Availability

Astricloud will endeavor to ensure that the service is available 24 x 7 subject to planned outages as communicated by ASTRICLOUD, which in many cases will be determined by third party providers.

Scope of Service Support and Exclusion

4.1          Hours of Support

The Focus Support Desk is available between 09:00 and 17:30, Monday to Friday (excluding Public Holidays).

4.2          Service Schedule

  • 4.2.1.     Precise details of what is covered should be clear on the Sales Order form, but as a general rule we will usually cover the following
  • Router giving access to telephony cloud (provided router assurance is maintained)
  • Handsets or soft clients
  • Any wireless access points provided as a part of the service
  • Data connection
  • Fixed lines obtained from AstriCloud
  • Software
  • PCs or Servers

4.3          The following services and devices are not covered by this SLA or any service schedule

  • 4.3.1.     Customers IT Services, including infrastructure, hardware and software
  • 4.3.2.     Network switches used for the telephony service
  • 4.3.3.     DECT phones
  • 4.3.4.     Internal cabling
  • 4.3.5.     Mains cabling and supply
  • 4.3.6.     Headsets


The customer is responsible for the following:

  1. Providing a valid service identifier such as site name, address or telephone number when reporting an incident to the Support team.
  2. Provide and maintain a list of authorized technical representatives who can act on behalf of the customer, and be contacted either by Focus Support or a third party appointed by ASTRICLOUD.
  3. Checking that equipment is cabled and powered correctly, including phones, routers etc.
  4. Completing diagnostic checks when requested by a Astricloud representative.
  5. Confirmation that the incident reported has been resolved.

Astricloud is responsible for the following:

  1. Support provided via telephone and email.
  2. Issuing a unique reference number for each new incident raised.
  3. Monitoring each incident through to completion.
  4. Providing updates on the status/progress as agreed with the customer.
  5. Escalation as appropriate.
  6. Confirming when an incident has been resolved.

Incident Management

All incidents relating to the service detected by end users must be reported to the Focus Support team for further diagnosis. The Support team member will log a task on our in-house CRM System. The call will then be routed to the appropriate Support Technician in accordance with the minimum Service Level timelines.Within the SLA defined working hours:

  • The Support team will receive an email/telephone call of any incidents relating to the telephony system.
  • The Support team will log the incident with the customer contact as the “requester” and provide you a Case ID.
  • Each call logged by the Support team is assigned a unique Case ID. This Case ID number will be communicated to the requester and should be used when contacting the Support team for updates.
  • The Support team will assess the issue and engage the various technical representatives to assist and diagnose.
  • The customer contact will receive regular email (in some cases,voice call) updates in accordance with the category assigned to the task.
  • When the incident is resolved, changes completed, and/or the questions answered, the customer will be further updated and Astricloud will request acceptance to close the ticket. Astricloud will make a maximum of 2 closure requests within a period of 2 days after we believe the incident has been resolved. The ticket will then be closed unless anything further is heard from the customer in that time.

Service Levels

Astricloud prioritizes all requests according to their impact and urgency to ensure that appropriate response times to the incident service requests it receives are easily identifiable. Incidents with a large impact or problems that prevent a section of a business from performing its work completely are given a higher priority than other incidents or requests, for example, those affecting a single individual or affecting a less important function.

The following priorities are for incidents and service requests which cannot be immediately resolved.

Note: the status of any call can be obtained by contacting the Support team and providing the relevant task number. You will, however, receive periodic updates on any tasks raised.Astricloud will look to agree the priority level with the customer to avoid confusion or differing expectations.

In some cases, the incident may take longer to resolve than desired and Astricloud will endeavor to ensure that customers are informed of the incident status. In all cases, the Support team will notify the customer (or agreed representative) when the issue has been resolved and will only close the call when the customer has agreed to do so, or a request to close has not been responded as mentioned above.

Priority 1 – Incidents where there is a total system failure or failure of a component that renders the complete system unusable in one or more sites. (Class = Major Incident)

Priority 2 – Incidents that reduce the level of functionality or performance of the system across 1 or more sites. (Class = Significant Incident)

Priority 3 – Incidents that affect a single user or component that has a limited effect on the rest of the system. No disruption to service. (Class = Minor Incident)

Priority 4 –Service requests for configuration changes or a loss of functionality that is not service affecting. No disruption to service. (Class = Information request or config. change)

Incident Management Responses

All times are working hours/days

  P1 P2 P3 P4
Initial response time 30 Mins 30 Mins 60 Mins 60 Mins
Frequency of updates 2 Hours 2 Hours 4 Hours 2 Days
Target Fix Time 8 Hours 2 Days 3 Days 5 Days

Escalation Path

If you feel that a fault is not being progressed within the given timescales or is not receiving the appropriate attention or priority, please feel free to contact Focus Escalation team below; quote the relevant ticket number and state the reasons to why you believe the ticket should be escalated. Please note that escalation levels are designed to assist you, so please use them in order.

Escalation Name Role Email
Level 1 – Lines Devi Support manager
Level 1 – Systems Shahril Product Specialist
Level 2 – All Pratharean General manager
Level3 – All Kim Director


All complaints related to logged Support incidents should, in the first instance, be directed to the escalation paths. The complaint will be investigated and actioned, and if necessary, can be escalated to the Management Team –

Out of Hours Support

Out of hours support is provided only by prior agreement, however, faults on care level lines can be reported out of hours and will be logged
Please note that only those with care level 4 are 24 x 7 response and will be processed from the time of calling – these carry an

Appendix A – Incident logging requirements

Fault Localization

Preliminary Checks

  • To enable us to resolve any support queries as quickly as we would like, we will need certain information from you to open and progress support tasks.
  • Problem symptoms referring to all faults should be captured and must be recent.
  • Example calls should not be older than 48 hours except where this is impossible. The details required before reporting to our Support Desk are listed in ‘Fault Logging Requirements’.

Telephone Line Fault Localisation


  • Reboot the Customer Premises Equipment (Telephone System).
  • If you are unsure as to your equipment suitability for this then please check first with your system maintainer. This course of action resolves around 50% of faults reported to us.
  • Where a Telephone System is present, can you make internal calls?
  • Take note of what happens on incoming and outgoing calls.
  • If fault is intermittent how often does it occur?
  • Are DID’s  affected also? If so, which are affected? All/some?

VOIP Fault Localization

  • Reboot access router. Power down and leave off for a minimum of 20 minutes; power back on; wait 5 minutes, then check for connectivity.
  • If using SIP trunks, reboot the telephone system in line with the advice of the system maintainer. Check lights on routers; make a note of which are on/off.
  • If using ADSL as access method check for dial tone at socket.
  • Check if all handsets are experiencing issue.
  • Check lights on routers; make a note of which are on/off.
  • Take note of what happens on incoming and outgoing calls.
  • If fault is intermittent how often does it occur?
  • Are DDIs affected also? If so, which ones are affected? All/some?

Fault Logging Requirements

All current service faults should be preferably reported by telephone direct to our Support Desk. Verbal communication will allow our Support Desk to discuss the fault in detail and provide initial diagnostics without delay.

The following information should be provided to our Support Desk when logging a fault.

Line (WLR) Fault Requirements:

  • –              End-User & Service details
  • –              End-User’s Name
  • –              (i) PSTN & ISDN2 -CLI of the faulty line (complete, including the STD code)
  • –              (ii) ISDN30 – Circuit Reference number & type of telephone system
  • –              Full postal address of End-User’s premises
  • –              Contact name and telephone number (for BT & possible access purposes)
  • –              End-User Site Non-Access periods
  • –              Required Call Divert telephone number (Not International or premium rate)

Completed Preliminary Checks:

  • –              Has the equipment been checked & is okay?
  • –              Has the power supply been checked & is okay?
  • –              Has “Fault Localisation” been completed?

Faults Details:

  • –              Nature of fault
  • –              Symptom of fault
  • –              Intermittent/Frequency or permanent?
  • –              When did the fault start?

VOIP Fault Localization


  • –              Name
  • –              Full Postal Address
  • –              Contact Number
  • –              Access hours to premise

Circuit reference or telephone number

  • –              What is the problem?
  • –              Nature of fault
  • –              Symptom of fault
  • –              Frequent / Intermittent?
  • –              Has reboot been completed?
  • –              If broadband line has been tested or voice call attempted on the line from the test socket
  • –              Trace routes to, default gateway and next hop/available address if possible

VOIP Fault Requirements


  • –              Name
  • –              Full postal address
  • –              Contact number

What is the problem?

  • –              Nature of fault
  • –              Symptom of fault
  • –              Frequent/Intermittent?
  • –              If intermittent are there any patterns in the time(s) of failure?
  • –              Product type; Horizon, SIP trunking etc
  • –              When did the problem start?
  • –              Identify your router Make and Model
  • –              Have any changes happened on your local area network or firewall recently?
  • –              Which provided Internet Service are you using?
  • –              If you are having issues with call quality or destinations please create and complete a table similar to the one shown below dependent on whether or not the issues are for outgoing calls or incoming calls. We need at least three examples within the last 48 hours to investigate.
  • –              Do you need a divert?