SubmitSignal

Choose a form, review its public page and authorize one clearly labeled inquiry. SubmitSignal shows separate browser submission, WordPress acceptance and email-handoff evidence in WordPress. Start free with one website, one form and up to three manual checks per day. No card is required. Version 0.4.0 shortens setup: connected form controls load automatically, known public form pages are suggested locally, monitor names are supplied, and one explicit Check this form action can prepare a paused monitor and run its first authorized check. Daily monitoring and payment remain separate choices. SubmitSignal connects an administrator-authorized WordPress website to the hosted SubmitSignal monitoring service. It reports metadata about successful WPForms processing and WordPress mail-transport outcomes. The service can submit visibly labeled synthetic contact inquiries to forms the account owner explicitly selects. This is the official SubmitSignal WordPress connector. SubmitSignal, this plugin and the hosted monitoring service are owned and operated by Axtrel AI LLC. Visit the official service website or setup guide. This connector uses the canonical service API at https://getsubmitsignal.com. Setup, individually authorized checks, evidence, submission-review controls and the billing handoff are available inside Settings > SubmitSignal. Supported launch coverage is ordinary WPForms Lite contact forms. WPForms Pro is not included in supported launch coverage until acceptance testing with a licensed Pro installation is complete. The free plugin requires a SubmitSignal service account. The free service tier includes manual diagnostics for one website and one monitor, with up to three checks per day. Scheduled daily monitoring and automated email failure alerts require an active Solo or Agency subscription. Current availability and subscription pricing are shown on the service website. Paid launch enrollment is limited to US businesses with US billing. Solo monitoring is $19/month plus tax; Agency monitoring is $99/month plus tax. Install free and authorize your first check in WordPress. If you are unsure about fit, the optional free form review evaluates your answers without visiting or submitting your form. An actual test requires the website owner's authorization. Browser checks require the service's browser runner to be configured, and scheduled monitoring and email alerts also depend on the hosted scheduler and email service. The dashboard shows current availability. Installing this plugin alone does not start synthetic submissions or promise active scheduled checks. Supported first-release forms contain ordinary name, email, text and paragraph fields, with optional HTML, hidden fields and dividers. Payment, registration, uploads, signatures, custom choice fields and multi-step forms are excluded. CAPTCHA, external assets, custom validation, redirects and custom confirmations can cause an inconclusive result. Checks do not bypass CAPTCHA or other anti-spam protections. Synthetic inquiries use the label "SubmitSignal automated test" and the reserved example.com email domain. Existing autoresponders and CRM integrations may still run. Owners must use a suitable ordinary contact form and exclude labeled tests from reporting and downstream sequences. This plugin does not automatically suppress or change existing integrations. Mail handoff means WordPress's wp_mail_succeeded hook reported success. This is not proof that the intended recipient's inbox received the email. Custom mail providers which bypass WordPress hooks remain unverified. WPForms can send notifications asynchronously, so mail outcomes can arrive later than form acceptance. Optional test inbox receipts require connector 0.2.0 or later, a configured receiving service, the WordPress administrator's separate test-copy consent, and consent on the hosted monitor. A short-lived signed test authorization and one-use server claim permit a BCC only when every entered and processed field matches fixed synthetic test values. The complete synthetic notification, including template content and sender/recipient headers, is received by SubmitSignal's test destination at Resend. Ordinary visitor inquiries are not copied. Custom hidden values, attachments, transformed field values and asynchronous contexts without the current ticket remain unverified. Leave copies disabled if notification templates contain private static information. Test inbox receipt proves arrival at this one receiving provider only. It does not prove delivery to your own inbox, spam placement, another provider, or CRM. Missing receipts are not automatically failures. The original notification's recipients and body are not changed; an authorized test adds one BCC.

