The document is very easy to read and tells me all about my requires. The development team is very nice to respond to my bug report. I found a bug with error message "webhook body render timeout" and they had a fix created within 24h, even though it didn't work properly but another fix applied later. Finally I got my result. It's very nice for me to using their product.

I worked in E-commerse and SuprSend built the platform that I would've otherwise had to build myself. Why is sending emails a hard problem? Because engineers should not manage content templates. We shouldn't have to store content as code and have to deploy all the time whenever a paragraph or image needs to be updated. This gives marketing and product teams the agility to adapt to trends quickly without waiting for slow cumbersome code reviews or integration tests. Finally, engineering only needs to properly populate the application with appropriate API calls with the right template variables, rather than worry about contente rendering, fallback variables, and misaligned layouts for emails. On top of the basics, SuprSend provides user-initiated opt-out and communications preferences, event-driven email triggers, email digests and periodic roundups, and even a full-blown notification platform complete with pre-built React components. This saves much coding work needed to introduce a rich notification ecosystem to keep users engaged and coming back to our app.

Easy setup of templates, workflows, integration, and vendors! The documentation really helped a lot and even if we need some help Suprsend team are keen on supporting us on our challenges.