Build business email around your own domain
An address such as hello@yourbusiness.example connects your email with the domain customers see on your website. It also gives you a consistent address to use as staff, responsibilities, or email providers change.
The address is only one part of the setup. Someone must own the account, monitor incoming messages, and keep the sending configuration working.
Choose addresses around responsibilities
A named mailbox suits an individual relationship. A role address such as enquiries@yourbusiness.example can work well when more than one person handles requests. Decide who receives those messages, who replies, and what happens when that person is away.
An alias usually delivers to another mailbox rather than providing a separate inbox. A shared mailbox or delegated access may be more suitable for a team. Check the provider's actual arrangement instead of assuming every address includes its own storage and login.
Keep ownership with the business
Record who controls the domain registration, DNS settings, and email administration. Those may be three different accounts. Use business-controlled recovery details, enable multifactor authentication where available, and store recovery information securely.
Give staff the access they need without sharing one administrator password. When someone leaves, review their permissions and arrange appropriate access to business correspondence. A provider change should not require tracking down a former contractor who owns the only login.
Configure authentication for every sender
SPF identifies authorized sending systems, DKIM provides a signature that receiving systems can verify, and DMARC adds domain alignment, reporting, and policy controls. Google recommends setting up all three in its email sender guidelines.
Inventory the services that send on your behalf: ordinary email, contact forms, invoices, newsletters, and booking confirmations. Follow each provider's current instructions. Have the complete configuration checked before tightening a DMARC policy; an overlooked legitimate sender can otherwise have delivery problems. Authentication helps establish legitimacy, but it does not guarantee inbox placement.
Treat website forms as a separate delivery test
A contact form can display a success message while its notification goes missing. Submit a real test enquiry and confirm delivery to the intended recipient. Check the reply action too: it should reach the person who made the enquiry.
Where supported, configure the form to send from an authenticated address on your domain and place the visitor's address in Reply-To. Do not assume that using the visitor's address as the sender will work reliably. Keep a record of the sending service so future website changes do not silently break it.
Plan the switch before announcing it
- Set up and secure the new mailboxes.
- Confirm sending, receiving, replies, and any migration of existing mail.
- Test forms, invoices, and other automated messages.
- Update the website, directory listings, signatures, and business materials.
- Monitor the old address during a planned transition.
Email hosting and website hosting do not have to come from the same provider. They do need clear responsibilities. When discussing website hosting and maintenance, ask how form delivery will be monitored and who handles email configuration. For help coordinating the website side, contact Web Design Just For You.
