SuprSend Reviews & Product Details

What I like best is that push credentials are stored on the server, not in the app. When an app's Firebase or APNs credential is wrong, we replace it on the SuprSend side and notifications start arriving within minutes. There's no new build and no new App Store or Play review, which saves days on mobile. I can also see which Firebase project a stored credential belongs to, so I can find mismatches fast. And when a notification is shown wrong, one template fix on the SuprSend side reaches every app at once. Review collected by and hosted on G2.com.

Most of what I'd change is about failures that don't announce themselves. The notification template HTML-escaped push text, so "&" showed up as "&" on the device. Push titles and bodies are plain text, so escaping should be off by default for APNs and FCM. A Firebase credential that points at a project that has been shut down also fails quietly, so it looks like a bug in the app. A health check that flags it would save hours. And when two backends send to the same users from different workspaces, tokens registered in one can't be seen from the other. A hint like "this user exists in another workspace" would make that obvious right away. Review collected by and hosted on G2.com.

I like how easy it is to create workflows, build segment lists based on SQL queries, and send broadcast messages when needed. The newly launched MCP has been a great help and saved me a tonne of time by letting me use my AI agent instead of doing things manually. I also like the quick support from the team over Slack. Review collected by and hosted on G2.com.

I had a bit of a learning curve creating and testing complex workflows, and it took about 2–3 weeks to get everything set up smoothly. The analytics and logs don’t always reflect the exact current status of sent messages, especially on WhatsApp. The SMS vendor options are limited, and my current vendor, CBIS, isn’t listed. RCS messaging is also missing. I can’t add multiple WhatsApp numbers or vendors, so I’m limited to one number across different communications. I’d like to use separate numbers for different templates and workflows, since marketing messages can get flagged as spam and affect transactional messages if Meta flags the account. I’d also like an option to retry failed WhatsApp deliveries. Review collected by and hosted on G2.com.

Honestly, what stood out most to me was how fast I could get everything up and running. Adding the .p8 file for iOS and the FCM config for Android was painless, and I didn’t have to wade through a mountain of documentation just to get it working. And when something does go wrong, it’s usually pretty easy to pinpoint the cause and fix it.

Most of my time in SuprSend is spent in the logs. I can quickly pull up a user, review their devices, see what was sent, and the status gives me an immediate signal about what’s happening. No token usually means the app never registered the device. A token with a failure is almost always a setup problem. If it shows as delivered, then the issue is on the phone side. Before using this, I’d end up going back and forth with customers forever just to narrow it down to that, so it genuinely saves me a lot of time. The dashboard is straightforward too, which means I’m not wasting time clicking around trying to find what I need.

I also appreciate that a single API covers both iOS and Android, and that it works with APNs, FCM, and our Expo and React Native apps. That keeps the notification code our AI agent writes clean, and it stays consistent across all our apps. The error messages are generally clear, and I can usually see a push appear in the logs shortly after it’s sent. I’m not involved in pricing, but considering the debugging time it saves me, I’d say it more than earns its place. Review collected by and hosted on G2.com.

The biggest issue for me is silent failures. A push can show as “sent” and still never reach the phone—for example, if a key is missing or the package name is empty. Seeing “sent” doesn’t tell me whether it actually arrived, so I end up digging through the logs just to confirm delivery. I’d really like a health check per channel and a warning for stale tokens, because that’s where things feel weakest from a reliability/performance standpoint.

I’d also appreciate some AI assistance with the logs, such as a short note that says, “this failed because the APNs key is missing.” Right now I have to infer that myself from the status details. Search feels limited as well: I’d like to be able to filter by device token, error code, and date range without needing the exact user ID. Review collected by and hosted on G2.com.

I appreciate that SuprSend’s integrations are reliable and have very little downtime. I can track delivery and find all the logs in one place. I can quickly open a workspace and use the logs to find the cause of a problem, even at a critical time. I also like having support for multiple types of integrations on one platform. Review collected by and hosted on G2.com.

I find it hard to find workspaces in the UI. We have more than 5,000, so I have to scroll; a search bar by workspace name would be best. I’d also like agentic maps with links, a better telemetry API for the monitoring system, and a broadcasting dashboard for Android. Review collected by and hosted on G2.com.

I like how SuprSend seamlessly sends every push notification and email. The UI builder of templates is probably the tool I use the most. The initial setup was pretty straightforward. Review collected by and hosted on G2.com.

There's something that's been bothering me, like I want to use tenant primary, secondary, and tertiary colors in a centralized way without writing the code in HTML. I wish there was a feature in the UI editor for this. I've already shared this with the team. Review collected by and hosted on G2.com.

I like SuprSend's unified multi-channel notification orchestration, which fits our lean Los Angeles apparel e-commerce team perfectly. Before we adopted this platform, we managed email, SMS and web push notifications using separate services, and it created constant chaos. Last summer during our linen collection launch, our disjointed messaging stack triggered inconsistent customer alerts. Some shoppers received duplicate shipping updates while others never got abandoned cart reminders, leading to dozens of support tickets. Now we build a single notification template and route it across email, SMS, and browser push, keeping our brand tone consistent without recreating content repeatedly. I value the straightforward routing and frequency control rules, allowing us to segment audiences easily. Loyal repeat buyers get priority restock alerts for our best-selling denim, while first-time shoppers receive lighter promotions to avoid message fatigue. The centralized delivery dashboard is another standout feature. I once spotted a batch of undelivered SMS alerts days before customers started complaining, and we resolved the issue quickly. SuprSend simplifies our notification stack and removes the hassle of switching between dozens of platforms. It standardizes our brand communications and consistently wins back lost revenue through timely abandoned cart reminders for our apparel store. Even with existing integration flaws, this unified notification hub has become essential for our small team during seasonal fashion launches. Review collected by and hosted on G2.com.

