Form notifications frequently fail silently because of how they are sent, and the visitor sees a success message either way. Sending through an authenticated service and storing submissions in the site are the two fixes.

Why this failure is worse than it looks

Every other website failure announces itself. A broken page produces an error, a slow site produces complaints, an expired certificate produces a warning.

A form that stops delivering produces a thank you message to the visitor, no error anywhere, and silence. The business concludes enquiries are down.

Cases running for weeks are common, and the enquiries lost during that period are unrecoverable because nobody knows who they were.

Why it happens

The server sends the mail directly

The default arrangement in many setups is for the web server to send notification mail itself. That mail frequently fails authentication checks, because the server is not an authorised sender for your domain.

Receiving mail systems then treat it as suspicious, which means it lands in junk or is discarded silently. No bounce arrives, so nothing indicates a problem.

The from address is the visitor's

A common configuration puts the person's own address in the from field so replies work. That makes the message appear to come from a domain the sending server has no authority to use, which is precisely the pattern spam filters exist to catch.

The correct arrangement is sending from your own domain and putting the visitor's address in the reply field.

A plugin or platform update changed something

Form and mail configurations break during updates, and because nothing tests them, the break is discovered by absence.

A filter is catching them

A rule created years ago, a junk classification that gradually became permanent, or a shared mailbox where somebody archived a batch.

The two fixes

Send through an authenticated service. Rather than letting the server send directly, notifications go through a proper mail service using authenticated credentials. That mail passes the checks and arrives.

This is a settings change on most platforms and it eliminates the largest cause.

Store submissions in the site as well as emailing them. Most form tools can save every submission to a database, which means a delivery failure no longer means a lost enquiry.

Those two together mean the mail arriving is a convenience rather than the only copy.

The storage option carries an obligation: submissions accumulate indefinitely unless a retention period is set, which is information you are holding without a purpose. Setting a deletion period is part of doing this properly.

The sender authentication records

Worth setting regardless, since they affect all your mail rather than only forms.

Records published in your domain's settings tell receiving systems which servers may send using your domain, and a signature confirms messages were not altered.

Without them, mail from your domain is more likely to be treated as suspicious, and anybody can send messages appearing to come from your business.

The related policy record instructs receivers what to do with messages failing those checks, and it needs setting carefully since a strict policy applied before all your legitimate senders are authorised will block your own mail.

Testing it properly

Not once, and not only from your own address.

  1. Submit the form from a phone, on mobile data, as a stranger would.
  2. Use an address on a different service from your own.
  3. Check junk as well as the inbox.
  4. Confirm the reply address works by replying to the notification.
  5. Check the stored copy exists in the site.
  6. Repeat after any update to the platform, theme, or form plugin.

The last step is the one that matters. Most form failures are introduced by a change, and a two-minute test after each one catches them the same day rather than the same quarter.

The monitoring version

For a business where enquiries are the whole revenue.

A monthly test submission, diarised, is the simplest arrangement and catches most failures within weeks.

Where a form is critical, sending notifications to two addresses on different services means a filter at one provider does not silence everything.

Some form tools can also alert you if no submissions have arrived in a set period, which is the closest thing to automated monitoring available for this.

The related silent failures

Worth checking at the same time, since they share a cause.

Order confirmations from a store, booking confirmations, password resets, and automatic acknowledgements all use the same mail path and fail the same way.

A business that fixed its contact form and left the rest on the old configuration has fixed one symptom of a general problem.

The visitor-facing side of this, meaning what somebody sees after submitting, is a separate matter covered in why people start your form and stop.

Frequently asked questions

Why is this failure worse than others?

It announces nothing. The visitor sees a thank you message, no error appears anywhere, and the business concludes enquiries are simply down.

What causes most form delivery failures?

The web server sending mail directly, which fails authentication checks because it is not an authorised sender for your domain, so messages are junked or discarded silently.

What is wrong with using the visitor's address in the from field?

It makes the message appear to come from a domain the sending server has no authority to use, which is exactly the pattern spam filters catch.

What are the two fixes?

Send notifications through an authenticated mail service, and store every submission in the site so a delivery failure no longer means a lost enquiry.

Does storing submissions create an obligation?

Yes. They accumulate indefinitely unless a retention period is set, which is information held without a purpose. Setting a deletion period is part of doing it properly.

When should forms be tested?

After every platform, theme, or plugin update, plus a diarised monthly test. Most failures are introduced by a change and caught only by absence.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Enquiries quietly down for a few weeks?

We test the form the way a customer submits it and check whether the notifications were ever arriving.

Start a Conversation