Service Names
Onix Workspace Basic Support
Onix Workspace Business Support
Onix Workspace Enterprise Support
Product Codes
ONIX-SUP-WS-BASIC
ONIX-SUP-WS-BUS
ONIX-SUP-WS-ENT
Onix Delivery Team
Onix Support Services
Version
1.0
Published
February 2025
Technical Support for Google Workspace Service Specification
Technical Support for Google Workspace Service Specification
Technical Support for Google Workspace Service Specification
Technical Support for Google Workspace Service Specification
Technical Support for Google Workspace Service Specification
Technical Support for Google Workspace Service Specification
Technical Support for Google Workspace Service Specification

01. Service Overview

1.1 Service Description

Onix Technical Support for Google Workspace provides access to a Professional Google Workspace certified team of experts to help resolve Google Workspace issues and questions in a timely manner. The service aims to  boost collaboration and productivity, get value out of your Google Workspace licenses, and proactively plan for feature releases to minimize impact while increasing awareness for your end users.

02. Onboarding

2.1 Onboarding Process and Prerequisites

The Onix Support Team will guide onboarding to the Technical Support service. Technical Support Business and Technical Support Enterprise will include a Technical Account Manager guided Service Kick-Off Workshop within ten (10) business days of the agreement signature date unless otherwise agreed upon with Customer.

2.2 Authorized Contacts

To ensure adherence to Access Management Policies, only predefined Customer Authorized Contacts will be able to raise a request with the Onix Service Desk.

 

During Onboarding, Onix will require the customer to identify key contacts (up to 25) who will be added to Onix’s ITSM Platform. These names can be added or removed by the appropriate contact throughout the term of agreement. The Google Sheet for this  will be shared with you during the onboarding process. It is the responsibility of the Customer to update Onix with any changes to the list which can be accomplished by reaching out through the Onix Service Desk.

03. Service Desk

The Onix Service Desk is available for 1st line support for all requests described in this document. The Service Desk can receive tickets from Onix Engineers, Onix TAMs, and the authorized Customer Contacts. From there, the Service Desk will triage the request into one of the following ticket types described through this document:

  • Incidents
  • Service Requests

3.1 Service Desk Hours

Service Level
Service Desk Hours
Technical Support Basic
Monday - Friday | 8AM - 5PM - US East
Technical Support Business
24x7
Technical Support Enterprise
24x7

3.2 Contacting the Service Desk

The Onix Service Desk can be contacted through the following channels:

Onix Cloud Support Portal: https://cloudsupport.onixnet.com

Service Desk Email: cloudsupport@onixnet.com

The ticket will be logged into the IT Service Management tool. If triaged as an Incident, it will assign a priority based on the impact and urgency of the information provided.

Onix Service Desk will use reasonable endeavors to find a work-around or solution to the Incident. The Service Desk has multiple escalation routes to 2nd and 3rd Line Engineers, Technical Account Managers, and software vendor support teams. Onix will work with the appropriate resources to provide a resolution to the Incident within the agreed timeframes described in Section 4.4.

The priority of a ticket is not permanent,  and can be re-assigned at any point depending on the severity and developing nature of an Incident. Onix reserves the right to re-assign an appropriate priority according to the impact table as described in Section 4.3.

04. Incident Management

4.1 Incident Scope

An Incident is defined in the Information Technology Infrastructure Library (ITIL) framework as an unplanned interruption to an IT Service. The goal of Incident Management is to restore service as soon as possible within agreed timeframes. The Onix Support Team may recommend a workaround to temporarily restore the service and escalate to CSP for resolution.

4.2 Logging an Incident

Incidents must be logged through the Onix Service Desk where they will be recorded in the IT Service Management Tool, Jira, and assigned a ticket number. From here, Authorized Customer Contacts and Onix can update the Incident ticket via the Onix Service Desk Portal.

 

When logging an Incident, the Customer needs to provide as much of the following diagnostic information to Onix as possible:

  • Issue and / or error details
  • Impact / severity of Incident
  • Time of occurrence / duration of Incident
  • Steps taken to troubleshoot thus far
  • Documented steps to reproduce the issue
  • Screenshots, logs, or other supporting material

 

