Start with the emails your product owes someone.
Transactional email is not marketing. It is the mail your product has already promised: the password reset someone is waiting for, the address confirmation that proves who they are, the receipt for what they just paid for, the alert about the change they made. Write down the list your product actually depends on, and treat anything outside that list as a decision rather than a default.
Send from a domain you control.
A message from a free mail address is harder for receiving services to trust and harder for your users to recognise. Verify the domain you send from and publish the authentication records your dashboard lists. If a message is a reply to something a person sent, set the reply-to address to a route your team actually reads.
Give every message one job.
A message that asks for one action gets that action. A reset link, a confirmation, a receipt, a notification about a change. When one message tries to welcome, explain and sell, the recipient cannot tell what you want from them, and the result is a message nobody acts on.
Test the paths your users will actually take.
Send to an address you control and look for it in the inbox and in the spam folder. Check the sender name, the reply behaviour and the link before you let the flow reach real users. Your delivery activity view records what happened to each send, so the check is part of the work rather than a one-off.
By the WazobiaMail team at Bonifade Technologies.
← Back to the guides