Prepare and test your skills

Prepare and test your skills

Examine Case Creation and Initial Triage is the first stage in the life of a support case in Google Cloud Customer Care (opens in a new tab). A user with the right role starts the case in the Google Cloud console, describes the issue, and sets a priority level. That early information decides how the case is classified, which team receives it, and how fast the response will be.
How Support Cases Are Started in the Console explains who can create a case and the ordered steps they follow. Only a user with the Tech Support Editor role can create or manage technical support cases. The Tech Support Editor role gives read-write access to support cases and can be granted at the organization, folder, or project level. The user must first select the organization or project for the case, because that choice controls where the case is filed and who can view it.
Creating a case follows a fixed flow from product selection to submission:
A six-step left-to-right flow showing how a Tech Support Editor starts, describes, prioritizes, classifies, channels, and submits a case in Support > Cases.
Live chat is the quickest connection to a representative but is available only in English, with a transcript sent by email and viewable in the console. Email allows the customer to specify a supported language. After submission, the Customer Care team responds based on the case priority and the support package that applies.
Information Needed for Classification of a Case is the detailed technical and business context that lets Customer Care route the case to the right experts. Classification works best when the case is detailed and specific, because the expert does not have to pause to ask for basic facts. Selecting the correct product, category, and sub-category is especially important because it decides which team first receives the case.
Strong cases include focused context about what happened, where, and what changed:
For access issues, the case should also include the requesting identity, whether all or only some identities fail, granted permissions, and the source of access such as console, CLI, Cloud Shell, or on-premises. Sensitive data such as access tokens, credentials, and credit card numbers should be redacted from logs before sharing with Customer Care (opens in a new tab).
How Severity Levels Shape Response Expectations describes how priority levels P1 through P4 signal business impact and set the speed of engagement. Priority levels have predefined response times defined in the Google Cloud Platform Technical Support Services Guidelines. Higher impact drives faster engagement and more intensive handling, while lower impact fits consultative analysis with less frequent communication.
| Priority | Definition | Example Situation |
|---|---|---|
| P1 | Critical Impact — Service Unusable in Production | Application or infrastructure is unusable in production with a high rate of user-facing errors and critical impact such as revenue loss or data integrity risk |
| P2 | High Impact — Service Use Severely Impaired | Infrastructure is degraded in production with noticeable user-facing errors or difficulty creating a new production system |
| P3 | Medium Impact — Service Use Partially Impaired | Issue is limited in scope with no user-visible impact, such as inconvenience or minor business process affected |
| P4 | Low Impact — Service Fully Usable | Little to no business or technical impact, recommended for consultative tickets preferring in-depth analysis over frequent updates |
A P1 case triggers immediate, dedicated handling. An expert is immediately alerted to work exclusively on the issue, and the customer receives a quick initial response to join a live troubleshooting call through Google Meet or a customer-provided bridge. The customer is expected to join within 15-30 minutes and stay engaged until mitigation, because becoming unresponsive for more than 3 hours may cause the priority to drop to P2. P1 cases follow the sun by default, which means experts engage 24 hours a day with handoffs across regions until the case is mitigated or deprioritized.
Exam tip: Choose P1 when production service is unusable with critical business impact; setting the correct priority drives a faster response, while escalating shortly after a priority change does not necessarily resolve the case faster.
Analyze Communication and Case Management Practices covers how customers and Google Cloud Customer Care (opens in a new tab) exchange information from creation to closure. The customer provides detailed issue data through the Google Cloud console, and Customer Care engineers respond, investigate, and request follow-up based on priority and support service. Clear updates on both sides keep the case moving instead of stalling while waiting for missing details.
How Customer Care Engineers Engage Throughout a Case follows the status lifecycle from assignment to investigation to resolution. A new case starts as New when it is not yet assigned, then moves to Assigned when a specialist takes ownership and responds within the target response time for its priority. From there, work continues as In progress Cloud Customer Care while specialists work the case, or shifts to In progress Google engineering or In progress Google other when product engineers or another Google team must investigate.
A state lifecycle showing New to Assigned to In Progress Cloud Customer Care to Closed, with branches to In Progress Google engineering, In Progress Google other, and a Waiting on customer pause loop.
| Status | What it means |
|---|---|
| New | The case is not assigned yet. |
| Assigned | The case is assigned to a specialist who responds within the target response time. |
| In progress Cloud Customer Care | Customer Care specialists are working on the case. |
| In progress Google engineering | Google product engineers are investigating, with timing that varies by complexity. |
| In progress Google other | Another Google team is investigating, with timing that varies by complexity. |
| Waiting on customer response | More information is needed from the customer before work can continue. |
The status changes to Waiting on customer response when specialists need more information, so the case pauses until the customer answers. If an issue causes pressing business impact, escalation pages an Escalation Manager who adds resources to fast-track resolution, though escalation does not apply to Comprehensive Support and Standard Support. When a case moves to engineering or another team, the assigned specialist remains the point of coordination while deeper investigation happens elsewhere.
Tracking and Updating Cases in the Support Center centers on the Cases page in the Support section of the Google Cloud console. The Cases page shows status, history, and general information for each case. The customer selects an organization or project with the resource selector, so an organization view shows all its cases while a project view shows only cases for that project. The Filter list helps find cases by property.
Any user with permission to edit cases can keep the record current, even if they did not create the case:
Live chat transcripts are also tracked through this system, with transcripts sent by email and viewable in the console by users with appropriate permission. Case sharing and linked cases extend tracking beyond a single console view. When case sharing is enabled by a Support Account Administrator, users inside and outside the organization can follow a case and reply by email. A linked support case (opens in a new tab) connects a customer case to a known issue, so the customer automatically receives updates about that issue.
Why Timely and Accurate Communication Moves Cases Forward explains how good input prevents delays and keeps investigation on track. The best cases are detailed and specific, including a clear issue description, observed error messages, priority, product, and sub-category. Selecting the correct sub-category forwards the case to the correct team, while attachments in widely supported formats such as PNG, TXT, or PDF give engineers evidence such as logs and screenshots. Before filing, checking known issues avoids duplicate cases and can point to an existing fix or linked case.
Progress after submission depends on continued responsiveness from both sides. The Customer Care team responds based on case priority and support service, so an accurate priority helps match urgency to resources. When the status is Waiting on customer response, no further work can proceed until the customer supplies the requested details. After closure, the customer receives a Customer Feedback Survey and can reopen the case within 15 days if the solution is insufficient.
Exam tip: A closed case can be reopened only within 15 days and returns to the last specialist to preserve context, but initial response times do not apply — set priority to P1 for urgent reopened cases.
Understand Resolution Processes and Post-Case Outcomes describes how Google Cloud Customer Care (opens in a new tab) resolves cases based on priority and support package, and how lessons after closure improve reliability. A technical support request is submitted through the Create Case option in the Google Cloud console (opens in a new tab). The case then moves from creation and classification through communication, possible escalation, resolution, and post-case feedback and learning.
Priority and Support Package Drive Resolution Behavior explains how urgency and subscription level shape who works the case and how fast. Priority tells Customer Care how much an issue affects the business, from P1 Critical Impact where production service is unusable, down to P4 Low Impact where service is fully usable and the request is consultative. When a case is set to P1, an expert is immediately alerted to work exclusively on the issue, and the customer should join a live troubleshooting call through Google Meet within 15-30 minutes. If the organization cannot use Google Meet, it can include a link to its preferred video conferencing software.
P1 cases follow the sun by default, meaning support experts engage 24 hours a day until the case is mitigated or deprioritized. If mitigation is best pursued in one region, the case can be locked to a specific time zone. P1 cases are handed to the next region because they follow the sun, while P2-P4 cases generally stay with the current owner to continue the next day. An existing P2-P4 case can be raised to P1 if it starts impacting production, which may reassign it to an available expert. If the customer becomes unresponsive for more than 3 hours, support may reduce P1 to P2 until the customer re-engages.
The support package also affects resolution. Standard, Enhanced, and Premium Support customers have a direct channel or point of contact on the Google Support team, and response times vary by support model. Basic Support customers for Telecom Network Automation use an issue tracker link and can expect an initial response within 24-48 hours, but Google cannot guarantee specific resolution times. For Sovereign Controls by Partners (opens in a new tab), partner-led support uses the partner ticketing system and partner personnel handle the case, while Google-led support uses the Cloud Customer Care ticketing system, requires Enhanced or Premium Support, and Google personnel handle the case.
Escalation and Resolution Decisions During a Case covers when to escalate and how a resolved case is closed. Escalation is used when circumstances change, such as an increase in business impact or a breakdown in the resolution process like missing an agreed update or the issue being stuck after several messages. For a high-impact issue, the best solution is to set the case to the appropriate priority for an adequate amount of time rather than escalating immediately. Escalating does not necessarily resolve the case faster, and escalating shortly after a priority change might even slow resolution.
Resolution may involve support experts, engineering teams, or partner personnel depending on the support model. Issue tracker reports are acknowledged and triaged within two business days, and updates are posted only when there are questions or something to share. To close a resolved case, the customer follows these steps:
When creating a case, the customer also chooses a support channel: live chat or email. Live chat is the quickest connection and provides a transcript by email and in the console, but is available only in English. Email allows the customer to specify a supported language.
Exam tip: For a high-impact issue, set the case to the correct priority for an adequate amount of time instead of escalating immediately; escalating shortly after a priority change can slow resolution.
Capturing Case Details and Access Troubleshooting Context shows what information helps Customer Care respond quickly and efficiently. The best support cases are detailed and specific, and selecting the best sub-category helps ensure the case is forwarded to the correct team. Before sharing logs with Customer Care, sensitive data such as access tokens, credentials, and credit card numbers must be redacted.
For access issues, gathering the following information before escalation speeds up triage:
This complete context lets the specialist reproduce the problem, check policy, and route the case without extra rounds of questions.
Post-Case Outcomes and Reliability Improvements are the feedback and learning steps that turn one case into better future operations. When a case is resolved, a Customer Effort Score (CES) survey is sent by email to collect the customer's opinion on how the process went. Issue tracker reports also produce outcomes: after triage, Google tells the reporter what was found, whether the issue is verified, or whether a feature will not be implemented for the foreseeable future.
Teams can use post-case insights by regularly analyzing support issues, iterating, and improving based on lessons learned. A standardized retrospective form helps capture those lessons in a consistent way. Communicating support processes to internal staff, including how to contact Google Cloud named contacts, helps the organization respond consistently and build operational best practices. This feedback loop supports reliability improvements by turning individual cases into changes in process or product behavior.
Only a user with the Tech Support Editor role can create or manage technical support cases, and the role can be granted at the organization, folder, or project level. The user selects the organization or project to control where the case is filed and who can view it, then selects the product such as Compute Engine, describes the issue, chooses a priority with P4 - Low impact as the default, selects category and sub-category for routing to the correct team, chooses live chat or email with business impact and affected resources, and submits for tracking on the Cases page.
Priority levels run from P1 Critical Impact where production service is unusable in production to P4 Low Impact where service is fully usable, and higher impact drives faster engagement. A P1 case triggers immediate dedicated handling with an expert alerted to work exclusively on the issue and a live troubleshooting call that the customer is expected to join within 15-30 minutes, and P1 cases follow the sun with 24-hour engagement across regions while P2-P4 cases generally stay with the current owner. Becoming unresponsive for more than 3 hours may cause a P1 priority to drop to P2.
When a case is resolved, a Customer Effort Score (CES) survey is sent by email to collect the customer opinion on the process, and teams use post-case insights by analyzing support issues and using a standardized retrospective form to improve reliability. A customer closes a resolved case through View case and Close case in General Information with confirmation, and a closed case can be reopened only within 15 days.
A retail organization's primary e-commerce application running in production on Google Cloud suddenly stops serving traffic to customers. The operations team observes the following conditions:
How should the team classify and submit the support case to ensure effective initial triage and the fastest possible response from Customer Care?
Last updated