Email and domains

Invoices and newsletters need different email journeys

Separate essential account messages from marketing. Handle delivery failures and unsubscribing without losing important notifications.

The CloudCity teamPublished 2 min read

An order confirmation and a promotional offer arrive in the same inbox but serve different purposes. One responds to a customer action; the other promotes something. Mixing their content and recipient lists makes preferences and sending reputation harder to manage. Start by classifying messages according to why they are needed, rather than which application generates them.

Define essential messages

Password resets, request confirmations and relevant notices about a purchased service should be assessed by their actual purpose. Do not label every announcement “transactional” to bypass marketing preferences. Establish the appropriate basis and notice for each category. If a message works without the promotional banner, keep it focused on the customer’s action.

Separate preferences

Customers should understand what they are subscribing to and how to stop marketing. Withdrawing a commercial preference should not prevent password recovery or essential service information. Avoid preselected consent boxes. Keep a record of the choice and follow the rules applicable to the channel and business relationship, which may be more specific than general personal data rules.

Use a recognisable identity

A consistent sender name, authenticated domain and monitored reply address help establish trust. The subject should describe the message: an invoice, a confirmation or an action required. Avoid artificial urgency. For sensitive information, direct the customer to their secure account instead of putting unnecessary documents and personal details in the email itself.

Monitor delivery, not just sending

A server accepting a message does not prove it reached the inbox or was read. Monitor rejections, invalid addresses and provider restrictions. Avoid repeatedly sending to nonexistent destinations. Retry logic should prevent duplicate notifications and give the team a clear explanation when delivery cannot continue. Logs should not expose sensitive message content.

Check the message on a phone

Keep one main purpose, readable text and an accessible button. The logo needs an accessible address and alternative text, while essential information should remain clear with images blocked. Include company identity and relevant contact details. For marketing, test unsubscribing too; do not hide it inside an image or unreadable text.

Sources and further reading

A CloudCity editorial guide informed by the documentation below. Check the official source for rules and procedures that may change.

Back to the blog