請與 Cloud Customer Care 團隊和 TAM 合作，尋求其他支援。如果你建立客服案件，請務必提供詳細且具體的資訊，方便客服團隊迅速且有效率地回覆你。如要讓 Google 立即處理，請考慮將支援案件的優先順序設為「P1」。之後隨時可以降級。詳情請參閱「使用 Customer Care 的最佳做法」。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Prepare to resolve issues during your event\n\nHow you respond to, categorize, and solve incidents of differing severity can\nsignificantly affect your operations during an event. Use a centralized incident\nmanagement system for effective tracking throughout the incident lifecycle. For\nmore information, see\n[Manage incidents and problems](/architecture/framework/operational-excellence/manage-incidents-and-problems).\n\nReview best practices when working with Customer Care\n-----------------------------------------------------\n\nWork with your Cloud Customer Care team and your TAM for additional support. If\nyou're [creating a support case](/support/docs/customer-care-procedures), make\nsure to provide detailed and specific information to make it easier for the\nCustomer Care team to respond to you quickly and efficiently. To get\nimmediate attention from Google, consider choosing \"P1\" for the support case\npriority. You can always downgrade the priority later. For more information, see\n[Best practices for working with Customer Care](/support/docs/best-practices).\n\nCreate a communication plan\n---------------------------\n\nEstablish clear incident response procedures including clear roles and\nresponsibilities, communication protocols, and escalation paths. Create a\nvirtual chat room or conference call for cross-collaboration and communication\nbetween teams and vendors so that there's a channel for updates and progress\nreports.\n\nEnsure access\n-------------\n\nResolve any authentication and access issues before your event. Make sure that\nyou have granted the appropriate permissions to users, developers,\noperators, data scientists, security administrators, network administrators, and\nany other roles in your organization. This includes the ability to create\nsupport cases, troubleshoot issues, and access your disaster recovery\nenvironment.\n\nReview your contacts\n--------------------\n\nMany Google Cloud offerings, such as Cloud Billing, send out\nnotifications to share important information with Google Cloud users. By\ndefault, these notifications are sent to members with certain\nIdentity and Access Management (IAM) roles. With Essential Contacts, you can\ncustomize who receives notifications by providing your own list of contacts.\nMake sure to review your contacts ahead of your event and modify them as needed.\nFor more information, see\n[Managing contacts for notifications](/resource-manager/docs/managing-notification-contacts).\n\nEnable Personalized Service Health\n----------------------------------\n\nPersonalized Service Health lets you identify Google Cloud service disruptions\nrelevant to your projects so that you can manage and respond to them efficiently.\nFor more information, see the\n[Personalized Service Health overview](/service-health/docs/overview).\n\nMake sure that you have enabled the Service Health API ahead of your event\nand that your organization can access the dashboard and configure alerts.\nFor more information, see\n[Manage Personalized Service Health access](/service-health/docs/manage-access).\n\nWhat's next\n-----------\n\n- [Optimize your cloud resources](/support/docs/peak-events/optimize-resources)"]]
