The quiet version of a lost sale
You send a quote. You don’t hear back. You figure the customer went with someone else, or got busy, or changed their mind. Most of the time that’s true. But some of the time they never saw it — the email went to spam, and neither of you will ever know.
That’s the worst kind of problem, because nothing tells you it happened. No error. No bounce. The email just quietly doesn’t get read, and you’re left guessing why the job went cold.
Spam filters stopped reading your words
A few years ago, filters mostly looked at what was inside a message — certain words, too many links, a sketchy attachment. Write a normal email and it arrived.
That’s not how it works now. Google, Microsoft, and Yahoo decide whether to trust an email based mostly on where it came from — the reputation and setup of your sending domain — before they read a word of it.
So a plumbing company in Columbia sending an invoice from a personal Gmail gets judged the same way a stranger’s marketing blast does: by the sending domain’s record, not by the fact that the customer asked for that quote an hour ago.
“Sending domain” — what that means. It’s the part of your email address after the @.
[email protected]is a domain you control and can vouch for.[email protected]is one you share with millions of strangers, and you can’t prove to a filter that your messages are the legitimate ones.
What actually changed in 2024
In February 2024, Google and Yahoo changed the rules for sending mail to their users. The strictest requirements aimed at high-volume senders — roughly 5,000 messages a day — and forced them to authenticate their mail, offer one-click unsubscribe, and keep spam complaints low.
You’re probably not sending 5,000 emails a day. So the headline rules may not apply to you directly. But the change still matters, because it confirmed where the filters were already headed: mail from a domain that can’t prove who it is gets treated as guilty until proven innocent. A personal Gmail used for business can’t prove much, and neither can a domain that was never set up correctly.
The three checks that decide your fate
When your email arrives, the receiving server runs three quick checks on your domain. If they’re missing or wrong, your message starts the trip already distrusted:
- SPF — is this server allowed to send email for your domain?
- DKIM — was the message really sent by you, and not altered on the way?
- DMARC — what should happen to mail that fails the first two?
You don’t need to run these yourself to understand the stakes. If they aren’t in place, the filter has no reason to trust you, so it plays it safe and files you under spam. We wrote a plain-English walkthrough of SPF, DKIM, and DMARC if you want the detail.
How to check whether your email is getting filtered
You don’t have to guess. Four ways to find out, none of which cost anything:
- Send yourself a test. Mail a quote or invoice to a Gmail address and an Outlook or Hotmail address you don’t normally use, then see where each one lands. Spam folder or the “Promotions” tab? That’s your answer.
- Run a free deliverability test. Send one email to the address shown on mail-tester.com. It gives you a score out of 10 and a list of exactly what’s wrong.
- Read the receipt. In Gmail, open a message you sent, click the three dots, and choose “Show original.” You’ll see SPF, DKIM, and DMARC each marked PASS or FAIL. Three FAILs means receiving servers have nothing to trust.
- Ask three customers. “Did my last email land in your inbox or your spam?” Their answer is worth more than any tool.
Why it’s usually happening
The causes we see most often, in rough order:
- Business mail sent from a personal Gmail, Yahoo, or internet-provider address like
@sbcglobal.net. - A real company domain, but the three trust records were never set up.
- A new tool — an invoicing app, a CRM, a scheduler — started sending mail on your behalf, and nobody updated your records to allow it.
- No DMARC record, so failures get a free pass and your domain’s reputation quietly slides.
- Sending to a bought or stale list, which spikes spam complaints and drags your whole domain down with it.
Most of these have nothing to do with how you write. You could send the clearest, most polite invoice in Monroe County and still land in spam because the envelope it came in wasn’t trusted.
Put a number on it
Say you send 40 quotes a month and even one in ten lands in spam. That’s 4 quotes a month nobody reads. If one in four of those would have closed, at an average job of $800, that’s roughly $9,600 a year walking out the door — not because your price was wrong, but because the email never arrived.
That’s the kind of leak worth finding: real money, lost quietly, with no alarm going off.
What to do, in order
- Send business mail from a real domain — your own company domain, not a personal account.
- Set up SPF, DKIM, and DMARC for that domain, or have someone do it.
- List every tool that sends mail as you and make sure each one is authorized.
- Re-test with the steps above until you get clean passes across the board.
None of this is expensive. The expensive part is the year of quotes that didn’t arrive while you assumed business was just slow.
Where to start
You can check most of this yourself if you’re comfortable digging into DNS records. If you’re not — or you’d rather have someone confirm it before you assume it’s fine — that’s what our free email and domain check is for. We look at whether your mail is set up to be trusted, flag any gaps in your payment setup, and send you a written summary in plain language. No call required.
