GoBuildWP

Support

Open a support request. Tell us what went wrong.

Signing in keeps the conversation on one page, where you can reply in place. This form is for when you cannot sign in. A public request reaches the queue only after you use its email confirmation link, which helps reduce unsolicited requests.

Before you write

Three things that save a round trip

  1. Say what you expected

    Then what happened instead, in that order. The gap between the two is the bug.

  2. Paste the exact error

    Redacted. The literal text beats a description of it every time.

  3. Include your versions

    GoBuildWP, WordPress and PHP. Versions show at once whether Free is older than Pro accepts or the stack is below the minimum.

Never send account secretsNo passwords, application passwords, API keys, licence keys, card details or unredacted database exports. We will never ask for them. If you already exposed a credential, revoke it and contact support with a redacted description; do not assume automatic deletion. Billing, invoices, downloads and your licence key live in the customer portal.

For connection failures, add the Free and Pro versions, WordPress and PHP versions, AI client, authentication method, active safety profile and the complete error with credentials removed. For builder or integration failures, add the companion plugin and theme versions, and whether the same action works directly in wp-admin.

Sign in to your requests

Redact before pasting. We will never ask for a password, an application password, an API key or a licence key - do not send them.

If the request is accepted, a confirmation link is sent to your email. It reaches the queue only after you use that link; confirmation helps reduce unsolicited requests.

Response targets

What happens after you confirm

Ordinary support targets count from email confirmation, during 09:00 to 17:00 UTC, Monday to Friday. They are aims for a first human reply, not guaranteed deadlines or resolution times; request complexity, queue capacity and email delivery can affect timing. Attachments are not accepted; paste redacted text instead.

First-response targets by request type
TypeFirst responseHelps us most
Security reportSeparate disclosure processEmail security@gobuildwp.com; the security page aims to acknowledge receipt within three business days.
Paid download or licence access1 business dayHave your purchase email ready.
Activation or update failure1 business dayInclude WordPress, PHP and plugin versions.
Production-blocking defect1 business daySay what breaks and how to reproduce it.
Usage or how-to2 business daysCheck the help centre first - it is often faster.
Feature request3 business daysLogged to the backlog. No delivery promise.