A small business had a contact form on its website that had worked fine for two years. Enquiries had gone quiet over the summer, which everyone put down to the season.
They had not gone quiet. The form had been silently failing to send for roughly six weeks after a routine plugin update changed how mail was dispatched. Submissions were being accepted, the visitor saw a thank-you message, and nothing arrived.
Why nobody noticed
Every party involved had a reasonable view. The visitor saw a success message and assumed they would hear back. The business saw a quiet inbox and assumed it was August. Nothing errored, nothing logged, nothing alerted.
This is the shape of the failures that cost the most: no symptom until somebody happens to check.
The fix, and the better fix
Repointing the form at proper authenticated mail delivery took under an hour. That was the immediate repair.
The more useful change was adding a monthly check: an automated test submission that confirms the message actually lands, and complains if it does not. The failure can still happen. It just cannot go unnoticed for six weeks.
Worth doing today
Fill in your own contact form, right now, and confirm the email arrives. It takes two minutes and it is the single highest-value check on any small business website.
Do the same for anything else that is supposed to email you: booking confirmations, order notifications, password resets. Anything that quietly stops is worse than something that loudly breaks, because loud breakage gets fixed the same day.
This is the same failure mode that makes a stopped automation so expensive. Nothing errors, nothing looks wrong, and the absence is invisible until someone happens to check.
It is also a good argument for knowing what is actually installed on your site, because form plugins are among the most commonly duplicated and least commonly tested.
Send yourself a test through your own contact form today. If it does not arrive, or you are not sure where it went, describe your setup.