Contact form failures
Contact form monitoring for leads your clients expect to receive
A contact form can thank the visitor and still lose the lead. MetricPoints submits the forms you configure and keeps the proof you selected. That proof is not the same thing as a message arriving in the client’s inbox.
What a form check can prove
An automatic check can submit an active form in a browser and record whether the page accepted it. Email proof depends on the path you choose: a MetricPoints inbox address, a visitor reply, or a copy of the lead notification sent through the same outgoing mail path as a real lead.
A verification inbox or a visitor reply does not prove delivery to the client’s business mailbox. A missing reply before a successful baseline means the reply path is unverified. It is not, by itself, a client mail failure.
WordPress adds context, not the message
When the WordPress plugin is connected, form and mail signals can sit beside the public check: the site attempted to send mail, a known form plugin recorded a submission, or cron and updates changed around the same time. Snapshots do not include submitted fields, email bodies, or recipients.
Supported application context includes Gravity Forms, WPForms, Fluent Forms, Formidable, and Contact Form 7. External form checks still run on sites that are not WordPress.
- Use a test recipient and the same mail server the real form uses.
- Keep the client’s real recipient in place when you add a notification copy.
- Read the form monitoring docs before you treat a receipt as inbox delivery.