A practical evaluation framework for choosing a transactional email provider — the criteria that matter in production, how to test them before committing, and the costs that only appear later.
The three ways to send transactional email, how to choose between them, and the architecture decisions — queueing, retries, template storage — that decide whether it holds up in production.
A working Node.js implementation — sending by API, queueing dispatch, handling retries idempotently, and keeping templates out of your repository.
What each record does, how to configure all three correctly, and why alignment — not just passing — is what decides whether your transactional email reaches the inbox.
Timing, subject lines, content structure, authentication and operations — the practices that decide whether your transactional email works or quietly fails.
Why transactional email lands in spam, how mailbox providers actually score you, and the authentication, reputation and hygiene work that keeps critical email in the inbox.
The 15 transactional emails almost every product ends up sending — what each one must contain, what breaks it, and which ones are worth getting right first.
Consent, infrastructure, sender reputation and legal obligations all change depending on which one you are sending — and the line is thinner than most teams think.
What a transactional email is, how it differs from marketing email, the 15 most common types, and how sending actually works — from API call to inbox.