Delivery failure email

Email when result or delivery email was not created correctly: acknowledges the issue and gives recovery path.

After a webhook gap, delivery gap, failed generation, or email bounce when the user has already paid.

Owner note

Do not hide the problem. The user should know the payment is not lost.

{{order_id}}{{status_url}}{{support_email}}

Fallback

If the delivery failure is widespread, move to incident log and status page update.

Do this

Acknowledge that delivery is delayed or needs manual review.
Say that a second payment is not needed.
Provide status/support path.

Avoid this

Do not use technical jargon instead of clarity.
Do not blame Stripe, Resend, or the user.
Do not send if the issue is already fixed and the normal reading-ready email went out.

Default

Subject

We are checking your scroll delivery

Preview

Your payment is not lost. Delivery needs review.

Body

We see that scroll delivery for order {{order_id}} needs review. A second payment is not needed. We are checking the status and will restore access if the result did not appear automatically. Status: {{status_url}}. If you want to add details, contact: {{support_email}}.

Before sending

Checks before wiring the template into Resend or the API.

Subject does not reveal the private question or sensitive situation.
Preview text explains the email action without pressure.
CTA points to the correct route and avoids stale links.

After sending

Checks after a test send.

Email reads on mobile without horizontal scrolling.
Plain text version works without images.
Support email is visible but not the only path.