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
Say what you expected
Then what happened instead, in that order. The gap between the two is the bug.
Paste the exact error
Redacted. The literal text beats a description of it every time.
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.
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.
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.
| Type | First response | Helps us most |
|---|---|---|
| Security report | Separate disclosure process | Email security@gobuildwp.com; the security page aims to acknowledge receipt within three business days. |
| Paid download or licence access | 1 business day | Have your purchase email ready. |
| Activation or update failure | 1 business day | Include WordPress, PHP and plugin versions. |
| Production-blocking defect | 1 business day | Say what breaks and how to reproduce it. |
| Usage or how-to | 2 business days | Check the help centre first - it is often faster. |
| Feature request | 3 business days | Logged to the backlog. No delivery promise. |