THE SUBMITSIGNAL FIELD GUIDE

From setup to a useful signal.

Connect your site, run an authorized test, and read the evidence. Here is what the first release supports—and where its visibility stops.

Connect your first site

You need administrator access to a public HTTPS site running WordPress 6.2 or later, PHP 7.4 or later, and WPForms Lite or Pro. The plugin verifies site access before it connects a site to your account.

Open your workspace. Sign in with ChatGPT, then select “Connect a site.”
Install the plugin. Download the ZIP below. In WordPress, go to Plugins → Add New Plugin → Upload Plugin. Upload and activate SubmitSignal.
Create a pairing code. Generate a one-time code from the connection panel. Keep it private: it expires in 15 minutes and can pair one site.
Connect from WordPress. Open Settings → SubmitSignal, review and accept the data sharing notice, paste the code, and connect.
Choose a contact form. Back in your workspace, add a monitor, choose the form, enter its public page URL, and explicitly authorize test submissions.
Run a first check. If the browser service is configured, select “Run check.” Read each stage separately and confirm the synthetic inquiry is excluded from your lead workflows.

Download WordPress plugin

This is an early access pilot. Your dashboard shows whether the browser service, alert service, and scheduler are configured. Free diagnostics include 1 website, 1 form, and up to 3 manual checks per day when the browser service is available. Paid Solo and Agency plans add daily monitoring and automated failure emails. Setup can be completed while services are unavailable, but checks will not be represented as active.

Keep the first check simple

Version one supports ordinary WPForms contact and inquiry forms on a verified WordPress site. Use a publicly reachable form with standard name, email, text, and message fields.

Outside the supported scope

Payment, purchase, signup, subscription, booking, and other consequential forms.
CAPTCHA and verification challenges. The testing service does not bypass them.
File uploads, complex conditional logic, unsupported required fields, login-protected forms, and multi-step workflows.
Forms that send the inquiry into a process with irreversible effects.
Recipient inbox inspection, CRM reconciliation, ad attribution, and visitor behavior analytics.

Tests are real submissions with clearly labeled synthetic content. Review all form notifications and downstream automations before enabling a monitor. Exclude synthetic tests from sales follow-up, conversion analytics, and advertising signals.

The test stops when it encounters unsupported inputs. An inconclusive result is preferable to submitting something the owner did not authorize.

Read the evidence, stage by stage

Browser submission: A remote browser loads the public page, finds the selected WPForms form, fills supported fields with synthetic data, and attempts submission.
WordPress acceptance: The authenticated plugin reports that WPForms completed successful processing for the matching test. Browser success text alone does not prove acceptance.
Email handoff: The plugin reports the result of WordPress’s mail attempt. A successful handoff is not proof of delivery to an inbox.
Inbox arrival: Unverified in this release. SubmitSignal does not connect to or read the recipient’s inbox.

What the statuses mean

Verified: evidence confirms that particular step. Failed: a failure was observed. Inconclusive: the check could not establish an answer. Unverified: no confirming evidence is available for that step.

A check’s summary is limited to the supported submission path. Missing events may indicate reporting delays or a disconnected plugin; they are not automatically counted as lost leads. Open an incident’s evidence, investigate, and rerun the check after a repair.

Explore three sample outcomes

Scheduled checks & alerts

Free accounts can run manual diagnostic checks; they do not receive scheduled checks or automated failure emails. An active Solo or Agency subscription enables checks at a 24-hour interval. Actual execution requires a connected browser provider and an operational scheduler. The dashboard separately displays service configuration and the most recent scheduler contact.

Pause a monitor to stop its scheduled checks. You can still run an authorized manual check when the browser service is available. Deleting a monitor removes its stored monitor records and history.

Automated failure emails require an active Solo or Agency subscription and a configured email service. Free accounts can read failure incidents in the dashboard. A configured alert service is not a guarantee of email delivery. Check the dashboard for the current incident record and status.

The WordPress plugin uses WordPress’s background scheduling to transmit queued events and refresh its inventory. On low-traffic sites, this can be delayed. A check may remain inconclusive while matching events are unavailable.

Let your agent inspect the evidence

SubmitSignal exposes an MCP endpoint through its hosted Sites integration. Account tools require the authenticated platform connection and use the same owner-scoped records as your dashboard.

Endpoint: https://submitsignal.brinybadge64.chatgpt.site/mcp

For the current pilot, use the authenticated Sites plugin connection provided with the deployment. The endpoint URL alone is not an access credential. Standalone MCP client authentication has not yet been verified for this release.

Useful requests after connecting

“List my monitored forms.”
“Explain the evidence from my latest form check.”
“Which checks have recorded failures?”

Your agent should keep a verified step, a recorded failure, and missing evidence distinct. Review the client’s permission prompts before authorizing a test or configuration change.

The pilot is not listed in an agent marketplace. Connection availability depends on the host and account permissions. Marketplace approval and agent recommendations are not guaranteed.

Keep your WordPress pairing code and plugin token out of conversations. Neither is an agent access credential.

Small payloads. Scoped access.

The plugin shares site identity, form IDs and names, timestamps, opaque event IDs, event types, and a synthetic test correlation ID when applicable. It does not transmit visitor names, email addresses, or message contents to SubmitSignal.

Browser tests process the public page and submit fixed synthetic content. Your form and existing notifications continue to be managed in WordPress. Avoid including personal information in a form’s name.

A site must prove possession of a temporary verification value before pairing. Connection tokens are scoped to that site. Disconnecting in WordPress removes the local connection and stops plugin transfers. Delete the site in your SubmitSignal dashboard to revoke its server token and remove hosted records. Your dashboard and account exports are scoped to your signed-in identity.

Export your stored records or delete your account data from the dashboard. Active subscriptions must be canceled before account data can be deleted. See the privacy notice and terms for more detail.

When a check needs attention

Pairing fails: Generate a fresh code, confirm the site uses public HTTPS, and check that its WordPress REST API can be reached. Private networks and redirects in the verification path are rejected.
No forms appear: Confirm WPForms is installed and an ordinary contact form exists. Refresh the connection from WordPress, then refresh your dashboard.
Run check is unavailable: The browser service has not been connected. The dashboard shows this explicitly. Creating a monitor does not provision a browser service.
No acceptance event: Check that the plugin is connected, the correct form was selected, and WordPress can make outbound HTTPS requests. Queued events may need time to arrive.
Email handoff fails: Inspect your WordPress mail configuration and mail provider logs. Repair the cause, then run another test. SubmitSignal does not modify your mail settings.
Inconclusive result: Inspect the recorded reason, supported-field requirements, and any verification challenge. Manually test the form if needed; do not assume an unsupported automated check proves a broken form.

Need a hand?

Email jarvismaximum+submitsignal@gmail.com with the affected site, approximate check time, and a description of the issue. Do not send passwords, pairing codes, plugin tokens, or real lead messages.

This early access pilot has no guaranteed support response time or service-level agreement.