Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Newsletter Subscription confirmation email #3563

Open
2 tasks done
r3yc0n1c opened this issue Jan 10, 2025 · 6 comments
Open
2 tasks done

[FEATURE] Newsletter Subscription confirmation email #3563

r3yc0n1c opened this issue Jan 10, 2025 · 6 comments

Comments

@r3yc0n1c
Copy link

Why do we need this improvement?

Currently, users who subscribe to the newsletter do not receive any confirmation or feedback acknowledging their subscription, which can cause confusion. A confirmation email enhances the UX, builds trust, and ensures proper communication.

How will this change help?

  • Improves UX: Users will receive instant feedback that their subscription was successful.
  • Builds trust: A confirmation email reassures subscribers and establishes credibility.
  • Reduces errors: If users accidentally subscribe with a wrong email address, they can recognize the mistake and take corrective action.
  • Increases engagement: The confirmation email can include a brief introduction to the newsletter, setting expectations for future content.

Screenshots

newsletter-email-conf.mp4

How could it be implemented/designed?

  1. Trigger on successful subscription:
    • When a user subscribes to the newsletter, trigger an event to send a confirmation email.
  2. Design of the email:
    • Subject
    • Body
    • A personalized greeting (e.g., "Hello [User], thank you for subscribing!")
    • Brief description of the newsletter content and frequency (e.g., "You’ll receive updates every [X] weeks.")
    • An option to unsubscribe or manage preferences.
  3. Create a new Netlify Cloud function for the confirmation email, following the same approach as the newsletter updates.

🚧 Breaking changes

Yes

👀 Have you checked for similar open issues?

  • I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue?

Yes I am willing to submit a PR!

@r3yc0n1c
Copy link
Author

Waiting for triage. I'm willing to work on it once it passes triage.

@Aditya-Prakash14
Copy link

/assign

@r3yc0n1c
Copy link
Author

/assign

please read CONTRIBUTING... the issue is awaiting triage and is already being worked on

@neerja-1984
Copy link

is the issue solved / being solved .. as of now its not assigned to anyone and i wish to contribute

@priyanshuxkumar
Copy link

is anyone working on this issue ??

@r3yc0n1c
Copy link
Author

I'll, once they approve it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants