CHEVERTONMEDIAStart a brief

CHEVERTON MEDIA / ENQUIRY OPERATIONS

The form says “sent.” Where is the enquiry?

A confirmation on the page and a message in the right inbox are different events. Use this triage map to identify what is known, what remains unverified, and who should check the next handoff.

See the one-site check

A BOUNDED DIAGNOSTIC MAP

Follow the handoff, not the reassuring message.

  1. First, establish a safe test.

    Get the site owner’s express permission for one non-sensitive synthetic submission, the exact form and destination, a time window, and a person who can confirm receipt. Do not use a real customer message or test a payment, medical or financial intake path.

  2. If the browser rejects the form, stay at the page.

    Record the actual validation or error state, browser, device size and time. The issue may be at the form or page layer; there is no reason yet to infer that an email was handed off. Avoid repeated live submissions.

  3. If the page says “sent,” check that form’s notification rules.

    With authorized admin access, the agency or site owner should confirm that notification email is enabled and that the recipient is correct. WPForms documents its per-form notification settings, including the Send To address; its troubleshooting guide also covers conditional rules. Contact Form 7 documents the Mail tab. These are platform-specific checks, not proof of delivery.

  4. Then ask the destination owner to look.

    The designated person checks the agreed inbox, spam or quarantine and any authorized entry or mail logs for the matching synthetic marker and time. A provider or host may need to investigate after the form hands off mail. Contact Form 7’s FAQ specifically distinguishes a green success response from later non-receipt. Do not claim that a mail configuration change, plugin or new provider guarantees inbox placement.

  5. Close with one precise finding.

    Report confirmed received, confirmed not received at the agreed destination, or receipt unverified, with the evidence and the person who confirmed it. If the system cannot expose the handoff, say so and route the technical question to the authorized host, mail administrator or form maintainer. One successful test confirms only that moment; it cannot rule out an intermittent failure. If reliability over time matters, agree separate, expressly permitted checks on different dates and record each outcome. Repeated checks improve visibility but do not guarantee future delivery.

FOR A SITE OWNER / ONE-SITE PILOT

One path. A report someone can act on.

If you own the site, ask about a proposed $150 one-site pilot: one agreed, non-sensitive enquiry path, desktop/mobile/keyboard checks, one expressly permitted synthetic submission, receipt confirmation by your designated person, and a concise report. For WordPress or another CMS, the pilot is report-only: no admin, plugin, mail-server or deliverability repair is included. A small approved source repair of up to 30 minutes is possible only for an agreed editable static site. At most two hours of work; delivery within one business day after fit, scope, permission, access and payment are confirmed. We agree the exact scope before payment. This is a one-time pilot, not a subscription.

Site owner: ask about the pilot

The email action opens a draft in your own email app; this page sends and stores nothing. An inquiry is not permission to test. Do not email passwords, actual customer messages or sensitive form contents. No customer result, email-deliverability fix or recovered-lead guarantee is claimed.

Site owner? Read the one-site scope before asking ↗

Agency? See the agency-branded pilot and optional monthly plan ↗

Read the five-point form-check checklist ↗