Find the step that stopped working

Published · Updated

Start with what you can see: the panel does not open, the account is not connected, or generation fails after the panel opens. Each points to a different part of the workflow. Save any reply text you want to keep before refreshing a social page.

The panel does not open with /rp

  1. Check that ReplyPilot is installed and enabled in the browser profile you are using. In desktop Chrome, open the Extensions menu or chrome://extensions.
  2. Open a comment field described in the platform guides. An unrelated text box, direct-message editor or mobile app may not use the same integration.
  3. Refresh the social tab after installing or reconnecting the extension, then try /rp once in the intended field.
  4. If it remains ordinary text or the panel opens against the wrong context, stop that attempt. Remove the command before manually posting anything and record the field where it happened.

Chrome's extension help explains how to inspect permissions and enabled status. Avoid uninstalling as your first check; it can remove local settings without identifying the cause.

The panel asks me to sign in or connect

Open the extension connection page in the same browser profile as the installed extension. Sign in if requested and read the connection result. Return to the social tab afterwards.

If website sign-in works but connection does not, report that distinction. It helps support separate an account problem from the extension handoff. See account help for sign-in recovery.

Generate is disabled or a request fails

  1. Wait for any current generation to finish. A request in progress can temporarily disable the button.
  2. Check Credits Used in your account and note any quota message in the panel.
  3. Confirm that the browser is online and can open ordinary websites.
  4. If the request fails, note the visible error and when it occurred. Try one simple text post to see whether the failure is specific to the original post or media setting.

Repeated clicks can make the problem harder to describe. If the draft is fluent but wrong, report it as a context or writing issue, with a redacted example; that is different from a failed request.

What if I use Brave or another browser?

Check the same profile, enabled-extension and site-access details first. Privacy controls or another extension may affect page behavior, but do not disable browser protections everywhere as a blanket fix. If you choose to test a site-specific change, record it and restore the setting afterwards. Tell support the browser so the behavior can be investigated accurately.

Send a useful support report

Email [email protected] with:

  1. The failing step: Opening the panel, connecting the account, generating, or reviewing the wrong context.
  2. The environment: Browser version, extension version and platform. Say whether the field is a main-post comment or a nested reply.
  3. What happened: Expected result, actual result, visible error and approximate time, with your time zone.
  4. A safe example: A public test post or cropped, redacted screenshot if it helps. Exclude credentials, sign-in links and private conversation content.

Include what you already tried. Keep any unfinished reply until the issue is resolved, and check the intended destination before you return to posting.