Contact GoBuildWP. You reach the people who write the code.

Four ways to contact GoBuildWP, and what each one does with your message

There is more than one door, and they do not behave the same way. Picking the right one decides whether your message becomes a tracked request with a reference and a response target, or simply lands in a mailbox.

• Signed in at app.gobuildwp.com, under Support. This is the route for anyone with a GoBuildWP account, and the best one for Pro customers: the request is opened straight away with no confirmation email, the conversation stays on one page, and you reply in place. If the account has an active Pro licence linked, the request is marked for priority handling automatically.
• The support request form, for when you cannot or would rather not sign in. It needs only an email address you can read. Nothing reaches the desk until you click the confirmation link it emails you, and that link lasts 48 hours. Once confirmed, the request also appears under Support in any account that uses the same email.
• Email to the GoBuildWP support email address, support@gobuildwp.com, which the buttons on this page pre-fill with a subject line. It suits a short product or pricing question that does not need tracking.
• Email to security@gobuildwp.com for a suspected vulnerability. The security page explains the disclosure process. Requests in your account and through the form are private between you and the GoBuildWP team, but they run on support targets rather than the disclosure process, so keep vulnerability details for the email. Never post them in a GitHub issue, the WordPress.org forum or any other public thread, where they are public before a fix ships.

How quickly a request is answered

Requests opened through the form or the account carry a first-response target set by the type of request you choose. Targets are counted in business hours, which run from 09:00 to 17:00 UTC, Monday to Friday, so a request sent on Friday evening starts its clock on Monday morning. Public holidays are not modelled, and a business day means one working day of eight hours rather than a 24-hour period. For a form request, the clock starts when you click the confirmation link, not when you press send.

• Suspected vulnerabilities use security@gobuildwp.com and the separate disclosure process, which aims to acknowledge receipt within three business days.
• Paid download or licence access, activation or update failure, production-blocking defect: 1 business day each.
• Usage or how-to: 2 business days.
• Feature request: 3 business days, logged to the backlog with no promise that it will be built.

What changes for Pro customers

A Pro licence linked to your account under Licences halves each target, never below two business hours, and raises the starting priority by one step. The request is filed as GoBuildWP Pro whichever product you picked in the form. This happens because the account knows about the licence; the public form does not look licences up, so a Pro customer who uses it starts at the standard target. If you bought Pro with a different email from the one you sign in with, link that address on the Licences page first, and every later request benefits.

These are first-response targets: the time to a human reply, not to a fix. A reply may well be a question, which is why the evidence list higher up this page matters. Each round trip it saves is a full target period you do not wait for.

Contacting GoBuildWP before you buy

Pre-sales questions are welcome and get the same engineers as support. The useful version of the question is concrete. "Will GoBuildWP work with my site?" can only be answered with a list of caveats; "I run Elementor and WooCommerce on six client sites, connect from Claude Desktop, and want an agent to update product descriptions with my approval before each write" can be answered with a yes, a no, or the exact boundary.

Before writing, it is worth checking the parts you can check alone, because the answer will point you there anyway:

• Whether each plugin you rely on has an integration page, and which edition its abilities need.
• How your AI client connects, from its setup guide in the WordPress MCP section.
• Which tier fits: every Pro tier includes the same plugin features and differs by Pro site activations and Cloud allowances, as the pricing page shows.
• Whether you need GoBuildWP Cloud at all. It is optional; a client can connect to each site directly.

Start from wp-admin when the question is technical

For a connection or ability problem, the most useful thing to attach is produced by the plugin itself. Open GoBuildWP > Diagnostics, choose how your client signs in under "How do you connect?", press "Run diagnostics", and when anything is flagged press "Copy report for support". The copied text lists the site address, the GoBuildWP, WordPress and PHP versions, the connection method, any security or edge layer it detected, and each check with its result. It is designed to leave credentials out, but read it before pasting, because the site address and plugin list may still be things you would rather not share.

The support form does not take attachments, so paste the report and any error text into the message itself. For a bug in GoBuildWP Free that you can reproduce on a clean site, a public GitHub issue is often the better route: the fix then reaches every install, and other people hitting the same problem find it.

Corrections, credit and things we will not ask for

If something on gobuildwp.com disagrees with the plugin in front of you, the accuracy route is the one to use, and it is not a complaint channel: claims on this site are meant to be traceable to the plugin source, so a mismatch is a defect on our side. Include the page address, your Free and Pro versions, and the behaviour you saw. The about page describes how claims are checked and how corrections are recorded.

Whichever channel you choose, GoBuildWP will never ask you to send a password, an Application Password, an OAuth token, an AI provider key or a full licence key, and will not ask for administrator access to your site. A message claiming to be from GoBuildWP that asks for any of those should be treated as phishing and reported to support@gobuildwp.com.