wiki/knowledge/email-marketing/finwellu-confirmation-email-strategy.md · 662 words · 2026-04-05
FinWellU Confirmation Email Strategy
Overview
During the FWDR/FinWellU website launch planning session, NLP Wealth Management identified clear requirements for overhauling the default WordPress confirmation emails. The existing generic emails were flagged as inadequate for both branding and user experience. Two distinct email types require attention: the site registration confirmation (sent when a user creates an account) and the event registration confirmation (sent when a user signs up for a specific workshop).
See also: [1] | [2]
Email Type 1: Site Registration Confirmation
Sent automatically when a new user registers on finwellu.com.
Requirements
- Remove all "Next Level" branding. Any reference to the internal project name must be replaced with "Financial Wellness Done Right" or "FinWellU."
- Include the approved logo (Logo D) prominently at the top of the email.
- Add motivational/hype copy — a brief statement reinforcing the value of the Financial Wellness Done Right program. Peter Tourville described this as a short, energetic line that resonates with the financial wellness mission.
- Clarify what the user has done and what comes next. The current "success" message is ambiguous. The email should make clear:
- The user has created their profile (step one of two)
- The next step is to log in and register for a workshop
- Include a clear call-to-action (CTA) linking directly to the user's company page or the workshop listing.
- Encourage saving the email as a reference for future logins.
- Send from the finwellu.com domain, not the legacy Next Level domain.
Suggested Messaging Pattern
"You're halfway there! Your Financial Wellness Done Right profile is active. Log in now to browse upcoming workshops and get registered."
Email Type 2: Event Registration Confirmation
Sent when a registered user signs up for a specific workshop event.
Requirements
- Dynamic content based on event type — the email body must adapt depending on whether the event is virtual or in-person:
| Event Type |
Required Content |
| Virtual |
Workshop join link / URL |
| In-Person |
Physical location details (e.g., "Conference Room C, 3rd Floor" or full street address) |
- Consistent branding — same logo and FWDR identity as the site registration email.
- Event-specific details — date, time, and format should be clearly stated.
- Reply-to address — Peter Tourville noted that replies from attendees should likely route to the presenting rep or a rep-specific address rather than a generic FinWellU inbox, to avoid muddying the relationship. John Jonas was tasked with coordinating this decision with Paul before the email template is finalized.
Implementation Notes
WordPress / SMTP Configuration
- Emails are sent through WordPress and are currently tied to the site's domain.
- Once the domain switches to
finwellu.com, outgoing email should reflect that domain.
- SMTP configuration must be hardened before launch to reduce the likelihood of emails being caught by corporate firewalls or spam filters. LPL Financial's email environment (used by Peter Tourville) was identified as a known challenge — emails may be quarantined, delivered to junk, or batched once daily.
- Proper SMTP setup (SPF, DKIM, etc.) should be treated as a launch prerequisite, not a post-launch fix.
Sender Identity
- All automated emails should identify as coming from Financial Wellness Done Right / FinWellU, not "Next Level."
- The reply-to strategy for event confirmation emails is pending a decision by Peter Tourville and Paul (see Action Items).
Action Items
- [ ] Overhaul site registration confirmation email with FWDR branding, Logo D, hype copy, and CTA to register for a workshop (@Karly Oykhman)
- [ ] Build event confirmation email template with dynamic virtual/in-person content fields (@Karly Oykhman)
- [ ] Confirm reply-to address strategy with Paul; report back before finalizing event email (@Peter Tourville)
- [ ] Ensure SMTP is properly configured on finwellu.com domain before launch (@Karly Oykhman / dev)