Detailed SLA

Detailed SLA

Support & Service Level Agreement

Environment :

Customer will be able to access the Service only by using a standard Web Browser like Google Chrome 20+, Internet Explorer 8.0+, Mozilla Firefox 20+ over the internet (and their respective updated/upgraded versions) over the internet.

Environment :

Customer will be able to access the Service only by using a standard Web Browser like Google Chrome 20+, Internet Explorer 8.0+, Mozilla Firefox 20+ over the internet (and their respective updated/upgraded versions) over the internet.

Hardware :

The hardware required to provide the Services will be located in a data center which have facilities like Multiple Carrier’ link to the Internet, Backup Power Supplies, Climate Controlled Air Conditioning, Raised Floors for Cabling and Electronic Security Systems.

Uptime :

The Company shall use commercially reasonable endeavours to make the Services available twenty-four (24) hours a day, seven (7) days a week, with an uptime guarantee of 99.9% except for:

  • planned maintenance carried out during the maintenance schedule from time to time; and

  • unscheduled maintenance performed outside normal business hours, provided that the Company has used reasonable endeavours to give the Customer notice in advance.

Support &  Service Levels :

  • Zipteams will respond to and resolve issues as per the timelines given in the issue resolution matrix. This could be any query that the admins of a Customer raise via an email to (1) their designated point of contact at Zipteams or (2) info@Zipteams.com.

  • On-site support is not included and any out-of-scope work shall be subject to Company's standard man-day rate.

Issue Resolution Matrix :

Every issue reported by a client will be classified by their designated point of contact at Zipteams under one of the following categories and resolved as per the following timelines: 


*: An incident is considered resolved when a reasonable and functional solution has been implemented to restore the user experience to its pre-incident condition. This resolution may take the form of a permanent fix that fully addresses the root cause, or alternatively, it could be a temporary workaround that mitigates the impact while a more comprehensive solution is developed and deployed at a later time.

Issue Priority

Issue Priority

Response Time

Response Time

Resolution Time*

Resolution Time*

Definition

Definition

P1 – Critical

P1 – Critical

60 minutes

60 minutes

3 hours

3 hours

P1 issues are critical where attention is required immediately. Security, availability, legal liability issues or storage issue (data loss or corruption); a resolved bug which is re-opened or functionality affecting almost all users.

P1 issues are critical where attention is required immediately. Security, availability, legal liability issues or storage issue (data loss or corruption); a resolved bug which is re-opened or functionality affecting almost all users.

P2 – High

P2 – High

60 minutes

60 minutes

12 hours

12 hours

Functionality affecting significant number (∼50%) end users or permission holders/admins, integration issues with other systems

Functionality affecting significant number (∼50%) end users or permission holders/admins, integration issues with other systems

P3 – Normal

P3 – Normal

120 minutes

120 minutes

48 hours

48 hours

Functionality affecting limited number of end users, aesthetics, typographical errors.

Functionality affecting limited number of end users, aesthetics, typographical errors.

Backend tasks

Backend tasks

120 minutes

120 minutes

7 business days

7 business days

Back end jobs and workaround activities which are not directly related to the functionality of the product and have to be executed by the Company's Tech Team by writing a bespoke script from the back end.

Back end jobs and workaround activities which are not directly related to the functionality of the product and have to be executed by the Company's Tech Team by writing a bespoke script from the back end.

Issue Priority

Issue Priority

Elaboration & Instances

Elaboration & Instances

P1 – Critical

P1 – Critical

  • System is down without prior notice

  • Not able to conduct meetings

  • Security concerns or breach

  • Data loss or corruption of the data

  • Issues which affects the existing functionality after every release

  • Configs  are not getting applied as per the setups

  • System is down without prior notice

  • Not able to conduct meetings

  • Security concerns or breach

  • Data loss or corruption of the data

  • Issues which affects the existing functionality after every release

  • Configs  are not getting applied as per the setups

P2 – High