There are several frustrating limitations within SuprSend that add extra manual labor for our fashion brand operations. The native integration with our Square Online store lacks stability during high-traffic events. During our fall knitwear launch, slow order data sync caused over 70 customers to wait hours for shipping confirmations, flooding our support inbox with complaints. There is no automatic notification to warn me when syncs fall behind, forcing me to manually check logs every few hours. The audience segmentation functionality remains fairly basic. We want to send targeted restock alerts to shoppers who previously purchased denim, yet the platform cannot pull detailed historical order information automatically. I have to export customer data from Square Online and import CSV files regularly, a tedious process that once led to duplicate contact entries in our system. The template visual editor also lacks flexible styling controls. Notification formatting displays inconsistently across SMS and email, so I need to create multiple modified versions instead of reusing one master template. Embedding product thumbnails inside automated alerts is restricted, which makes it harder to showcase new apparel styles to potential buyers. All these shortcomings pile up during busy sales periods and take valuable time away from product launch planning. Review collected by and hosted on G2.com.

I like the user-level logs. I can search for a user, see their registered iOS or Android devices and the status of every push, and usually figure out the problem in a few minutes. The clear error codes help me point customers to the exact fix, instead of going back and forth, and save our engineers from digging through backend logs. I also like having one API for both platforms: the app sends a push to a user ID, and SuprSend handles the APNs and FCM details. That keeps the generated code simple and consistent across apps, with less that can go wrong and one predictable place to support. It also means we don’t have to build and run our own push system. Being able to connect SuprSend’s devices and logs with our internal ticketing and deployment tools helps us find the root cause quickly. The initial setup was good, too. Review collected by and hosted on G2.com.

The biggest issue for me is silent failures: a push can show as successful even though nothing reaches the phone, and the dashboard doesn’t warn us when an APNs key is missing or revoked or the FCM channel has no app package name. “Sent to APNs/FCM” also doesn’t tell me whether the push arrived on the device. I’d like clearer provider responses and stale-token flags. Search is hard unless I have the exact user ID, and filtering logs by device token, error code, status, app, or date range would make debugging faster. Swapping or rotating keys could also be easier, with a clearer indication of which key is active. Review collected by and hosted on G2.com.

What I like most about SuprSend

is how thoughtfully the platform is designed from both a developer and product perspective. The UI is clean and easy to navigate, so setting up notification workflows doesn’t feel overwhelming even when handling multiple channels like email, push, SMS, Slack, and in-app messaging.

The integrations are another strong point. It connects well with modern product stacks and makes it easier to centralize communication logic instead of managing notifications separately across tools. From a performance standpoint, the platform feels reliable and scalable, especially for teams that send large volumes of notifications and need good observability.

I also like the balance between flexibility and automation. Features like batching, user preferences, workflow rules, and intelligent routing help reduce notification noise and improve the overall user experience. There’s a subtle AI/intelligence layer in how workflows and delivery can be optimized, which makes the system feel smarter than a basic notification service.

In terms of ROI, it saves a significant amount of engineering effort that would otherwise go into building and maintaining an in-house notification infrastructure. That alone can justify the pricing for growing teams. The onboarding experience also feels developer-friendly, with good documentation and a product flow that’s relatively quick to understand. Overall, it feels like a mature platform solving a very real operational problem in a practical way. Review collected by and hosted on G2.com.

One thing I dislike about SuprSend

is that while the platform is powerful, some parts of the setup can feel a bit overwhelming initially — especially when configuring complex multi-channel workflows or advanced notification logic. Review collected by and hosted on G2.com.

What stands out most about SuprSend is how it simplifies and centralizes notification management across multiple channels. The platform makes it easy to design, trigger, and monitor notifications (like email, SMS, push, and in-app) from a single place, which saves a lot of development time and effort. Its clean API, flexibility in handling workflows, and ability to personalize messaging at scale are especially impressive. Overall, it helps teams deliver timely, consistent, and engaging communication without unnecessary complexity. Review collected by and hosted on G2.com.

One area that could be improved in SuprSend is the learning curve when getting started - some of the advanced features and configurations can take a bit of time to fully understand. Additionally, expanding the documentation with more real-world examples and use cases would make onboarding even smoother. That said, once you get familiar with the platform, it becomes very powerful and efficient to use. Review collected by and hosted on G2.com.

I like how smooth it is to create notifications, set up conditional logic, add batching, and configure the entire workflow end to end. It also supports a wide range of channels for sending notifications, which makes our lives easier. Review collected by and hosted on G2.com.

I don’t like the in-app notifications. Sometimes the bell icon appears, and other times it doesn’t. Also, the button in the in-app notification doesn’t render properly. Review collected by and hosted on G2.com.