DMARC: start at none, read the reports, then tighten
DMARC tells receivers what to do when a message fails authentication. Publishing reject before you know who sends as you is how legitimate mail disappears.
Email templates fail when they sound like templates. Here are the six worth saving for a small business, and the structure that keeps them short and human.
Email templates are supposed to save time, and the badly written ones cost it: the recipient reads two lines, senses a form letter, and either ignores it or replies asking what you actually want. The saving comes from templating the structure, not the personality.
A small business needs about six. Everything beyond that gets written once and never found again.
Every template needs one blank the sender must fill in: a specific detail from the actual conversation. It is the sentence that stops the message reading as a form letter, and making the field impossible to skip is the whole trick.
In Ettex Mail, reusable replies live next to the inbox, and sixteen transactional layouts cover receipts, confirmations and notifications — the messages that must be plain and must arrive. Per-address signatures keep branding consistent across your domain mailboxes, scheduled send lets you write at midnight and deliver at nine, snooze and follow-ups stop a thread being forgotten, and filters and rules route incoming mail before it needs your attention. Mail from hosted domains is signed with DKIM and sent over real SMTP, which is what keeps a well-written template out of the spam folder.
Templates rot. Prices change, the person who signed off leaves, the process gains a step. Reread the set every six months and delete the ones nobody has used — a library of thirty templates is a library nobody searches. And keep them where the team can reach them: templates in one person's drafts folder are not templates, they are that person's habits.
Templates are a starting point, not the message. It is worth keeping a small set of email examples that were actually sent and worked, alongside the templates, because a real message that got a reply teaches more than a placeholder with the customer name merged into it.
Around six: enquiry reply, quote cover, invoice reminder, meeting follow-up, onboarding welcome, and a polite decline. More than a dozen and people stop looking.
Require one specific detail from the real conversation in every send, keep it under two hundred words, and cut the opening pleasantry.
Plain text for one-to-one business mail — it is more likely to be delivered and read. Save HTML for newsletters and transactional layouts where structure genuinely helps.
A template is a starting point a person edits before sending. A transactional layout is generated and sent by a system — a receipt or confirmation — and should stay plain and predictable.
Short enough to act on from a phone without scrolling. If it needs more, attach a document and keep the email as the summary.
Good email templates hold the structure and leave room for one real sentence. That sentence is why the reply comes back.
DMARC tells receivers what to do when a message fails authentication. Publishing reject before you know who sends as you is how legitimate mail disappears.
A hard bounce is a permanent answer and must be suppressed immediately. Retrying it damages the reputation that gets the rest of your mail delivered.
Segmentation is only worth doing if the segments get treated differently. Most segmentation projects produce a chart, and every customer continues to receive exactly the same email.