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. Review collected by and hosted on G2.com.

Custom SLA reporting in the dashboard would be useful for enterprise customers who need to track and report on notification delivery guarantees. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

A product roadmap page where customers can see what is coming next would be a nice addition. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The API rate limit documentation could be a bit more detailed for high volume use cases. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The email template editor could support a few more layout blocks for complex email designs. It covers the common ones well though. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

A cost calculator on the website that estimates monthly spend based on notification volume would be very helpful during the evaluation process. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

A tenant dashboard that each tenant admin can access directly for basic reporting would be a useful addition down the line. Review collected by and hosted on G2.com.

The ease of use

Strong navigable documentation

Traceable logs

Workflow UI is intuitive

Lots of connectors

Haven't used their new CLI tool but it's good know that they're keeping up with the agentic trends Review collected by and hosted on G2.com.

Environments, versioning, and fields within templates can be a bit complicated.

Testing workflows is complicated, you need to know the recipient id and it's hard to track environment variables Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Having some pre-built workflow templates for common use cases would help new users get started a bit faster. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Would be nice to have a few more template design options built in. Review collected by and hosted on G2.com.