Keep permission and message purpose visible before sending.

Treat each audience as its own operational decision

A regional label does not explain why a person expects your message. Document the contact source, the intended message category and the information available to the reviewer. This matters when a team receives a spreadsheet from another department or inherits an old mailing list without its original context.

Keep the source system and responsible owner in the handoff. Use your controlled internal records for contact-level evidence and use the public planning worksheets only for generic notes. If the evidence is incomplete, assign a review action before importing or launching a promotional campaign.

Choose the country guide for your immediate task

Classify the message before choosing a template

A receipt, a service interruption notice and a new offer are different communication tasks. Write the essential purpose first and identify whether promotional material has been added. Do not assume that an existing customer relationship makes every future message appropriate for every recipient.

Keep a simple content inventory: message name, trigger or audience, necessary information, promotional blocks, review owner and suppression decision. This is an operational aid for your team. The applicable legal classification depends on the actual facts and should be checked against the relevant local guidance.

Protect exclusions during a migration

Plan how unsubscribe, bounce and other exclusion records will move with the contact set. Compare counts and sample the mapping in a controlled environment before resuming live work. Record the cutover boundary so that the old and new systems do not both release the same campaign or automation.

A successful file import is not the end of the migration. Review the sender details, destination links, reply address and recurring workflows. Give one owner the authority to pause release while the team resolves an inconsistency. Retain enough migration evidence to explain what changed and when.

Budget for the sending model you will operate

SendMailOS separates the platform subscription from a customer-paid VPS. Connected own-server sending starts at €12/month and has no monthly platform email quota for messages actually sent through that server. Hosted delivery instead uses the allowance included in the chosen plan.

A lower subscription price does not remove infrastructure work. Review provider policies and outgoing SMTP access, plan warm-up, and decide who responds to queue or reputation issues. Capacity, safety checks, fair-use rules and other plan limits remain relevant. The calculator helps separate costs; it does not quote a VPS or guarantee a volume the server can deliver.