The forms your website uses are at the centre of how your audience engages with you. Whether that’s generating leads, processing applications, or taking orders, they need to work reliably, every time. And yet, for years, there’s been a quiet blind spot sitting right in the middle of that process.
The problem with “good enough” monitoring
Most website monitoring tools are pretty good at telling you when something is visibly broken. A page that won’t load, a server that’s gone down, a certificate that’s expired. These are the kinds of failures that announce themselves.
But what about the failures that don’t? What about the form submission that appears to work perfectly from the user’s perspective, fires off a confirmation message, and then silently fails to deliver anything to your inbox?
Traditional monitoring tools can’t tell us when a form submission email has failed to send, leaving you completely in the dark. There’s no alert, no warning, and no way to know until a prospect mentions they never heard back from you, or worse, until you notice the enquiries have quietly dried up.
For organisations that depend on their website to generate business, that’s not just an inconvenience. It’s a reputational risk and, in some cases, a compliance one too.
So we built our own solution
Because no off-the-shelf tool solved this problem adequately, we built one ourselves.
This month, we’re rolling out SMTP Status Monitoring across every website we look after. It works at the infrastructure level rather than the surface level, which means it catches problems that conventional tools simply miss.
Here’s what it actually does. It configures your site to send email through your own domain’s mail infrastructure, which immediately reduces the chance of your emails being incorrectly flagged as spam by receiving mail servers. It then watches every outbound email from your site in real time. And if something goes wrong at the point of sending, our team receives an immediate Slack notification so we can investigate and resolve the issue before it becomes a problem for you.
What this means in practice
Throughout March, we’ll be rolling this out across all the websites we look after. For most clients this will happen without any involvement needed from your side. We’ll only need to reach out directly if your setup requires specific configuration or permission from your email infrastructure.
It’s also worth understanding what the tool monitors and what it doesn’t. SMTP Status Monitoring works at the point of sending. Once an email leaves your site successfully, what happens on the receiving end sits outside our visibility. Email providers like Microsoft don’t report back to sending servers when they reject or filter messages, so if you ever notice an email that wasn’t received despite the monitoring being active, it’s worth asking your IT team to check for anything that may have been rejected or caught in a spam filter at their end.
This isn’t a limitation unique to our tooling; it’s simply how email infrastructure works across the industry. What we’ve done is close the gap that was previously invisible to everyone.
A small thing that makes a meaningful difference
The best infrastructure improvements are often the ones you never notice, because they prevent the problems that would have otherwise kept you up at night. SMTP Status Monitoring is exactly that kind of improvement: quiet, proactive, and working in the background so your forms keep doing their job without interruption.
If you have any questions about how this affects your website, just get in touch with your Client Partner and we’ll be happy to talk it through.
