How Should Infrastructure Teams Design Reliable Email and SMS Communication?
Short answer: for a small SaaS, use an email API for a transactional password reset only when the message contract, retry state, and delivery reporting are explicit. Treat email and SMS as two delivery channels with different failure modes, not as interchangeable notification switches. Define the reset event once, make delivery state observable, keep retries bounded, and give recipients a clear next action even when a network or downstream mailbox is unavailable.
This is a communication system, not just an API call. A useful design has four explicit boundaries: event creation, policy selection, channel delivery, and delivery reporting.…