Esia NathanielSvenska

Stage 6 of 6: Build. Courses, tools and automations that are yours.

Email automations with Resend: the right email at the right moment

Decide which moments should trigger an email: a booking, a payment, the day before a session, a week after. Verify a domain you own in Resend, keep the API key in an environment file, write each email in your voice and test every one on your own address before anything reaches a real person.

By Nathaniel · 3 min read · Facts checked: 26 October 2026

BookedConfirmRemindDay 7 follow-up

Which emails should send themselves?

Picture this

A client books at eleven at night. By morning they have heard nothing, and wonder whether it worked. A confirmation that arrived within a minute, in your voice, with the time and what to bring, would have settled it. You were asleep, and the email was not.

An automation is an email sent because something happened, not because you remembered. Start with the moments where silence costs you: after a booking, after a payment, before a session, after a week, and when someone writes to you. I use Resend for exactly these on my own sites: confirmations, notes of interest and alerts to me.

Pick your moments

Which emails should go out by themselves? Choose, and get the instruction.

Booking confirmationAt once
Reminder before the session24 h before
Receipt and thank-youAt once
Alert to me about a new enquiryAt once
Set up these email automations with Resend:
1. Booking confirmation: sent when a booking is made (At once)
2. Reminder before the session: sent when 24 hours before the session (24 h before)
3. Receipt and thank-you: sent when a payment succeeds (At once)
4. Alert to me about a new enquiry: sent when a form is submitted (At once)

Rules: send from a verified subdomain I own, never from a public address. Keep the API key in an environment file, never in the code that is published. Write each email in my voice following BRAND.md, short, with one clear next step and a plain unsubscribe or reply line where it fits. Send every email to my own address first as a test and show me the result before anything goes to a real person. Log what was sent and tell me if one bounces.

How do I set up Resend safely?

How do I write emails people read?

  • One job per email and one clear next step.
  • Write them in your voice, short, from you, not from “the team”.
  • A confirmation says what, when, where and what to bring. Nothing else.
  • A plain way to reply or unsubscribe where it fits. Marketing emails to people who have not asked for them are a separate matter, so ask a professional if unsure.
Set it up

Set up these email automations with Resend: [list]. Send from a verified subdomain I own. Keep the API key in an environment file. Write each email in my voice following BRAND.md, short, with one clear next step. Send each one to my own address first as a test and show me the result before anything goes to a real person. Log what was sent and tell me if one bounces.

How do I time them?

  • At once: confirmations, receipts and alerts to you.
  • Before: a reminder the day before a session. Resend can schedule an email for a later time.
  • After: a check-in a week later, when the person has had time to use what you gave them.
  • When quiet: one genuine check-in after a long silence, then let it go.

Send at a time that suits the reader, in their time zone, and not at night.

How do I know it works?

  • Check the logs in Resend: what was sent, delivered and bounced.
  • Use a webhook if you want your site to react when an email bounces or is clicked.
  • Read your own emails as a stranger, once a month.
  • When a person replies, a person answers. Automation is for the routine, not for relationships.

What becomes possible?

Email is where all the pieces meet: bookings, payments, courses and the people you serve.

  • A seven-day program delivered by one email a day.
  • A welcome pack that arrives after a purchase and changes with what they bought.
  • A weekly summary to yourself of everything that happened.
  • A small community letter that goes out to people who have said yes to it.
Stretch

Look at everything that happens in my business: bookings, payments, enquiries, sessions. Where would the right email at the right moment help a person most, or save me the most time? Suggest five automations, each with the trigger, the timing, a draft of the email in my voice, and what it should never say.

Questions people ask

Do I need a domain of my own?

Yes. Resend sends from a domain you own and have verified, not from a shared or public one.

Can I send a newsletter with it too?

Resend has tools for contacts and broadcasts as well. Only email people who have said yes, and make unsubscribing easy.

Sources

  1. Resend: introduction
  2. Resend: verified domains
  3. Resend: schedule an email
  4. Resend: webhooks

Who is writing this

I am Nathaniel, a commercial operator. For twenty years, across four continents and more than fifteen ventures, I have taken research and young companies from idea to customer. Two KTH spin-offs reached joint development agreements with Fortune 500 partners. An indoor farm sold its full production within about ninety days and ended in a joint venture exit. This year I am a commercial expert for the European Innovation Council's Tech to Market programme. Now I build agents, because the hard part of new technology is rarely the technology. It is getting people to want it and use it.

Want to do this together?

In two hours I can build this with you: Email automations with Resend.

Next on the pathA newsletter and a communityTurn the list you already have into people who look forward to hearing from you