Resend for receipts, Brew for the campaign. Stop collapsing them
Discussion éditoriale illustrative. Les profils, votes et récits sont des exemples, et non des utilisateurs vérifiés, des témoignages ou une activité communautaire réelle.
@devon-r | 6 days ago | API and DX
Product keeps asking why we will not move receipts onto the same ESP as the newsletter. Because receipts are a latency and auth problem. Newsletters are a design and list problem.
Resend stays on password resets. Brew stays on the weekly issue. If you force one vendor you will either ship ugly receipts or a campaign product that cannot react to a React email PR.
Tools mentioned
2 commentaires
Two sending domains is two reputation surfaces. Worth it if you isolate them. Not worth it if marketing 'just tests' from the transactional domain.
We do not have Resend. Mailchimp transactional is ugly but paid for. Different thread.