The 15-minute lead-loss audit

The signal

The most expensive form failure is quiet. The page loads, the button works, and the confirmation screen appears. The owner sees no obvious outage. Meanwhile, a routing rule, mailbox filter, CRM connector, or notification address has changed. The visitor believes the request arrived; the operator never sees it.

That is why a useful lead-path check has two independent observations. The first is what the visitor sees in the browser. The second is whether the uniquely marked test arrives at the real business destination. If either side is missing, the path has not completed a round trip.

The five-step audit

Use a form you own or are expressly authorized to test. Do not defeat CAPTCHA, submit to a regulated intake, or use plausible customer details. The test record should be unmistakably synthetic so nobody treats it as a sale.

1. Write down the exact public form URL, the expected success text or destination URL, and the mailbox or CRM record that should receive the notification.
2. Create a unique marker such as FRT-20260831-01. Use a name like “Form Delivery Test” and a message that says “DO NOT CONTACT OR TREAT AS A LEAD.”
3. Submit once. Record the UTC timestamp, browser result, response text, and any redirect. A successful page is browser evidence only.
4. Search the real destination for the exact marker. Record arrival time and the provider message or record ID. Check spam, quarantine, and routing logs when applicable.
5. Classify the result: full pass, browser failure, destination failure, delayed arrival, or unsupported protection. Preserve the evidence and remove the synthetic record from sales metrics.

Copyable run record

Form URL: ____ Authorization owner and date: ____ Expected browser result: ____ Expected destination: ____ Unique marker: ____ Submitted at UTC: ____ Browser result and evidence: ____ Destination result and evidence: ____ Latency: ____ Final classification: ____ Next diagnostic: ____

Keep browser state and destination state separate. A single green field hides the exact failure you need to repair. If the page succeeds but the message is absent, inspect notification configuration, forwarding, authentication, suppression, and mailbox filtering. If the browser fails, inspect validation, scripts, network responses, and the form provider before touching email.

Limits and failure modes

A marked synthetic submission proves only that one controlled path worked at one time. It does not prove every real lead reached a person, that every browser behaves the same way, or that a staff member responded. Server acceptance of an email is also not proof that someone saw it.

Do not run frequent tests against a form without permission. Never solve or bypass CAPTCHA. Avoid healthcare, legal, employment, financial, payment, identity-document, emergency, or other sensitive forms. If the form requires a phone number, use a business-controlled test number and make the synthetic nature explicit.

A good schedule is conservative enough not to pollute reporting and frequent enough to catch meaningful drift. One run every six hours, with a single retry after a failure, is a testable pilot boundary—not a universal recommendation.

The owned tool, plainly labeled

FROM ELEVEN WILDCARDS — Eleven Wildcards operates FormRoundtrip. Its founding offer is intended to run one authorized public-form round trip for $29 per site each month, using a tagged test and separate browser/destination evidence. The paid service is not yet open; authorization, runner, inbox, billing, cancellation, and real-site verification gates remain incomplete.