Why your confirmation emails land in spam

Mailbox providers are asking one question

Gmail and Outlook are not judging your copy. They are asking whether this message genuinely came from the domain it claims to come from, and whether mail from that domain has behaved well in the past. Both halves of that are things you configure once, in DNS, and then earn over time.

A site that sends confirmations through whatever default the hosting platform provides is failing the first half before the message is even written. The mail says it is from your business, and nothing cryptographically backs that claim, so it gets treated with the suspicion it has earned.

What actually has to be in place

• A cryptographic signature on every message, published in your DNS, so a receiving server can verify the mail really came from you.
• A sending address on your own domain — including the technical “envelope” address, which is invisible to humans and very visible to spam filters.
• Bounce and complaint handling that records every rejection and every spam report, because a sender who keeps mailing dead addresses gets throttled.
• Alerts on your sender reputation, so you learn about a deliverability problem from a monitor rather than from a customer.
• A warm-up period. New sending domains start untrusted and are granted volume as they prove themselves.

Make the email look like the site

Once mail is reliably arriving, the second half of the job is that it doesn’t look like a system artifact. The password reset, the booking confirmation, and the new-device alert are often the only things a customer receives from you between visits — and a bare, unstyled message from a no-reply address reads as either a bug or a phishing attempt.

I render those from the same brand tokens the website uses, so the colours, wordmark, and typography match. Same sender, same voice, same look. It costs nothing after the first time and it removes the flicker of doubt that makes people not click.

How to check yours in five minutes

Send yourself a booking confirmation at a Gmail address and a work Outlook address. Open the message details and look for the signature check passing. Look at the actual sending domain rather than the friendly name. Then look at your own bounce log — if you don’t have one, that is the finding.