Welcome Email Sequences via API: What to Send on Day 0
Onboarding mail from your domain — authentication, content, and reply handling.
Day-zero email sets product expectations. Send from the same domain users signed up on, with DKIM aligned and a reply path to support@.
What to send on day zero
- Confirmation that sign-up worked, plus email verification if you need it
- The single next step that gets value from your product — one link, not a menu
- Where to get help: a support address that a person reads, and your help centre
- What further mail to expect, and how to change it
Send it from the domain users signed up on
If someone signed up on yourproduct.com, the welcome mail should come from that domain, signed with its DKIM key. Mail from an unrelated sending domain looks like phishing and is more likely to be filtered. With OquMail your app sends through an API key tied to a mailbox on your domain, so it shares the same authentication as your team’s mail.
Let people reply
A welcome email is the most likely one to get a reply — a question, a bug, a thank-you. Send from an address that reaches a person, or set Reply-To to support@. Replies from new users also tell mailbox providers your mail is wanted.
After day zero
Keep follow-up onboarding mail tied to what the user has or has not done — not a fixed drip that ignores their progress — and give them a way to stop it. Anything promotional belongs in a separate stream they opted into.