Skip to content

Support

Use this page to diagnose common problems, collect the details our team needs, and contact ReachLLM support.

These guides resolve the most common setup and workflow questions:

You can also return to the ReachLLM dashboard and retry the affected action after refreshing the page.

Email team@reachllm.com when the documentation does not resolve the problem. Send the message from the email associated with your ReachLLM account when possible.

Include the following details:

  • Your ReachLLM account email.
  • The brand or workspace affected.
  • The page, integration, report, or workflow you were using.
  • What you expected to happen and what happened instead.
  • The approximate date and time of the problem, including your time zone.
  • The browser and device you were using if the problem happened in the dashboard.
  • A screenshot of the visible error when it does not contain private information.

If the issue can be reproduced, include the shortest sequence of steps that triggers it. Do not send passwords, sign-in codes, API keys, access tokens, private customer data, or full browser-storage exports.

For Google Search Console, Google Analytics 4, Bing Webmaster Tools, WordPress, GitHub, Webflow, Shopify, or MCP connection problems, include:

  • The integration name.
  • The account, property, site, or repository you intended to connect.
  • The step where the connection stopped.
  • The exact error text shown by ReachLLM or the external service.
  • Whether the connection previously worked.

Confirm that you selected the intended external account and that the connected user still has access to the property or site. If permissions changed recently, disconnecting and reconnecting the integration may be necessary.

For an AI visibility analysis, GEO audit, generated article, report, or publishing workflow, include the affected brand and the item name or page URL. Describe whether the item is waiting, failed, incomplete, or showing unexpected data.

For publishing problems, include the destination platform and the draft or page you attempted to publish. Keep the failed item in place until support has reviewed it unless it contains sensitive information.

For workspace access, invitations, plan access, or billing questions, include the account email and workspace name. You may include an invoice identifier, but do not send full payment-card or bank details.

If you believe an account or integration is being accessed without authorization, disconnect the affected integration where possible, secure the external account, and email team@reachllm.com with the subject Security issue. Do not include credentials or private tokens in the message.