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.
Fast, Straightforward SuprSend Onboarding with Reliable Slack Support
What do you like best about the product?
I managed the rollout of SuprSend at our company. The onboarding was straightforward. Our backend team handled the API integration using the docs and SDK. The product team started setting up workflows and templates from the dashboard at the same time. Both could work in parallel because the platform is designed for both technical and non-technical users.
When we had questions during the rollout the support team on Slack was available and gave us clear answers. They helped us think through how to structure our notification workflows for our specific use case rather than just pointing us to docs. That kind of guidance during onboarding made a difference.
The whole process from starting the integration to going live with our first notifications took less time than we had planned for. The engineering team did not have to spend extra cycles figuring things out and the product team was productive from the start.
For teams evaluating notification platforms I would say the onboarding experience matters a lot. If the initial setup is painful everything that follows will be harder. SuprSend made the onboarding easy and the ongoing support has been reliable.
When we had questions during the rollout the support team on Slack was available and gave us clear answers. They helped us think through how to structure our notification workflows for our specific use case rather than just pointing us to docs. That kind of guidance during onboarding made a difference.
The whole process from starting the integration to going live with our first notifications took less time than we had planned for. The engineering team did not have to spend extra cycles figuring things out and the product team was productive from the start.
For teams evaluating notification platforms I would say the onboarding experience matters a lot. If the initial setup is painful everything that follows will be harder. SuprSend made the onboarding easy and the ongoing support has been reliable.
What do you dislike about the product?
A structured onboarding checklist inside the dashboard would help teams track their progress during initial setup.
What problems is the product solving and how is that benefiting you?
We needed the rollout to go smoothly without taking up too much of anyone's time. The combination of a usable platform, good documentation, and responsive support meant we went live without delays or complications.
Affordable, Fast Setup—SuprSend Got Us Building Notifications in a Day
What do you like best about the product?
As a founder I care about two things when picking a tool. Is it affordable and can we start using it quickly without a long setup process. SuprSend checks both.
The free tier gave us room to build and test our notification flows before spending anything. When we moved to a paid plan the pricing was clear and we knew what we were getting. No complicated tiers where you have to figure out which features are behind which paywall. All channels are available on every plan which keeps things simple.
Getting started was fast. The API integration took our developer less than a day and I was setting up workflows from the dashboard the same afternoon. We did not need a sales call or an onboarding session to figure out how things work. The docs were enough to get us going.
For a small team that wants to move fast and keep costs manageable this is a good fit. We got a proper notification setup without it becoming a project or a budget concern.
The free tier gave us room to build and test our notification flows before spending anything. When we moved to a paid plan the pricing was clear and we knew what we were getting. No complicated tiers where you have to figure out which features are behind which paywall. All channels are available on every plan which keeps things simple.
Getting started was fast. The API integration took our developer less than a day and I was setting up workflows from the dashboard the same afternoon. We did not need a sales call or an onboarding session to figure out how things work. The docs were enough to get us going.
For a small team that wants to move fast and keep costs manageable this is a good fit. We got a proper notification setup without it becoming a project or a budget concern.
What do you dislike about the product?
A startup program with extended trial benefits would be a nice touch for very early stage companies.
What problems is the product solving and how is that benefiting you?
We needed notifications up and running quickly without spending a lot of money or time. SuprSend fit our budget and our timeline. We launched with multi-channel notifications without it being a distraction from building our core product.
Efficient Notification Management with Minor Improvements Needed
What do you like best about the product?
I had a problem with duplicate notifications, and SuprSend handles this well. Even if we send the same notification twice, it doesn't get sent multiple times to the user, which gets resolved easily with SuprSend.
What do you dislike about the product?
Exposing the idempotency key logic in the logs would help with debugging edge cases around deduplication.
What problems is the product solving and how is that benefiting you?
SuprSend handles duplicate notifications effectively, even resolving cases when the same notification is sent twice, ensuring users don't receive multiple copies.
SuprSend: Easy to Use with Responsive, Hands-On Support
What do you like best about the product?
Two things made this a good experience for us. First the platform itself is not difficult to use. I am not an engineer and I can navigate the dashboard, set up workflows, edit templates and check logs without needing help. Things are laid out in a way that makes sense and I did not need a long training period to get going.
Second the team behind the product is responsive. During our initial setup we had some questions about how to structure our workflows and the support team on Slack walked us through it clearly. They did not just send us links to docs. They actually looked at what we were trying to do and gave us specific guidance. That continued even after the initial setup whenever we had questions.
Having a product that is easy to use combined with a team that is available when you need them is not something you find with every tool. Both things matter and SuprSend delivers on both.
Second the team behind the product is responsive. During our initial setup we had some questions about how to structure our workflows and the support team on Slack walked us through it clearly. They did not just send us links to docs. They actually looked at what we were trying to do and gave us specific guidance. That continued even after the initial setup whenever we had questions.
Having a product that is easy to use combined with a team that is available when you need them is not something you find with every tool. Both things matter and SuprSend delivers on both.
What do you dislike about the product?
A few in-app tips or suggestions when setting up workflows for the first time would make the onboarding even smoother.
What problems is the product solving and how is that benefiting you?
We needed a notification tool that our product team could use independently and that came with support we could rely on. SuprSend covers both and it has made managing notifications a much smoother process for us.
Conditional workflows let us personalize the notification experience
What do you like best about the product?
Not every user should get the same notification flow. A new user needs a different experience than a power user. A free user should get different messages than a paying customer. Before SuprSend we could not do this without asking engineering to add conditions in the code for each case.
The workflow builder has branching built in. I set conditions based on user properties or event data and the flow splits accordingly. For our onboarding sequence new users get a welcome flow with helpful tips while returning users get a shorter reminder. Free users see upgrade nudges at the right moment while paid users get feature updates instead.
Setting up these branches is straightforward. I pick the condition, define the paths and each path can have its own channels, templates and timing. The visual builder makes it easy to see all the branches at a glance and understand what each type of user will experience.
This level of personalization used to require engineering work for every new condition. Now I manage it all from the dashboard and I can add or change conditions whenever I want. It has made our notifications feel more relevant to each user instead of one-size-fits-all.
The workflow builder has branching built in. I set conditions based on user properties or event data and the flow splits accordingly. For our onboarding sequence new users get a welcome flow with helpful tips while returning users get a shorter reminder. Free users see upgrade nudges at the right moment while paid users get feature updates instead.
Setting up these branches is straightforward. I pick the condition, define the paths and each path can have its own channels, templates and timing. The visual builder makes it easy to see all the branches at a glance and understand what each type of user will experience.
This level of personalization used to require engineering work for every new condition. Now I manage it all from the dashboard and I can add or change conditions whenever I want. It has made our notifications feel more relevant to each user instead of one-size-fits-all.
What do you dislike about the product?
Being able to test each branch separately with a preview user would make it easier to verify flows before pushing them live.
What problems is the product solving and how is that benefiting you?
All our users were getting the same notifications regardless of their stage or plan. That made messages feel generic. Conditional workflows let us personalize the experience without engineering effort and users are engaging more because the messages are relevant to them.
Retry logic and reliability have been solid
What do you like best about the product?
Reliability matters a lot in our case because we send business-critical notifications. Missed notifications can mean missed deadlines and unhappy customers. With our old system we had to build our own retry logic and it was never as robust as it needed to be. There were always edge cases we had not accounted for.
SuprSend handles retries automatically. If a provider fails to deliver, it retries based on configurable rules. If the primary provider is down entirely it falls back to the secondary one. We have seen this work in practice a few times and it has been seamless.
The uptime has been consistent and we have not experienced any downtime on the SuprSend side. The notification logs give us proof of delivery which is important for our compliance requirements. When a customer asks whether they were notified we can show the exact delivery trail.
We also use the webhook integration to push all notification events to our monitoring system. If something unusual happens, like a sudden spike in failures, we catch it through our own alerting. The combination of their built-in reliability and our own monitoring gives us good coverage.
SuprSend handles retries automatically. If a provider fails to deliver, it retries based on configurable rules. If the primary provider is down entirely it falls back to the secondary one. We have seen this work in practice a few times and it has been seamless.
The uptime has been consistent and we have not experienced any downtime on the SuprSend side. The notification logs give us proof of delivery which is important for our compliance requirements. When a customer asks whether they were notified we can show the exact delivery trail.
We also use the webhook integration to push all notification events to our monitoring system. If something unusual happens, like a sudden spike in failures, we catch it through our own alerting. The combination of their built-in reliability and our own monitoring gives us good coverage.
What do you dislike about the product?
Custom SLA reporting in the dashboard would be useful for enterprise customers who need to track and report on notification delivery guarantees.
What problems is the product solving and how is that benefiting you?
Our previous notification system had unreliable retry logic and no proper fallback. Critical notifications would sometimes fail without us knowing. SuprSend has been reliable and the automatic retries and fallback give us confidence that notifications are getting through.
The team behind the product is what keeps us here
What do you like best about the product?
The product is good but what really stands out is the team. We have been using SuprSend for a while now and the support has been consistently helpful. Not just during integration but on an ongoing basis. Whenever we have a question or run into something unexpected the response on Slack is quick and thoughtful.
There have been a few times where we suggested features or improvements and the team actually listened. Some of those suggestions ended up in the product. That kind of responsiveness makes you feel like you are working with a partner rather than just using a tool.
They also proactively let us know when new features are available that might be relevant to our use case. It is not a generic update email. It feels like someone actually looked at how we use the platform and pointed out what might help. For a small company that does not have a big engineering team to figure things out on our own having this kind of relationship with a vendor matters a lot.
There have been a few times where we suggested features or improvements and the team actually listened. Some of those suggestions ended up in the product. That kind of responsiveness makes you feel like you are working with a partner rather than just using a tool.
They also proactively let us know when new features are available that might be relevant to our use case. It is not a generic update email. It feels like someone actually looked at how we use the platform and pointed out what might help. For a small company that does not have a big engineering team to figure things out on our own having this kind of relationship with a vendor matters a lot.
What do you dislike about the product?
A product roadmap page where customers can see what is coming next would be a nice addition.
What problems is the product solving and how is that benefiting you?
We needed a vendor that would be there when we need help and not disappear after the initial sale. SuprSend has been reliable on that front and it gives us confidence that we are on the right platform.
Notifications are finally out of our codebase
What do you like best about the product?
We had notification logic scattered across our backend. Different services were sending emails and push notifications with their own templates hardcoded in. Changing anything meant touching multiple repos and coordinating deployments. It was fragile and nobody wanted to deal with it.
After moving to SuprSend all of that lives outside our code. The backend just fires an event and SuprSend handles the rest. Which channels to use, what template to render, whether to batch or delay. All of that is configured in the dashboard. Our product team manages templates and workflows directly and engineering does not need to be involved unless something changes at the API level.
After moving to SuprSend all of that lives outside our code. The backend just fires an event and SuprSend handles the rest. Which channels to use, what template to render, whether to batch or delay. All of that is configured in the dashboard. Our product team manages templates and workflows directly and engineering does not need to be involved unless something changes at the API level.
What do you dislike about the product?
The API rate limit documentation could be a bit more detailed for high volume use cases.
What problems is the product solving and how is that benefiting you?
Notification logic was tangled into our backend code and every change was risky and slow. Decoupling it to SuprSend simplified our architecture and gave the product team control they did not have before.
Event-driven approach keeps our code clean
What do you like best about the product?
The way SuprSend works is that our backend fires an event and SuprSend takes care of everything else. Which channels to send on, what template to use, whether to batch or delay, what the user's preferences are. All of that is configured outside our code.
This event-driven approach keeps our notification logic minimal. We just need to send the right event with the right data and SuprSend does the rest. If product wants to change the email template or add a push notification to an existing flow they do it in the dashboard. Our code does not change at all.
We started with a few event types and have been adding more as we build new features. Each time it takes a few minutes to set up a new workflow for the event in the dashboard. The API accepts the event and the workflow handles the logic. It is clean and predictable.
For developers who want to keep their backend simple and not clutter it with notification logic this approach works well. Our notification code is basically a few API calls that fire events. Everything else is managed outside the codebase.
This event-driven approach keeps our notification logic minimal. We just need to send the right event with the right data and SuprSend does the rest. If product wants to change the email template or add a push notification to an existing flow they do it in the dashboard. Our code does not change at all.
We started with a few event types and have been adding more as we build new features. Each time it takes a few minutes to set up a new workflow for the event in the dashboard. The API accepts the event and the workflow handles the logic. It is clean and predictable.
For developers who want to keep their backend simple and not clutter it with notification logic this approach works well. Our notification code is basically a few API calls that fire events. Everything else is managed outside the codebase.
What do you dislike about the product?
A way to validate event payloads against expected schemas before they trigger workflows would be a nice safety feature.
What problems is the product solving and how is that benefiting you?
Our notification logic was mixed into our backend code and it made things messy. The event-driven approach lets us keep our code clean while the notification complexity is handled in SuprSend.
Immediate Engagement with Slack and Teams Notifications
What do you like best about the product?
A lot of our users live in Slack or Microsoft Teams during their workday. Sending notifications to email or push was not getting the engagement we wanted because people would see them hours later. When we added Slack and Teams as channels in SuprSend the response was immediate. Users started acting on notifications much faster because the messages appeared right where they were already working.
What do you dislike about the product?
More rich formatting options for Slack and Teams message templates would be a nice improvement.
What problems is the product solving and how is that benefiting you?
Our B2B users were not engaging with email notifications because they do not check email frequently during work. Sending alerts directly to Slack and Teams got their attention faster and engagement went up without us having to change the content.
showing 11 - 20