The welcome email is the first piece of brand-affirming, instruction-bearing contact your new user gets. A great welcome email reduces support tickets, boosts activation, and tone-sets the relationship.
What to Include
- Personalised greeting with the user's first name.
- A single clear CTA taking them to the most useful next step (verify email, set up profile, take a tour).
- 3–5 quick-start tips showing them the highest-value features.
- Where to get help — link to docs and a way to contact support.
- Reassurance — a line about privacy, security or a refund policy if relevant.
Configuring
- Open Architect Panel → Email Templates and edit welcome_email.
- Customise subject and body.
- Test by triggering a self-registration in dev.
- Enable by toggling Send welcome email on registration in Site Settings → Users → Registration.
Delivery Timing
- Immediate: Most common — sent on successful registration.
- After verification: Only send once they click the verification link, ensuring deliverability checking is real.
- Delayed (24 hour): Some apps stage a sequence — email 1 immediately, email 2 with tips the next day, email 3 with case studies a week later.
Worked Examples
- SaaS trial: Welcome → 2-day tip → 5-day case study → 12-day trial reminder. Each email drives toward a specific feature use.
- Consumer app: Single welcome email with “Download the app” CTA above the fold.
- B2B platform: Welcome includes per-tenant onboarding link the admin set up — “Your team's workspace is ready at tenant.yoursaas.com”.