Onix is not obligated to respond to cases that do not follow the above requirements.

 

Incident requests submitted by users not on the Authorized Contact list will require Onix to reach out to the Customers’ Primary Contact for approval before any actions or remediation can be discussed or worked on with the contact reaching out – this also applies to P1 tickets.

4.3 Incident Prioritization

A priority level should reflect both the urgency of the issue, and its business impact to the Customer. Customer is to indicate the Ticket Priority upon submission of a new Ticket through the Support Portal to ensure intended Response Time. 

 

Onix Support reserves the right to redefine a Ticket priority after it is submitted by Customer to align with the following hierarchy:

Priority
Description of Issue
P1
Critical - Service Unusable in Production
P2
High - Service Use Severely Impaired
P3
Medium - Service Use Partially Impaired
P4
Low - Service Fully Usable

4.4 Service Level Agreements

4.4.1 Definitions

Response Time: Time for an agent to respond in a Case
Targeted Resolution Time: Target time to resolve a Case
Note: Time may vary if there is a Product issue from the Product owners (e.g. CSP, software vendor, etc.)

4.4.2 Service Level Agreements

Onix Workspace Basic

Service Desk Hours: Monday - Friday | 8AM - 5PM - US East

Priority
Response Time
Resolution Target
P1
4 Hour (24x5)
1 Business Day
P2
6 Hour (24x5)
1 Business Day
P3
8 Hour (24x5)
1 Business Day
P4
48 Hours (24x5)
3 Business Days

Onix Workspace Business

Service Desk Hours: 24x7

Priority
Response Time
Resolution Target
P1
1 Hour (24x7)
4 Hours
P2
2 Hours (24x7)
8 Hours
P3
4 Hours (24x7)
1 Business Day
P4
24 Hours (24x7)
3 Business Days

Onix Workspace Enterprise

Service Desk Hours: 24x7

Priority
Response Time
Resolution Target
P1
15 Minutes (24x7)
4 Hours
P2
1 Hour (24x7)
8 Hours
P3
4 Hours (24x7)
1 Business Day
P4
24 Hours (24x7)
3 Business Days

4.5 Three Strike Rule

Upon the resolution of an incident, the Onix Service Desk will contact the Customer to confirm they are satisfied with the result. If the Service Desk does not hear back from the Customer after three attempts to confirm the resolution, the ticket will be closed. Likewise, if the Service Desk has reached out to the customer for more information on an active ticket and does not hear back after three attempts, the ticket will be closed.

05. Service Request Management

5.1 Service Request Scope

Onix’s definition of a Service Request includes the following:

  • Request for information about the Customer environment from an Authorized Contact
  • Request for best practice guidance
  • Vendor requests, such as quota increase, from an Authorized Contact

5.2 Logging a Service Request

Service Requests must be logged through the Onix Service Desk where they will be recorded in the IT Service Management Tool, Jira, and assigned a ticket number.

 

From here, Authorized Customer Contacts and Onix can update the request via the Onix Service Desk portal and see progress towards resolution.

 

All Service Requests will automatically be treated as a P4, as described in Section Section 5.3, as this type of request should not include service impacting issues.

5.3 Service Level Agreements

Priority
Response Time
Resolution Target
P4
1 Business Day
3 Business Days

5.4 Three Strike Rule

Upon the completion of a Service Request, the Onix Service Desk will contact the Customer to confirm they are satisfied with the result. If the Service Desk does not hear back from the Customer after three attempts to confirm the resolution, the ticket will be closed. Likewise, if the Service Desk has reached out to the customer for more information on an active ticket and does not hear back after three attempts, the ticket will be closed.

06. Escalation Management

Where applicable, the Onix Technical Account Manager (TAM) will act as an escalation contact for Google Workspace issues.

6.1 Escalating a Ticket

Tickets may be escalated by logging into the Onix Support Portal, and clicking the Escalate button within the support ticket.

6.2 Response