P2 – High

  • Adhoc meeting issues with audio, video, screen-sharing etc

  • Functionality break affecting more than 50% of users

  • Any integration issues where our system fail to push the data to other systems

  • Adhoc meeting issues with audio, video, screen-sharing etc

  • Functionality break affecting more than 50% of users

  • Any integration issues where our system fail to push the data to other systems

P3 – Normal

P3 – Normal

  • UX/UI issues

  • Spelling corrections

  • Any issue specific to few users

  • UX/UI issues

  • Spelling corrections

  • Any issue specific to few users

Zipteams Escalation Matrix for any assistance or queries :

Level

Level

Point of Contact

Point of Contact

Contact Information

Contact Information

Email

Email

Escalation Context

L1

L1

Support Team

Support Team

9653198284 - WhatsApp/Dedicated WhatsApp Group

9653198284 - WhatsApp/Dedicated WhatsApp Group

support@zipteams.com

support@zipteams.com

First POC

First POC

L2

L2

Account Manager

Account Manager

WhatsApp Group

WhatsApp Group

support@zipteams.com

support@zipteams.com

After 12 hours

After 12 hours

L3-Technical Escalations

L3-Technical Escalations

Akash Chatterjee

Akash Chatterjee

akash@zipteams.com

akash@zipteams.com

For technical issue escalations

For technical issue escalations

L3-Any Escalations

L3-Any Escalations

Siddhartha Srivastava

Siddhartha Srivastava

9594020552

9594020552

siddhartha@zipteams.com

siddhartha@zipteams.com

For unresolved assistance/escalations beyond 24 hours

For unresolved assistance/escalations beyond 24 hours

Please note :

  1. Response/Resolution timelines are stated with reference to the time an issue is reported

  2. Response/Resolution timelines are for weekdays Mon-Fri 10 AM - 7 PM IST except for P1 issues where timings and team availability will be 24*7.

  3. Every issue is to be reported by the client via e-mail to their designated point of contact at Zipteams or support@zipteams.com.

  4. On-site support is not included and any out-of-scope work shall be subject to Zipteams's standard man-day rate.

  5. Based on priority, issues are automatically escalated by Zipteams’s internal systems to the Customer’s Customer Success Manager who shall take further actions to expeditiously resolve the request.

  6. While the SLA will hold true for reporting and escalations, Zipteams is committed to resolve business critical issues for its clients at the earliest to ensure business continuity without any blockers. A client can reach out to their designated Customer Success Manager to to escalate an issue, if required.


* Performance of back end tasks is subject to technical feasibility and risk assessment. Company shall not be obliged to do every back end task within the given timeline of 7 business days.

Please note :


  1. Response/Resolution timelines are stated with reference to the time an issue is reported

  2. Response/Resolution timelines are for weekdays Mon-Fri 10 AM - 7 PM IST except for P1 issues where timings and team availability will be 24*7.

  3. Every issue is to be reported by the client via e-mail to their designated point of contact at Zipteams or support@zipteams.com.

  4. On-site support is not included and any out-of-scope work shall be subject to Zipteams's standard man-day rate.

  5. Based on priority, issues are automatically escalated by Zipteams’s internal systems to the Customer’s Customer Success Manager who shall take further actions to expeditiously resolve the request.

  6. While the SLA will hold true for reporting and escalations, Zipteams is committed to resolve business critical issues for its clients at the earliest to ensure business continuity without any blockers. A client can reach out to their designated Customer Success Manager to to escalate an issue, if required.


* Performance of back end tasks is subject to technical feasibility and risk assessment. Company shall not be obliged to do every back end task within the given timeline of 7 business days.

Certain conditions :


Zipteams shall not be obligated to provide the support service if -

  1. the reported error was caused by changes in program parameters or other user adjustable features;

  2. the error results from operator error, errors in customer data or software not supplied by company or use that is not in accordance with the documentation;

  3. the customer has failed to pay any required fee or is otherwise in default of the agreement between customer and Zipteams;

  4. to the extent, if any, that the service is third party software (such as operating systems or third party data or applications), it is acknowledged that the level of support provided by such third parties may impact company’s performance of such services.

  5. support service will not be applicable if the third party is engaged by the company.