> ## Documentation Index
> Fetch the complete documentation index at: https://docs.newport.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Get Help: Contact Google Support and Find Resources
> Learn how to get help from the Google team through live chat, email support, community forums, and the documentation when you run into issues.
The Google support team is here to help you succeed, whether you are blocked by a technical issue, need guidance setting up a complex integration, or want to share an idea that would make the product better. Before reaching out, the self-service resources below resolve the vast majority of questions quickly — but when you need a human, we are easy to reach.
## Self-Service Resources
Most questions have already been answered in the documentation. Start here for the fastest resolution.
Browse the full Google documentation, from quickstart guides and core concepts to advanced API reference material.
Find answers to the most common questions about billing, API usage, integrations, data security, and team management.
Diagnose and fix authentication errors, API failures, integration problems, data issues, and performance slowdowns.
Explore the full REST API reference, including endpoint descriptions, request/response schemas, and code examples.
## Contacting Support
When self-service resources do not resolve your issue, the Google support team is available through the following channels.
Live chat is the fastest way to get help from a real person. You will find the chat widget in the **bottom-right corner** of every page inside the Google app — look for the chat bubble icon.
* **Availability** — live agents are available Monday–Friday, 9 AM–6 PM ET. Outside of those hours, the chat bot can handle common questions and create a support ticket for agent follow-up.
* **Response time** — Pro and Business plan customers receive a first response in **under 5 minutes** during business hours. Free plan users receive responses within 2 business hours.
* **What to have ready** — your workspace ID (found in **Settings → General**), a description of the issue, and any relevant error messages or screenshots.
For non-urgent issues or when you need to share detailed logs and screenshots, email support is a great option.
* **Email address** — [support@google.com](mailto:support@google.com)
* **Response time** — you can expect an initial response within **24 hours** on business days. Complex issues may require additional follow-up time.
* **What to include** — your workspace ID, the steps you took before the issue occurred, any error messages you received (including full stack traces if available), and screenshots or screen recordings that illustrate the problem.
You will receive an automated confirmation email with a ticket number when your message is received. Use that ticket number in all follow-up correspondence to ensure continuity.
Enterprise customers receive a dedicated, elevated support experience designed for teams with mission-critical workloads.
* **Dedicated Customer Success Manager (CSM)** — your CSM is your primary point of contact for onboarding, strategic guidance, and escalations. Contact them directly via their personal email or Slack channel.
* **SLA-backed support** — Enterprise SLAs guarantee a first response within **1 hour** for critical (P1) issues and **4 hours** for high-priority (P2) issues, 24 hours a day, 7 days a week.
* **Priority escalation** — critical issues are immediately escalated to the on-call engineering team, with regular status updates until resolution.
* **Quarterly business reviews** — your CSM will schedule regular check-ins to review usage, discuss upcoming features, and ensure Google is delivering value to your team.
To get started with Enterprise support or discuss upgrading your plan, contact your account executive or email [enterprise@google.com](mailto:enterprise@google.com).
## Reporting a Bug
If you have found unexpected behavior that looks like a bug, a detailed report helps the engineering team reproduce and resolve it quickly.
Before reporting, try to reproduce the problem consistently. Note the exact steps that trigger the issue, including the page you are on, the action you take, and the result you observe versus the result you expected.
Click the chat widget in the bottom-right corner of the app to open a new support conversation. Select **Report a Bug** from the topic menu to route your report to the engineering team.
Provide a clear, numbered list of the steps to reproduce the issue. Include the URL of the page where the bug occurs, the browser and OS version you are using, and whether the issue is consistent or intermittent.
Attach any screenshots, screen recordings, or browser console logs that capture the issue in action. To open your browser's developer console, press `F12` (Windows/Linux) or `Cmd+Option+I` (macOS) and copy any red error messages from the **Console** tab.
Once your bug report is submitted, you will receive a ticket number and an acknowledgment from the team. For validated bugs, the engineering team will post a status update when a fix is deployed.
## Feature Requests
Have an idea that would make Google better for you and your team? We actively build our roadmap around user feedback. Share your suggestion, vote on ideas from other users, and follow the progress of requested features through the in-app feedback portal — click the **?** icon in the top-right corner of any page and select **Share Feedback**.
When contacting support, always include your **workspace ID** (found under **Settings → General**) and, for API-related issues, the **request ID** from the `X-Request-ID` response header. These identifiers allow the support team to locate your exact request in the server logs within seconds, dramatically speeding up diagnosis.