You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Trigger on successful subscription:
When a user subscribes to the newsletter, trigger an event to send a confirmation email.
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.
Create a new Netlify Cloud function for the confirmation email, following the same approach as the newsletter updates.
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?
Screenshots
newsletter-email-conf.mp4
How could it be implemented/designed?
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: