Skip to main content
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

Community Forum

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.

Email Support

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.

Live 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).

Enterprise Support

Enterprise customers receive a dedicated support engineer, guaranteed response SLAs, quarterly business reviews, and an escalation path for critical production issues.

​
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

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.

​
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.

Frequently Asked Questions

Answers to common questions about accounts, billing, API keys, storage limits, and security. A great first stop before reaching out to support.

Troubleshooting Guide

Step-by-step instructions for diagnosing and fixing authentication errors, search issues, webhook failures, integration problems, and rate limit errors.
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.