Why contact form emails go to spam — and how to make enquiries easier to find

A customer fills in your contact form. The page says “Thank you.” You never see the message. It is an especially frustrating kind of lost enquiry, because both sides think the other side has the next step.

There are two separate questions to investigate: did your website actually save and send the enquiry, and did the receiving mailbox accept it into the inbox? Treating those as separate steps makes the problem much easier to diagnose.

Start with a sender you control

A common form setup uses the visitor’s email address as the message’s From address. That makes the notification look personal, but your website is not necessarily authorized to send mail for the visitor’s domain.

Use a verified sender on your own domain for the notification. Put the visitor’s address in Reply-To when the mailer supports it, so your response still goes to the right person. Keep the visitor’s name and message in the email body rather than using them to impersonate a sender identity.

Check authentication, not just the SMTP password

Email authentication helps a receiving system assess whether a message is authorized to use a domain. Gmail’s sender guidance discusses SPF, DKIM, and DMARC, including alignment between the visible From domain and an authenticated domain. A correct SMTP login alone does not establish that alignment. See the official Gmail sender guidelines.

If you use Brevo, follow the domain-authentication screen for your actual account. It provides the relevant Brevo verification, DKIM, and DMARC records. Brevo’s shared infrastructure has its own handling of SPF and return paths, so copying a generic SPF example from an unrelated tutorial is not a reliable substitute. Use Brevo’s domain-authentication instructions.

Trace one test enquiry from end to end

Send a new test with a unique phrase in its message, such as “Website enquiry test — Tuesday afternoon.” Then follow that exact test through each part of the system:

1. Confirm the website saved the submission or conversation.
2. Check whether a send attempt appears in the mail provider’s activity log.
3. Read its delivery status instead of relying only on the form’s success screen.
4. Search the destination mailbox, spam folder, and any filters or forwarding rules.
5. If a message arrived, inspect its original headers to review authentication results.

If no provider event exists, investigate the website’s queue, mail settings, or server connectivity first. If the provider reports a bounce, use its recorded reason. If delivery succeeded but the message went to spam, focus on authentication, sender reputation, content, and mailbox behavior.

Keep the notification simple

An enquiry notification has one job: help a teammate recognize and respond to a real customer. Use a descriptive subject, readable plain text or restrained HTML, and a clear link to the saved enquiry. Avoid turning every notification into a promotional message full of banners and unrelated links.

Protect your public form against automated abuse as well. Large amounts of junk can create noisy mail traffic and make genuine enquiries harder for your team to spot. Validation and a bot challenge should support the workflow without discarding the customer’s message silently.

Your mailbox should not be the only record

A more resilient design saves the enquiry before attempting notification delivery. The email is then an alert about a record that already exists, rather than the only copy of the customer’s request.

This is also the principle behind Botinto’s conversation inbox. Website messages are saved before AI processing. If an assistant is unavailable, or if a question needs a human, the message remains in the shared inbox. A teammate can read the context and reply in the chat.

That does not replace sound email configuration. It changes what an email failure means: a missed notification should prompt a check of the inbox, not make the underlying customer request disappear.

A small weekly habit makes a difference

During a launch, make a test enquiry part of your regular website check. Review failed jobs, look for unusual spam volume, and make sure someone owns the unanswered queue. Keep a simple record of what a successful test looks like.

If your immediate need is a structured form, explore FormGun on BizGun. If visitors need a useful first answer and an easy path to your team, see how Botinto’s website assistant works.