> ## Documentation Index
> Fetch the complete documentation index at: https://the-early-spring18.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Platform Support Channels and Help Resources

> Find the right support channel for your needs — community forum, email support, live chat, or dedicated enterprise support options.

Getting help with Google is straightforward — the right channel depends on your plan and the urgency of your issue. Free users have access to a thriving community forum where experienced members and Google staff answer questions every day. Paid plans unlock direct support via email and live chat, while Enterprise customers receive a dedicated support engineer and a guaranteed response SLA. This page explains each channel, what to prepare before reaching out, and how to navigate the self-service resources available to every user.

## Support Channels

<CardGroup cols={2}>
  <Card title="Community Forum" icon="comments" href="https://community.google.com">
    Ask questions, share tips, and search thousands of answered threads. Available to all users on every plan, including Free. The best starting point for general how-to questions.
  </Card>

  <Card title="Email Support" icon="envelope" href="mailto:support@google.com">
    Submit a support ticket and receive a response from the Google support team. Available on all paid plans. Include your account ID and request IDs for the fastest response.
  </Card>

  <Card title="Live Chat" icon="message" href="https://google.com/support/chat">
    Connect with a support engineer in real time through the in-app chat widget. Available to Pro and Enterprise plan customers during business hours (9 AM – 6 PM in your local timezone).
  </Card>

  <Card title="Enterprise Support" icon="building" href="https://google.com/enterprise">
    Enterprise customers receive a dedicated support engineer, guaranteed response SLAs, quarterly business reviews, and an escalation path for critical production issues.
  </Card>
</CardGroup>

## Before You Reach Out

Gathering the right information before contacting support helps our team reproduce your issue quickly and dramatically reduces back-and-forth. Before opening a ticket or starting a chat, collect the following:

* **Account ID** — found in **Settings → Account → Overview**
* **Affected resource IDs** — the unique identifiers of the records, integrations, or keys involved in the issue
* **Request IDs** — the `X-Request-Id` value from the headers of any failing API response (see below for details)
* **Steps to reproduce** — a numbered, step-by-step description of exactly what you did before the error occurred
* **Expected vs. actual behavior** — what you expected to happen and what happened instead
* **Error messages** — the full text of any error message, including HTTP status codes and response bodies

The more context you provide upfront, the faster we can resolve your issue — especially for API-related problems where a request ID lets us pull the exact server-side trace in seconds.

## Response Times

| Plan       | Email SLA                    | Chat Availability                         |
| ---------- | ---------------------------- | ----------------------------------------- |
| Free       | Community forum only         | Not available                             |
| Pro        | Response within **24 hours** | Business hours (9 AM – 6 PM local time)   |
| Enterprise | Response within **4 hours**  | 24/7 with dedicated phone escalation line |

<Info>
  Response time SLAs apply to the initial response from a support engineer. Resolution time varies depending on the complexity of the issue. Enterprise customers experiencing a complete service outage can use the emergency escalation phone number provided in their onboarding documentation to bypass the standard ticket queue.
</Info>

## Documentation & Self-Service

Many issues can be resolved quickly without opening a support ticket. The resources below cover the most common questions and problems our users encounter.

<CardGroup cols={2}>
  <Card title="Frequently Asked Questions" icon="circle-question" href="/help/faq">
    Answers to common questions about accounts, billing, API keys, storage limits, and security. A great first stop before reaching out to support.
  </Card>

  <Card title="Troubleshooting Guide" icon="wrench" href="/help/troubleshooting">
    Step-by-step instructions for diagnosing and fixing authentication errors, search issues, webhook failures, integration problems, and rate limit errors.
  </Card>
</CardGroup>

<Tip>
  When emailing support about an API error, always include the **`X-Request-Id`** header value from the error response. You can find it in the response headers of any failed API call — for example, `X-Request-Id: req_01hx4k9mz3fgv8j2p7qc`. This single value allows our team to locate the full server-side trace for your request instantly, often cutting resolution time from hours to minutes.
</Tip>