Cloud Support Procedures

This document explains how to complete common Cloud Support procedures and activities, including:

  • Create and manage support cases based on your organization's Support plan.
  • View known issues affecting Google Cloud services.
  • Contact Support by phone.
  • Access additional services available to select paid Google Cloud plans, such as escalate or change the priority of a support case.

To learn about the availability of Cloud Support, see Language Support and Working Hours.

For details about Google Cloud's Support offerings, see the Technical Support Services Guidelines.

Manage support cases

Your organization's Support plan determines how you create and manage support cases:

The details you include in a support case significantly affect how long it takes to resolve an issue. To learn about how to write an effective support case, see Best Practices for Working with Cloud Support.

Manage support cases in the Google Cloud Support Center

If your organization's Support plan is Bronze, Silver, Gold, or Platinum, learn how to manage support cases in the Google Cloud Support Center.

Manage support cases in the Google Cloud Console

If your organization's Support plan is Role-Based, Enterprise, or Premium Support, you must create and manage cases in the Cloud Console.

Create a support case

Before creating a support case, review known issues to see if a case has already been filed.

If no case has been filed, you can create one in the Cloud Console by completing the following steps:

  1. Sign in to the Google Cloud Console.
    Go to the Cloud Console
  2. Select the project for which you'd like to have support.
  3. On the Support page, go to Quick Support and click Create a new support case.

After creating a case, you are redirected to the Case page where you can manage new or existing cases. The Support team responds to your case based on its priority and your Support role.

Manage existing support cases

Any user with permission to edit support cases can update cases for your organization, even if they did not create the case.

To manage existing cases:

  1. Sign in to the Google Cloud Console.
    Go to the Cloud Console
  2. Access your project.
  3. On the Support page, click Cases.

The Cases page provides a list of your organization's support cases based on the selected resource. For example, if you select an organization, all cases for the organization are displayed. If you select a project, only the cases associated with that project are displayed.

You can can filter cases using Search or filter controls.

To view or update a case, click on its title. After selecting the case, you can make the following updates:

  • Comment on the case
  • Upload file attachments
  • Modify case attributes
  • Reopen cases

View known issues

The Cloud Support team posts information about known issues affecting Google Cloud services as they arise. If there are any open known issues that might be affecting your Google Cloud services, you will see a notification whenever you create a support case.

To view known issues that affect your organization's support cases:

  1. Sign in to the Google Cloud Console.
    Go to the Cloud Console
  2. Access your project.
  3. Go to the Support page and open Phone support.
  4. On the Support page, click Cases.
  5. Select Known Issues.

To learn about incident reporting, view the documentation on Incidents and the Google Cloud Status Dashboard.

Contact Support by phone

All users can contact phone support with questions about Cloud Billing. If your Support plan is Gold, Platinum, Role-Based Production, or Enterprise, you can also request phone support for technical questions about projects within your organization.

To contact Support by phone:

  1. Sign in to the Google Cloud Console.
    Go to the Cloud Console
  2. Select the project for which you'd like support.
  3. Go to the Support page and open Phone support.
  4. Select your current country and call the phone number provided.
  5. When prompted, enter the PIN that is displayed on the Phone support page.

Additional services

If your Support plan is Gold, Platinum, Role-Based Production, Enterprise, or Premium, you have access to the following additional services:

  • Request a call back or Google Meet
  • Change the priority of your support case
  • Escalate a support case

Depending on your plan and support language, you might also be eligible to receive 24/7 support. For information on availability, see Language Support and Working Hours.

Request a call back or Google Meet

When creating a support case, you can request a call back or Google Meet with a Support engineer. After investigating your case, the engineer can call back or start a Google Meet to provide further information.

Google Meet is a powerful tool for many reasons:

  • Multiple participants can be invited into the same Google Meet session, which can be useful and more efficient than phone conference bridges.
  • All participants can share their screen or exchange code snippets for faster troubleshooting.
  • Higher quality audio and video can enhance or personalize your interactions with the Support team.

To request a call back or Google Meet, include your preferred contact method and contact details in your support case.

