
Tone control for AI drafts: formal, friendly and firm
The same customer reply written formal, friendly and firm, with notes on what changed, prompts that steer AI tone, and how to strip over-apology and filler.
4 min read

The same customer reply written formal, friendly and firm, with notes on what changed, prompts that steer AI tone, and how to strip over-apology and filler.
4 min read

Lower TTLs before you change SPF, DKIM or MX, and know which caches ignore you. A practical timeline for authentication changes without surprises.
5 min read

When a live onboarding call earns its cost, when self-serve email onboarding is enough, and how to write the emails that book, recap and rescue those calls.
5 min read

A staged playbook for founders handing customer email to their first hire: shadowing, reviewed replies, owning a category, then owning the whole inbox.
5 min read

A client retry after a timeout should never email a customer twice. How idempotency keys work, the race people miss and how to pick key values.
4 min read

A changelog is written for the team that shipped. A product update email is written for the customer. How to pick what goes out, group it, and keep it short.
4 min read

A runbook for telling customers their bug is fixed: track who reported it, write the follow-up, confirm it works, and handle the cases where it does not.
5 min read

Which headers to sign, why signing From twice blocks header injection, and how the l= body length tag lets attackers append content to signed mail.
5 min read

Front, Help Scout and a plain shared mailbox solve overlapping problems for different teams. A fair look at who each one suits, at the time of writing.
5 min read

AI drafts can invent features, dates, policies, links and names. Five worked examples of each kind of error, plus a habit that catches them before sending.
5 min read

Receivers expect a sending IP to have a PTR record that resolves back to the same IP and a sane HELO name. Configure all three and verify them.
4 min read

A shared inbox is enough for longer than most teams think, and a help desk is right sooner than some admit. How to decide at each stage of a company.
5 min read