Your Main Domain or a Sending Subdomain: Where Should Your Business Email Come From?

You wrote a good email. The subject line is right, the offer is clear, and it goes to people who asked to hear from you. Half of them never see it, because it landed in spam, and nothing you wrote had anything to do with it.

Whether an email reaches the inbox is decided before anyone reads a word. Gmail, Outlook and Yahoo look at where the email came from, whether that address can prove it is really you, and how people have reacted to email from that address before. Get those right and your emails arrive. Get them wrong and the best copy in the world goes unread.

This guide explains the part most small businesses never get told: what a sending domain is, the difference between sending from your main domain and a sending subdomain, when each one is the right call, and the single DNS record that quietly costs a lot of businesses their inbox placement.

Why the address your email comes from matters

Every email has a return address, and inbox providers treat it the way a bank treats a signature. An email from hello@yourbusiness.com that can prove it really came from yourbusiness.com is trusted. An email that claims to be from you but can't prove it looks exactly like the scam emails that pretend to be your bank, and it gets treated the same way.

There is a second reason. Your clients recognize your name and your domain. An email from your own address looks like it came from you, because it did. An email from a shared sending service address looks like marketing before anyone opens it, and people are quicker to ignore it or mark it as spam.

What a sending domain is

A sending domain is the domain your emails are sent from and signed as. Setting one up means adding a few records to your domain's DNS, the public settings that tell the internet how your domain works. Three records do the heavy lifting:

• SPF lists the services allowed to send email for your domain. When an email arrives claiming to be from you, the inbox checks the list.
• DKIM adds a digital signature to every email. The inbox checks the signature against a public key on your domain, which proves the email wasn't forged or changed on the way.
• DMARC tells inbox providers what to do when an email fails those checks, and shows that you are paying attention to your domain.

None of these touch your inbox. Your normal email keeps arriving exactly as it does today. They only affect how the emails you send are checked.

Domains and subdomains, explained simply

Your domain is the name you own, like yourbusiness.com. A subdomain is a name that lives under it, like mail.yourbusiness.com or news.yourbusiness.com. You already own every subdomain of your domain, so creating one costs nothing and needs no new purchase.

Think of your domain as your building and a subdomain as a suite inside it. Mail to the suite still arrives at your building, and it still carries your name. But the suite has its own mailbox, so what happens with the suite's mail can be kept apart from the rest of the building.

That separation is the whole point. Inbox providers keep a reputation score for each sending address, built from how people react to its emails: opens and replies push it up, spam reports and bounces pull it down. A subdomain builds a reputation that sits alongside your main domain's rather than on top of it.

When to send from your main domain

Sending from your main domain, like hello@yourbusiness.com, makes sense when:

• Your domain already has a good history. If you have been sending normal email from it for years, inbox providers already know it, and there is nothing to warm up.
• You mostly email people who know you. Booking confirmations, reminders, invoices and a newsletter to clients who signed up rarely draw spam reports.
• You want the simplest setup. One address for everything, and the one your clients already recognize.

The trade off is shared risk. Every email you send from your main domain adds to or takes from the same reputation your everyday inbox relies on. If a campaign ever draws a pile of spam reports, the damage lands on the domain you use to talk to clients one to one.

When a sending subdomain is the smarter choice

A sending subdomain, like hello@mail.yourbusiness.com, is the better choice when:

• You reach out to people who don't know you yet. Emailing a list of venues, planners or businesses you found carries more risk of spam reports than emailing your own clients. A subdomain keeps that risk away from your main domain.
• You send a lot of marketing. Regular newsletters, promotions and campaigns build their own reputation, separate from your personal emails.
• Your main domain is precious. If losing inbox placement on your main address would hurt, say because every client inquiry and every contract runs through it, protect it.

The trade off here is time. A subdomain is new to inbox providers, so it starts without a track record. It is not a complete stranger, because providers give some weight to the main domain it sits under, but it still needs a gentle start.

How to warm up a new sending address

Warming up means building a good reputation before you send in volume. It takes a couple of weeks and a little patience:

• Start with people who know you. Past clients and newsletter subscribers open and reply, and those replies are the strongest good signal there is.
• Start small and grow. A handful of emails a day in the first week, more in the second, then your normal volume.
• Ask a question. An email that invites a reply earns replies, and one real reply does more for your reputation than a lot of emails nobody opens.
• Space your sends out. A batch that goes out one email every couple of minutes looks like a person working through their inbox. A thousand emails in one second looks like a blast.

The record most small businesses are missing: DMARC

Plenty of businesses set up email years ago, got SPF right because their email provider told them to, and never added DMARC. Gmail and Yahoo now expect anyone sending in volume to have one, and without it your emails are more likely to be filtered.

The good news is that the safe version is one line. Add a TXT record named _dmarc with the value v=DMARC1; p=none;. The p=none part means it only watches and never blocks anything, so it can't stop your normal email from arriving. It simply shows inbox providers that your domain is set up properly.

One rule: a domain can only have one DMARC record. If yours already has a TXT record named _dmarc, leave it alone rather than adding a second.

Common mistakes that stop a domain verifying

• Typing the whole name. Most DNS hosts, including GoDaddy, Namecheap and Cloudflare, add your domain to the end of the name for you. Type send, not send.yourbusiness.com, or the record ends up as send.yourbusiness.com.yourbusiness.com and is never found.
• Retyping long values. The DKIM value is a long string of letters and numbers, and one wrong character breaks it. Always use the copy button.
• Changing your mail records. Sending setup never needs you to touch your MX records. If you are editing MX, stop, because that is what delivers your inbox.
• Expecting it instantly. New records usually check out within minutes, and occasionally take up to an hour to be seen everywhere.

Setting it up in ClientBranch

In ClientBranch, go to Settings, then Email domain. Enter your domain, then choose where your emails come from: a sending subdomain, which is recommended and uses mail by default, or your main domain. Pick the part before the @, like hello, and click Connect domain.

ClientBranch gives you a short list of DNS records, each with its own copy buttons. Add them at your DNS host, come back, and click Verify once. Each record shows its own status, and the page checks again by itself every thirty seconds until your domain turns Verified. You don't need to keep clicking, and you can close the page, because verification finishes in the background.

From then on, every email ClientBranch sends for you goes out as your address and properly signed: booking confirmations, reminders, invoices, newsletters, automations and AI Outreach. Replies come straight back into your Conversations inbox, threaded against the right contact.

The short version

Send from your own domain, because email from you should look like it came from you and be able to prove it. Use your main domain if it has a long, clean history and you mostly email people who know you. Use a sending subdomain if you reach out to new people or send a lot of marketing, and give it a couple of weeks to warm up. Whichever you choose, add the one line DMARC record if you don't have one. It takes five minutes, and it is often the difference between the inbox and the spam folder.