The Onix Service Desk will respond within 60 minutes within the service hours described in Section 4.4 to confirm the escalation. The Service Desk will escalate the ticket within the Onix team. For cases opened with the software support vendor, the Onix Service Desk will follow the vendor escalation process and monitor until the vendor responds.

6.3 Validity

Tickets should not be escalated before the SLA response time has been reached. In the event that a ticket is escalated prior to first response and within the contracted first response time, the Onix Service Desk will make sure the ticket is being addressed and respond as normal.

 

For changes in business impact or urgency, please update the ticket with information about the business impact when escalating the ticket.

07. Financial Operations

7.1 Service Description

As part of the Technical Support Business and Technical Support Enterprise services, the Onix Technical Account Manager will review the Customer’s Google Workspace environment and provide quarterly Financial Operations review and recommendations.

08. Technical Account Management

8.1 Service Description

Onix provides the Customer with a named Technical Account Manager (TAM). The TAM is responsible for ensuring that the service(s) provided meet the specifications detailed in this document and will act as an escalation point for the Customer within the Onix Support Team.

Service
Weekly TAM Hours
Onix Workspace Basic
N/A
Onix Workspace Business
Up to 2 Hours
Onix Workspace Enterprise
Up to 8 Hours

8.2 Enhanced Support Experience

The Onix TAM will actively monitor Customer’s support tickets with both Onix and the software vendor, and is available during Customer business hours to discuss support issues or create support tickets on the Customer’s behalf. The TAM will provide updates and reports on support activity in regularly scheduled meetings and Quarterly Service Reviews.

8.3 Quarterly Service Reviews (QSR)

Onix TAM services are designed to maximize return on the Google Workspace investment by providing guidance on product use, educating, managing changes and planning strategies around use of the product.

8.3.1 Review Content and Cadence

The TAM will prepare and deliver a QSR virtually to the key Customer stakeholders. This review can be customized as the relationship between Onix and the customer progresses to ensure that the information shared continues to provide value. The review can include but not be limited to the following:

  • Summary of Cases Logged and Incident Trends
  • SLA Attainment
  • License Optimization Recommendations
  • FinOps Review and Recommendations
  • Google Workspace Roadmap Updates

8.4 Security Review for Google Workspace

A periodic review of security best practices and possible problem areas within the Google Workspace environment, provided that the Onix TAM has appropriate access to do so.

  • Scope: 100+ security settings will be reviewed in the Workspace Administration console for the organization’s top-level OU and one randomly selected sub-OU
  • Scorecard: A score of the security review will be delivered by the TAM to give the Customer a clear, metrics-driven picture of the Google Workspace environment’s security status
  • Follow-up: The TAM will outline a list of action items to address any issues that arose during the review and may suggest a project plan to outline any initiative that we can help with due to the review.
  • Frequency: Technical Support Enterprise service level, the TAM can conduct a semi-annual Security Review of the root-level OU and one additional OU. At the Technical Support Business service level this review will take place annually.

8.5 Google Workspace Roadmap Discussion

The Onix TAM will share the quarterly Google Workspace Roadmap and lead a discussion of Roadmap items that are important to the Customer’s organization, providing updates around expected release dates and feature requests.

09. Disclaimers & Additional Acknowledgements

  1. The Customer will work with any end-user in their environment directly as Onix Support will not interact with non-administrators for support unless agreed upon in a separate paid agreement.

  2. The Customer shall only allow Authorized Contacts to open Tickets with Onix Support. Onix shall not be liable for delays or inability to deliver Support Services caused by an unknown contact reaching out for support or information.

  3. The Customer shall only open Tickets via the Support Channels defined in Section 3.2. Onix shall not be liable for delays in support caused by issues submitted through other channels.

  4. The Customer shall provide Authorized Contact(s) with appropriate administrator credentials on the Production Environment. Failure to have appropriate permissions will cause delay in troubleshooting.

  5. The Customer acknowledges that third-party software (from neither Google nor Onix) is not supported under this agreement. Separate agreements will be required for any 3rd party software that Onix Support will be responsible for.

  6. Onix will not make direct changes (hands on keyboard) to your Google Workspace tenant.