When a contact form service goes down, how do you keep the leads?

On the evening of November 4, 2026, the service that delivers the messages from our website forms stopped working, and nothing on the site showed it. I found out by accident, because I tried to fill out our own form on my phone and the lead never arrived.

This post explains what happened, how it was caught, and what we changed so a lead cannot disappear the same way again. If you run a contact form on your own website, the same thing can happen to you.

What happened to our website forms?

Many websites, including the ones we build, send form submissions through an outside lead submission company. The visitor fills in the form, the page hands the message to that service, and the service emails it to the business owner. It had worked for months.

At about 5:30 PM Pacific on November 4, that service began returning a server error (HTTP 522, which means the service's own server stopped answering). The error came from their side, and it hit every website that used them at the same moment. I tested the address from a plain command line, with none of our page code involved, and it failed the same way. As I write this on the morning of November 5, it is still failing.

The part that matters for a business owner is what the visitor saw. On some pages the form appeared to accept the message and then did nothing. The visitor believes the message went through, and the owner never receives it.

How did we find the problem?

By chance. I opened our homepage on my phone, tapped the demo button, filled in the form, and sent it. It behaved strangely, and nothing arrived in my inbox. If I had not been testing it myself at that moment, the failure could have run for days.

That is the same lesson I wrote about in an earlier post on testing your contact form: a thank-you screen proves nothing. Only a submission that lands in your inbox counts.

Why did a second check matter?

I had already checked the forms and they passed. Claude Desktop, the AI assistant I work with, still recommended a second check. It was right to. A form that worked when you tested it can fail an hour later, because the service behind it is not under your control.

The second look is what exposed the outage the same evening. A test is a snapshot, and the form has to keep passing for as long as it is on your site.

What was the fix?

We added our own backup route using Google Apps Script. Apps Script is a small program that runs inside a Google account, and it can receive a form submission, write it into a Google Sheet, and send an email, all without a third-party form service in the middle.

Each form now works in this order:

1. The page sends the submission to our own Apps Script first. 2. The script saves the lead as a new row in a Google Sheet and emails the business owner, with a copy to us. 3. If the script is unreachable, the page falls back to the lead submission company, as before. 4. If both fail, the visitor sees an error message with a phone number, instead of a false thank-you.

We also added a hidden spam trap field to every form, so automated bots that fill in every box are quietly dropped instead of reaching the inbox.

Situation	Before	Now
Lead submission company working	Lead emailed	Lead saved to the Sheet and emailed
Lead submission company down	Lead lost	Lead saved to the Sheet and emailed
Both routes down	False thank-you	Visitor told to call

The backup went live across our own pages first. We then rebuilt the same route for the client sites that depended on that company alone. Clients whose forms already ran on their own scripts were never affected.

How can you protect your own website forms?

Start with the check, then add a second path.

• Submit your own form from your phone this week, and confirm the lead arrives in your inbox and not in spam.
• Find out where your form sends its data. If one outside service is the only path, that service is a single point of failure.
• Ask whether the form shows a real error when delivery fails. A form that always shows "thank you" will hide an outage from you.
• Repeat the test after any change to your site, and a few times a year even if nothing changed.

You can run a broader check on your site with the website audit, which looks at security, mobile speed, schema, and indexing.

Why does this matter for a local contractor?

For a service business, one inquiry can be a full job. If a homeowner in Lake Elsinore or any other town fills out your form and hears nothing back, they call the next contractor on the list. You never learn that the lead existed, so you cannot even count the loss. Reliable delivery is part of the site, the same as the design.

Sun City Marketing builds custom HTML websites for contractors and service businesses. See our work at suncitymarketing.org.