Form monitoring for WordPress agencies

Know your client's form is dead before the client does.

FormVigilant sends a labelled test through every client contact form, every day, and proves it arrived in an outside mailbox. You get the alert in minutes, the client gets a monthly report with your logo on it.

Northwind Digital · 42 sites · live
Healthyacmeplumbing.comL1L2L3L4L512 min ago
Failingbrightsmiledental.coL1L2L3L4L53 h ago
Healthynorthsidelaw.comL1L2L3L4L541 min ago
Testingpinecrest-roofing.comL1L2L3L4L5running
Contact form on brightsmiledental.co is failing at L4. SMTP accepted the message but nothing reached our mailbox. Alert sent 02:10, 3 min after the first failure.
Works withWPFormsGravity FormsContact Form 7Fluent FormsFormidableNinja FormsElementor Pro
The problem

Your uptime monitor says green. The client hasn't had a lead in four days.

A 200 OK proves the page loads. It does not prove the submit button works after a plugin update, that the SMTP plugin still has valid credentials, that the host's mailer isn't blocklisted, or that the notification didn't land in spam. Forms fail silently in all four places.

Plugin update breaks submit

A form-plugin, theme or CAPTCHA update changes the handler. Visitors see a spinner; nothing is saved.

SMTP credentials rotate

The host or provider rotates an API key. wp_mail returns true; the provider rejects the message.

Domain reputation drops

A DNS change drops DKIM. Mail is accepted upstream and silently discarded downstream.

Spam filter eats it

The notification arrives, in the client's junk folder, where nobody looks.

How it works

A real test, from inside WordPress, verified to a real mailbox.

  1. Install the connector

    One plugin from wordpress.org, one pairing code. It lists every supported form on the site.

  2. Submit through the plugin's own API

    No fight with CAPTCHA or bot protection. The entry is labelled and CRM, autoresponder and SMS actions are suppressed.

  3. Follow the message out

    We watch wp_mail, the SMTP plugin's log and the provider, then wait for the message at our own mail server.

  4. Alert, then report

    Email, Slack, Teams, SMS or webhook within minutes, with the stage that failed. A branded PDF every month.

See the full verification model
Evidence, not a green tick

Every result says exactly what was verified.

Five levels, from "the plugin accepted it" to "it is in the client's actual inbox". The dashboard, the alert and the report all show the level, so nobody mistakes a transport success for a delivered lead.

L1Submission accepted · the form plugin processed it
L2Entry recorded · the entry exists in the plugin
L3Transport confirmed · SMTP provider accepted it
L4External delivery verified · it reached our mailbox
L5Destination verified · it is in the client's inbox or CRM
  • L1 Submission accepted · 0.6 sWPForms processed the entry in test mode
  • L2 Entry recorded · 1.1 sMarker fv_9k2m7x found in entry #4812
  • L3 Transport confirmed · 2.4 swp_mail succeeded via Postmark, message id 7f3a…
  • L4 External delivery verified · 41 sArrived at mx.formvigilant.com · SPF, DKIM, DMARC pass
Northwind DigitalFORM DELIVERY REPORT · SEPTEMBER
acmeplumbing.com

All 3 forms delivered 100% of 90 tests, verified to an independent mailbox. No incidents.

90
tests
0
incidents
38 s
median delivery
Retainer insurance

Proof your care plan is worth paying for.

A monthly PDF with your logo, in plain language: what was tested, what was delivered, what you fixed. A client status page under your domain. FormVigilant is never mentioned unless you want it to be.

Everything else you expect

Built for 5 sites or 500.

Incidents, not noise

One incident per failing form, with retries, dedup, acknowledge, snooze, assign and an escalation ladder to the owner.

Alerts where your team lives

Email, Slack, Microsoft Teams, Discord, SMS, webhooks. Daily and weekly digests.

Root-cause runbooks

Every reason code comes with the three checks that fix it most often, from SMTP logs to DKIM.

Client portal and status pages

Read-only health pages per site, branded and on your own domain, with report downloads.

Team, roles, 2FA, SSO

Owner, admin, technician, viewer. Enforce two-factor. SAML on request.

API, Zapier, WpClientHub

REST API with scoped keys, Zapier and Make triggers, and a two-way link with WpClientHub ticketing.

Pricing

Priced per site, not per form.

Full pricing and add-ons
Starter
$29/mo

5 sites · 15 monitors · daily · L4

Start free
Agency
$79/mo

25 sites · 100 monitors · every 6 h · client reports, portal, Slack

Start free
Agency Pro
$179/mo

100 sites · 500 monitors · hourly · white-label, SMS, status pages

Start free
Enterprise
Custom

250+ sites · 15 min · SSO · dedicated support

Talk to us
FAQ

Questions agencies ask first.

Will clients see test submissions?

Tests go to a separate FormVigilant mailbox that we append on test runs only. The client's own recipients still receive the test unless you route it; the subject is prefixed [FormVigilant test] so it is easy to filter. Test entries can be deleted automatically after verification.

Does it trigger my client's CRM or autoresponder?

No. The connector sets a test flag that suppresses CRM feeds, autoresponders, SMS and Zapier actions on every adapter that supports it. Where a plugin cannot suppress an action, the form is marked and you confirm before monitoring it.

What about CAPTCHA, Turnstile and honeypots?

We submit through the form plugin's own API from inside WordPress with a signed connector token, so bot protection is not in the path.

Does FormVigilant read real visitor submissions?

Never. The connector only handles the labelled test entry and reports mail events. No names, emails or message bodies from real visitors leave the site.

I use WpClientHub. Is this included?

Yes, FormVigilant Agency is included with WpClientHub Agency and Pro. Link the accounts under Integrations.

Your first verified test takes under ten minutes.