Change case priority

If the service impact of a support case changes, you can change the priority of your case accordingly. When you change the priority, Cloud Support is notified and attends to your case based on the new priority.

You can change the case priority in the Google Cloud Support Center or by replying to the latest email of your case.

When changing the case priority, be sure to provide information about the reason for change, and specifically, how the impact to the business has changed.

Escalate a case

If your support case has the appropriate priority, you can escalate it if the support effort is not meeting expectations.

The following examples demonstrate possible reasons for escalating a case:

  • Cloud Support misses time commitments.
  • Cloud Support misunderstands the impact of the issue.
  • The case might require additional expertise to resolve the issue.

When requesting an escalation, quote the case number and provide a reason for the escalation. You can make the request in the following ways:

  • Comment in the case.
  • Click the Escalate case button which appears 60 minutes after creating the case.
  • Contact Support by phone

If you have a Platinum, Enterprise, or Premium Support offering, you can also request an escalation by contacting your Technical Account Manager during local business hours.

For more information about navigating escalations, see the Best Practices guide.

Following the sun

Normally, a case is handled within one time zone by a single Support engineer. Doing so allows Cloud Support to offer a personalized service in the time zone closest to you.

Due to the high impact of Priority 1 (P1) cases, they are defaulted to follow the sun, which means that the case is handed off between global teams to provide 24-hour Support coverage. If your plan is Platinum, Enterprise, or Premium, you can also request this service for Priority 2 cases.

To enable follow-the-sun service, contact the engineer working on your case during local business hours.

Reference

Support case status

After a support case is created, you can view case status in the Support Center for Bronze, Silver, Gold, and Platinum offerings or in the Google Cloud Console for Role-Based, Enterprise, and Premium offerings. Below is a description of the different statuses and their meaning:

Status Description
New The case is not assigned yet.
Assigned The case is assigned to one of our engineers. You'll see a response within the target response time mentioned in the priorities table.
In progress Cloud Support Cloud Support engineers are working on the case.
In progress Google engineering Google product engineers are investigating the case. Turnaround times vary, depending on the issue complexity and product component in question.
In progress Google other Another Google team is investigating the case. Turnaround times can vary, depending on the issue complexity and product component in question.
Waiting on customer response We need more information from you before we can proceed.
Waiting on customer action We need you to do something before we can proceed.
Solution offered A solution for the issue or request in the case has been offered. The customer can reopen the case if the offered solution is insufficient.
Closed The case is resolved and closed by the Support engineer. If the issue is still ongoing, you can reopen it within 30 days by replying to the last communication. After 30 days, you'll need to open a new case.

Support case priority

When creating a support case, it's important to assign it the correct priority. Per the Google Cloud Technical Support Services Guidelines, the case priority determines the initial response time for the case.

The following table defines support case priorities. For more information, see best practices for changing case priority.

Priority definition Example situations
P1: Critical Impact—Service Unusable in Production The application or infrastructure is unusable in production, having a significant rate of user-facing errors.

Business impact is critical (revenue loss, potential data integrity issue, etc.).

No workaround is available that is easy to implement (less than 30 minutes).

Affected Google Cloud component or feature is marked as General Availability.

Immediate attention from Google is required to resolve the problem.

P2: High Impact—Service Use Severely Impaired The infrastructure is degraded in production, having a noticeable rate of user-facing errors or difficulties in spinning up a new production system.

Business impact is moderate (danger of revenue loss, productivity decrease, etc.).

A workaround to mitigate critical business impact is available and easy to implement.

Affected Google Cloud component or feature is marked as General Availability.

Fast response from Google is required.

P3: Medium Impact—Service Use Partially Impaired The issue is limited in scope and/or severity. The issue has no user-visible impact.

Business impact is low (for example, inconvenience, minor business processes affected, etc.).

Case requires more in-depth investigation and troubleshooting and less frequent interactions.

P4: Low Impact—Service Fully Usable Little to no business or technical impact.

Recommended for consultative tickets where in-depth analysis, troubleshooting or consultancy are preferred to more frequent communications.