This would be a really amazing upgrade and honestly something that would help a lot of Memberstack customers building production SaaS products and global web apps.
1. No-reply sender address support
It would be extremely useful to allow the option to use a no-reply sender address (for example no-reply@yourdomain.com) for transactional emails.
Right now, as far as the docs indicate, Memberstack requires a valid reply-capable email address, which makes sense technically. But in practice, many larger SaaS companies and modern web apps intentionally separate transactional messaging from support channels using no-reply addresses.
Having this as an optional configuration would give developers more flexibility in how they structure communication flows, reduce inbox management overhead, and better match real-world production setups.
2. More advanced transactional email customization
It would be amazing to see more control over transactional emails in general, especially:
- Deeper template customization (layout, structure, and styling control)
- More powerful dynamic variables and conditional logic
- Better per-email-type customization options
- Stronger branding control without needing external workarounds
This would make it much easier to match transactional emails with the rest of an app’s UX and brand system.
3. Native localization for transactional emails
Another huge improvement would be built-in support for multilingual transactional emails.
A system like this would be incredibly powerful:
- Ability to define multiple language versions of each transactional email template
- Assign a language to a user via a Memberstack field (or similar property)
- Automatically send the correct localized email based on that value
- Optional support for advanced logic (e.g. Memberscript or rules-based routing)
This would make it much easier to build truly global SaaS products without relying on external email providers just for localization.
Overall, this feels like something that would significantly improve Memberstack’s flexibility for serious production use cases. A lot of builders working with global audiences would definitely benefit from this.
2 comments
Amazing description of the feature request and reason you need it. I'll see what we can do to work this into the roadmap 🙏
That’s amazing to hear Duncan, thank you for the thoughtful response and for considering this.
Being a long-time Memberstack customer and planning to continue using it for years to come, it’s genuinely exciting to see features like this potentially being explored. Changes like these would put Memberstack in an even stronger position and push it further ahead of similar tools in the space.
There’s strong confidence that founders building multi-language and global apps with Memberstack would find these improvements incredibly valuable, especially when it comes to scaling and creating more polished, production-ready experiences.
Thanks again for the consideration and openness to feedback — really appreciate it. Have a great day Duncan!
Please sign in to leave a comment.