1. Install and activate SubmitSignal and WPForms Lite. Open Settings > SubmitSignal, accept the connection disclosure and choose Connect SubmitSignal. Sign in, review the website and account shown, approve and return to the same WordPress administrator session. No pairing code is needed and the form controls load automatically. The official website ZIP can be installed with Plugins > Add New Plugin > Upload Plugin.
2. Review the form and its public HTTPS page. WordPress suggests published pages containing a recognized embed; dynamic or theme embeds may require entering the URL yourself. Authorize one labeled inquiry and choose Check this form. It creates a paused monitor and requests one check; existing email and CRM automations may run. Review each evidence stage. An uncertain submission must be reviewed before any later check; deleting or recreating the monitor does not bypass a hold.
3. After a useful first check, choose optional daily monitoring: Solo $19/month plus applicable tax for one website, or Agency $99/month plus applicable tax for up to ten. Confirm US business/billing eligibility and supported use, accept the selected monthly terms, and complete payment securely on Stripe/Link. WordPress reads verified status on return. Choose to enable daily checks separately when paid access is confirmed. Cancel through Manage billing; uninstalling or disconnecting does not cancel a subscription.

Free diagnostics include one website, one form and up to three manual checks per day. Daily monitoring and automated failure emails require an active paid plan and operational services. See the short setup guide or ask for free setup help there. Existing older connections and subscriptions are preserved. Manual pairing remains an advanced option. WordPress must be reachable over HTTPS and expose its public REST API. Install per website on multisite; network-wide configuration is not provided.

0.4.0

• Shorten setup to connect, check one form and choose optional daily monitoring.
• Load verified form controls after approval and read verified status on checkout return, without automatic form tests or purchases.
• Suggest recognized public form pages locally and supply monitor names; preserve manual page entry when an embed is unknown.
• Combine paused monitor preparation and one explicitly authorized first check, preserving single-use attempts and uncertainty holds.
• Simplify billing declarations while retaining US eligibility, supported-use limits, exact-plan monthly terms and separate schedule permission.
• Preserve complete Stripe Checkout destinations, including opaque fragment state, without weakening host validation.

0.3.1

• Show meaningful evidence headings for current service stage names and older identifiers, while preserving failed, inconclusive and unverified results.
• Explain the required Refresh status step after account approval and the fields needed to create a paused monitor.
• Hide duplicate creation after the free monitor is configured and explain how to remove an untested mistaken monitor in the dashboard. Submission-review holds survive deletion and must never be evaded.
• Preserve explicit consent, private credentials, single-use actions and connection recovery behavior.

0.3.0

• Add session-bound sign-in approval and native WordPress administration without copying pairing codes.
• Keep management credentials server-side and require a separate grant for existing metadata-only connections.
• Add paused monitor creation, explicit manual checks, evidence, hold acknowledgment, pause/resume and bounded status refresh.
• Add explicit commercial consent and a validated Stripe checkout/billing handoff; no card details enter WordPress.
• Explain missing-form reasons and add an explicit inventory-only refresh.
• Use the canonical service API at getsubmitsignal.com; preserve synthetic-copy consent and ordinary visitor privacy.

0.2.2

• Add free dashboard and setup guide links before connection, with account sign-in and private pairing-code instructions.
• Add a Settings link on the Plugins page for administrators.
• Clarify directory installation, free manual checks, paid pricing and US launch enrollment in the readme.
• Improve the setup handoff without changing connection consent, monitoring, test submissions or test-copy behavior.

0.2.1

• Identify the official plugin and service owner as Axtrel AI LLC, with the plugin website at getsubmitsignal.com.
• Use the official domain for public privacy and terms links.
• Keep the connector API endpoint and monitoring and test-receipt behavior unchanged from 0.2.0.

0.2.0

• Add separately authorized synthetic-only test inbox copies, with signed expiring tickets and one-use server claims.
• Keep ordinary inquiries, mismatched values, attachments and unsigned/replayed requests out of test copies.
• Separate test-destination receipt from customer-inbox and CRM evidence.

0.1.1

• Use prepared table identifiers; WordPress 6.2 or newer is required.
• Reject malformed synthetic-run identifiers without changing them into valid IDs.
• Tested with WordPress 7.1.3; clarify free manual checks, paid monitoring and cache expiry after disconnect.
• Clarify WPForms Lite-only launch coverage; licensed Pro acceptance testing remains pending.

0.1.0

• Initial administrator-authorized WPForms metadata connector.
• Durable event retries and periodic form inventory heartbeat.
• Separate form acceptance and mail-transport outcomes, including asynchronous mail correlation.