The call that changed how I think about contact forms
Last year an agency owner rang me, slightly embarrassed. “We probably did something stupid,” she said. “Inbound leads from the site just… stopped.”
I opened the contact page. Filled in the form. Got the thank-you message. Checked the SMTP plugin in WordPress—green checkmarks everywhere. She tried from her phone. Same result. “See? It works.”
Except it did not. Messages were leaving the browser and dying somewhere between wp_mail() and the client’s shared inbox. No bounce alerts. No error in the UI. The form was lying politely.
“Works on my machine” is a category error
We borrowed that phrase from software development, but contact forms are worse. A successful HTTP response only means the website accepted your input. It does not mean:
- the mail relay authenticated correctly
- the recipient domain published the right SPF/DKIM/DMARC
- the message survived the spam folder
- the CRM webhook fired
- anyone on the team would notice if any of the above failed
I had been maintaining WordPress sites for decades. I knew this intellectually. That call made it visceral. The agency had shipped a redesign, updated plugins, and moved SMTP providers in the same week. Every piece looked fine in isolation.
What I actually do now before I say “you’re good”
I still click through forms manually when something feels off. But I also want proof I can show a client without waving my hands:
- Run a real submission with honest test data—not a curl against an API nobody uses.
- Capture what the browser saw: screenshots, timeline, any challenge pages.
- Confirm whether the expected notification arrived, or document that it did not.
That third step is the one most “form testers” skip. They stop at the thank-you page. For a business that lives on inbound leads, that is like testing a doorbell by pressing the button and never checking if anyone heard it.
Why this became FormReceipt
I did not set out to build another monitoring SaaS. Uptime tools already ping homepages. Security scanners already look for malware. What was missing was a narrow, boring product: verifiable proof that a contact form still delivers.
FormReceipt runs scheduled test submissions against the same forms your customers use. You get a timeline, screenshots, and a clear pass/fail—not a vague “looks OK from here.”
If you maintain client sites, you do not need more dashboards. You need one question answered reliably: did the inquiry actually arrive?
That is the question I stopped trusting my own browser to answer.