Giving a copy editor control over a welcome template also requires defining the point where that control ends. Short answer: compare transactional email APIs by template ownership, then require recipient suppression to veto every template revision. In a healthtech welcome flow, an approved wording change must never make an invalid destination eligible again. Select the transport after you can explain that rule. Submission isn't delivery.
For a bounded postmortem exercise, imagine two welcome jobs for the synthetic account clinic-demo-42, one using template revision 7 and the other revision 8, with a permanent bounce recorded between them. These are example inputs, not a reported production incident. I'd begin the review with a narrower question than whether the provider dashboard was green: what page fired, and could its responder establish why the second job remained eligible?
The lesson is a separation of authority.…