Suprsend
SuprSendReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
112 reviews
from
External reviews are not included in the AWS star rating for the product.
Our marketing team can manage notifications without dev help
What do you like best about the product?
I run marketing at a small company and we do not have a dedicated product team. Before SuprSend I had to ask our one developer every time I wanted to change an email notification or set up a new message flow. It slowed things down and I felt bad constantly asking for help on something that should be simple.
Now I do it myself. I log into the dashboard, open the template editor, make my changes and push them live. For new notification flows I use the workflow builder. It is visual and I can see the steps in order. I do not need to understand code to use it. When we launched a new feature last month I had the announcement notification set up and sent within an hour.
The learning curve was not steep. I figured out the basics in a day and have been comfortable using it since. For a marketing person who wants to move fast without creating work for others this has been a good experience.
Now I do it myself. I log into the dashboard, open the template editor, make my changes and push them live. For new notification flows I use the workflow builder. It is visual and I can see the steps in order. I do not need to understand code to use it. When we launched a new feature last month I had the announcement notification set up and sent within an hour.
The learning curve was not steep. I figured out the basics in a day and have been comfortable using it since. For a marketing person who wants to move fast without creating work for others this has been a good experience.
What do you dislike about the product?
A few ready-made email layout templates in the editor would save time when starting from scratch.
What problems is the product solving and how is that benefiting you?
I was always waiting on engineering for notification changes and it created delays. Now I manage everything myself and our developer can focus on building the product instead of updating email templates for me.
All our notification channels managed from one place
What do you like best about the product?
We send notifications through email, push and in-app. Before SuprSend each channel was a separate integration. Email went through SendGrid, push through Firebase, and in-app was a custom build. Managing templates, delivery logic and logs across three different systems was messy.
Now everything goes through SuprSend. One API call triggers the notification and it gets delivered on whichever channels the workflow specifies. Templates for all channels are managed from the same editor. Logs for all channels show up in the same dashboard. If I need to add SMS or WhatsApp later I just add the channel to the workflow and configure the provider. No new integration needed.
The consistency is what I like most. Before this each channel had its own way of doing things. Different template formats, different log structures, different error handling. Now it is all standardized. When something goes wrong I look in one place. When I need to update a template I go to one editor. It simplified things a lot for our team.
Now everything goes through SuprSend. One API call triggers the notification and it gets delivered on whichever channels the workflow specifies. Templates for all channels are managed from the same editor. Logs for all channels show up in the same dashboard. If I need to add SMS or WhatsApp later I just add the channel to the workflow and configure the provider. No new integration needed.
The consistency is what I like most. Before this each channel had its own way of doing things. Different template formats, different log structures, different error handling. Now it is all standardized. When something goes wrong I look in one place. When I need to update a template I go to one editor. It simplified things a lot for our team.
What do you dislike about the product?
The email template editor could support a few more layout blocks for complex email designs. It covers the common ones well though.
What problems is the product solving and how is that benefiting you?
Managing separate integrations for each notification channel was taking up too much time and making things inconsistent. Having everything in one platform simplified our stack and made it easier to manage notifications as a whole.
Support feels like working with another engineering team
What do you like best about the product?
The support experience has been consistently good. We communicate through Slack and whenever we have a question someone gets back to us fairly quickly. What sets it apart from other tools is that the people responding actually understand the technical context. We do not have to explain our architecture or repeat ourselves. They get it and give us specific answers.
During our initial integration they helped us plan how to structure our workflows and templates for our use case. It was not just answering questions but actually thinking through the best approach with us. That kind of support is rare. Even after the initial setup we have continued to get good responses whenever something comes up. There was one time we had a question about an edge case in our workflow logic and the team looked into it, confirmed the behavior, and suggested how to handle it. All within the same day.
For a small team that does not have a large engineering department to fall back on having reliable support makes a big difference. It gives us confidence that we are not going to get stuck with no help.
During our initial integration they helped us plan how to structure our workflows and templates for our use case. It was not just answering questions but actually thinking through the best approach with us. That kind of support is rare. Even after the initial setup we have continued to get good responses whenever something comes up. There was one time we had a question about an edge case in our workflow logic and the team looked into it, confirmed the behavior, and suggested how to handle it. All within the same day.
For a small team that does not have a large engineering department to fall back on having reliable support makes a big difference. It gives us confidence that we are not going to get stuck with no help.
What do you dislike about the product?
A community forum or shared space where teams can share tips and learn from each other would be a good addition.
What problems is the product solving and how is that benefiting you?
As a small team we needed a vendor we could rely on for quick and knowledgeable support. SuprSend has delivered on that consistently and it has made our integration and ongoing use smooth.
Preference center gave our users the control they needed
What do you like best about the product?
We had been getting feedback from users for a while that they wanted more control over their notifications. Some wanted fewer emails. Some wanted to get alerts only on specific channels. Others wanted to turn off certain types entirely. Our old system did not support any of that.
The preference center in SuprSend lets users pick which notification categories they want to receive and on which channels. They can set frequency preferences too. Some users want real-time alerts for high priority things but a weekly summary for everything else. That is all configurable from the user side.
From a design perspective the hosted preference page and the embeddable component gave us options. We used the embeddable one inside our app and customized it to match our design system. It did not take long and the result looks like a native part of our product. The product team manages the categories and channel options from the SuprSend dashboard so when we add a new notification type we can add a preference for it without engineering work. It has made our notification experience feel much more thoughtful and user-friendly.
The preference center in SuprSend lets users pick which notification categories they want to receive and on which channels. They can set frequency preferences too. Some users want real-time alerts for high priority things but a weekly summary for everything else. That is all configurable from the user side.
From a design perspective the hosted preference page and the embeddable component gave us options. We used the embeddable one inside our app and customized it to match our design system. It did not take long and the result looks like a native part of our product. The product team manages the categories and channel options from the SuprSend dashboard so when we add a new notification type we can add a preference for it without engineering work. It has made our notification experience feel much more thoughtful and user-friendly.
What do you dislike about the product?
A few more default layout options for the embeddable preference component would help teams that want to get it looking good quickly without custom styling.
What problems is the product solving and how is that benefiting you?
Users wanted control over their notifications and we had no way to give it to them. The preference center solved that and the feedback from users has been positive since we launched it.
Good value for what you get
What do you like best about the product?
We were getting multi-channel notifications, workflow builder, in-app inbox, template editors and logs all in one platform. Compared to stitching together separate tools for each channel this works out much better than building in-house. The pricing is fair for what we get. We started on the free plan which gave us enough to test everything during our early days. As we grew the pricing scaled in a way that made sense and did not catch us off guard. For an early stage company that matters.
What do you dislike about the product?
Having some pre-built workflow templates for common use cases would help new users get started a bit faster.
What problems is the product solving and how is that benefiting you?
We could not afford to spend weeks building notification infrastructure or pay for multiple tools. SuprSend gave us everything in one place at a price point that made sense for our stage. We launched with proper notifications from day one.
Straightforward, Uncluttered UI That Makes Email Templates Easy
What do you like best about the product?
It is pretty straightforward to use. I can edit email templates and set up basic notification flows without asking anyone for help. The interface is not cluttered and things just make sense. For someone who is not an engineer this matters a lot.
What do you dislike about the product?
Would be nice to have a few more template design options built in.
What problems is the product solving and how is that benefiting you?
I needed to make quick changes to our notification emails without going through engineering every time. SuprSend lets me do that and it has made our communication with users a lot more consistent.
Easy to integrate even for someone with less experience
What do you like best about the product?
I was assigned to integrate SuprSend and I was a bit nervous since I have not worked with notification platforms before. But the documentation walked me through everything step by step. The quick start guide was clear and the code examples in the SDK docs were easy to follow. I had the basic integration done within a day. For someone who is not super experienced with this kind of tool it was not as hard as I expected.
What do you dislike about the product?
A few video tutorials alongside the written docs would be a nice addition for visual learners.
What problems is the product solving and how is that benefiting you?
Our team needed to add notifications to the product and I was the one available to do it. The clear documentation and simple API meant I could handle it without needing a lot of hand-holding from senior engineers.
SuprSend Simplifies Multi-Channel Notifications with Predictable Pricing
What do you like best about the product?
We spent a fair amount of time deciding whether to build our notification system in-house or use a platform. Once we mapped out what it would take to support multi-channel delivery, template management, user preferences, retry logic, logging, and all the other pieces you need for a solid notification setup, it became obvious that building it ourselves would take months—and we’d still be on the hook for ongoing maintenance. SuprSend gives us all of that out of the box.
Pricing has also been straightforward and predictable. We started on the free tier to test things, and when we upgraded it was easy to understand exactly what we were paying for. There haven’t been any hidden limits or surprise charges, which matters a lot when you’re a small team watching the budget closely. Overall, the cost is a fraction of what we’d spend in engineering time to build and maintain the same system, so for us the build-versus-buy decision was simple once we did the math.
Pricing has also been straightforward and predictable. We started on the free tier to test things, and when we upgraded it was easy to understand exactly what we were paying for. There haven’t been any hidden limits or surprise charges, which matters a lot when you’re a small team watching the budget closely. Overall, the cost is a fraction of what we’d spend in engineering time to build and maintain the same system, so for us the build-versus-buy decision was simple once we did the math.
What do you dislike about the product?
A cost calculator on the website that estimates monthly spend based on notification volume would be very helpful during the evaluation process.
What problems is the product solving and how is that benefiting you?
We couldn’t justify pulling engineers away from core product work just to build notification infrastructure. SuprSend gave us a ready-to-use platform at a cost that made sense for us. We were able to get up and running quickly, and our engineering team stayed focused on what matters most.
Support team is quick and actually helpful
What do you like best about the product?
The support has been really good. They have a Slack channel where you can ask questions and someone usually gets back to you pretty fast. What I like is that the people replying actually understand the technical side of things. When we were integrating the API we had a few edge cases and the support team helped us work through them without much back and forth. That made the whole setup process a lot smoother than I expected.
What do you dislike about the product?
Nothing major. Sometimes responses take a bit longer on weekends but that is understandable.
What problems is the product solving and how is that benefiting you?
We were setting up notifications for the first time and had a lot of questions about how to structure things. Having responsive support meant we did not get stuck at any point during integration. It saved us time and we got everything running without delays.
Multi-tenancy handles our B2B customer needs well
What do you like best about the product?
We build a platform that other businesses use to serve their own customers. That means every tenant on our platform needs notifications that look like they come from them, not from us. Templates, branding, sender details, even the in-app notification feed needs to match each tenant.
SuprSend handles all of this with the tenant ID approach. We pass the tenant ID in our API call and the right branding, templates and provider settings are applied automatically. Some of our larger tenants use their own email provider and we can configure that per tenant without any custom code on our side. Smaller tenants use our shared setup and everything just works.
The per-tenant preference management is also useful. Different tenants have different rules about what their users can and cannot opt out of. Some want full user control, others want certain notifications to always go through. We configure that per tenant from the dashboard and it is applied without us touching any code. Adding a new tenant to the notification system is quick now. It used to be a manual process every time and it would take days. Now it takes very little time.
SuprSend handles all of this with the tenant ID approach. We pass the tenant ID in our API call and the right branding, templates and provider settings are applied automatically. Some of our larger tenants use their own email provider and we can configure that per tenant without any custom code on our side. Smaller tenants use our shared setup and everything just works.
The per-tenant preference management is also useful. Different tenants have different rules about what their users can and cannot opt out of. Some want full user control, others want certain notifications to always go through. We configure that per tenant from the dashboard and it is applied without us touching any code. Adding a new tenant to the notification system is quick now. It used to be a manual process every time and it would take days. Now it takes very little time.
What do you dislike about the product?
A tenant dashboard that each tenant admin can access directly for basic reporting would be a useful addition down the line.
What problems is the product solving and how is that benefiting you?
Managing white-labeled notifications for each tenant was a growing pain for us. Custom code for each one was not scalable. SuprSend gave us a native way to handle it and adding new tenants is no longer a project.
showing 21 - 30