Why your contact form emails end up in spam

Why a form email looks suspicious

A form service sends an email on your behalf. If the message claims to be from your own address but a different server sent it, receiving mail systems treat it the way they treat forgery, because it looks like forgery.

The message may also be thin: no greeting, a bare list of answers, a link or two. Short machine-written mail with an odd sender is exactly what filters distrust.

The filters are not personal. They weigh dozens of small signals, and a form email can collect several of them at once, such as a mismatched sender, a missing signature and a message with no text around the answers.

Reply-to and from are different jobs

The from address says who sent the message. The reply-to address says where your answer should go. A safe setup sends from an address the form service controls and sets the visitor's email as reply-to.

That way you press reply and write to the customer, and the mail system never sees a stranger pretending to be your domain. Some form tools get this backward by default.

Some form tools let you choose the from address and some do not. If yours insists on sending as your own address without proper records, switch it to the tool's own sender and rely on reply-to.

SPF and DKIM in plain words

SPF is a record at your domain listing which servers may send mail for it. DKIM adds a signature that proves a message was not altered. Both are short entries you add at your domain.

Your form or email provider publishes the exact values to use. Copy them as given, and do not guess. A wrong entry can break the mail you already receive.

Records are published in the place where your domain's settings are managed, which is usually your registrar or your DNS provider. Changes can take a while to spread, so test again after an hour.

A sequence of checks that finds the cause

Work through the list below with a test submission each time. Change one thing at a time so you know which change fixed it, and check spam and any quarantine folder every time.

A message that arrives in spam once may arrive normally the next time, which makes testing confusing. Test several times, and judge by where most messages go rather than by one result.

• Submit the form and look in spam, junk and quarantine
• Read the from and reply-to addresses on the received message
• Confirm the sending service is named in your SPF record
• Confirm the provider's DKIM record is published
• Try a different receiving address on another provider
• Check that the form actually shows a success message
• Ask the form provider whether the message was sent

Do not rely on email alone

Even a perfect setup can lose an occasional message. Keep a copy of every submission somewhere you can see it, so a missing email never means a missing customer.

Website Builder Studio keeps each lead on a Leads screen with a status and a note, and can also deliver to a CRM, Slack, Teams, email or any webhook. A second route makes silent failure far less costly.

A copy that you can see also lets you spot trouble early. If submissions appear on a Leads screen but never in your inbox, you know the form works and the email route does not.

Test it like a real customer

Submit the form from your phone, on mobile data, using an address that is not your own. Wait a few minutes, then check where the notification landed.

Repeat the test after any change to your domain or email settings. Our contact form guide and spam protection page cover the form side, so real messages stay separate from junk.

Ask a friend to try it too. Their provider may treat the message differently from yours, and a second view shows you whether the problem is your inbox or your whole setup.