Suprsend

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

We don’t have to build and run our own push system anymore. With this in place, our app builders don’t have to deal with sending notifications to Apple or Google, storing tokens, or retrying failed pushes. On the support side, it turns what used to be a long back-and-forth with customers into something we can resolve in a few minutes by checking the logs, and that’s where the ROI really shows up for us. I’m not involved in pricing, but for the amount of time it saves, I’d say it earns its place.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

SuprSend handles push delivery to iOS and Android, so the people building apps on Emergent never have to write Apple or Firebase sending code or store push credentials in their app. Credentials are kept on the server and each app has its own workspace, so one app's users, tokens and keys never mix with another's. For me in L3 mobile support, the biggest benefit is speed. When push breaks because of a wrong or outdated credential, I fix it on the SuprSend side and delivery comes back within minutes, with no rebuild and no new store review. Because I can see each app's stored credentials and registered devices, I can tell whether the problem is in the app, the credential or delivery itself. That turns a long back-and-forth with the customer into one clear answer.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

I use SuprSend so we don’t have to build our own push system. Apps send one request to a user ID, and SuprSend handles APNs and FCM across iOS and Android. Its logs help me pinpoint failures and give customers a clear answer instead of guessing.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

My team uses SuprSend for tracking and delivery from 0 to 100 steps, with logs in one place. We can quickly open a workspace and find the reason for a problem, even at a crucial time. Its integrations are reliable, with very little downtime.

What do you like best about the product?

The thing I like most about suprsend is how easy it is to navigate. It’s also simple to test notifications and quickly find errors when they aren’t working. On top of that, adding all the files required for Android and iOS configurations is straightforward.

What do you dislike about the product?

I don’t have any dislikes. Maybe they could add a search option for finding projects in the top-right corner.

What problems is the product solving and how is that benefiting you?

Its good

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Before SuprSend, we relied on multiple independent messaging tools to manage customer alerts, and that fragmented workflow created frequent customer-facing errors. I still remember our summer linen launch mishap, where inconsistent abandoned cart reminders cost us multiple potential orders and increased support workload. SuprSend brings all our multi-channel notifications into one centralized platform, eliminating the need to toggle between separate services for email, SMS and web push. It delivers unified brand messaging for order confirmations, shipping updates and restock announcements, so shoppers receive consistent communications from our apparel brand. Reliable abandoned cart outreach helps us recover sales that we would have otherwise lost. The centralized delivery log system allows me to spot failed alerts and delivery issues early. On one occasion, we identified a group of undelivered promotional notifications ahead of our flash sale and fixed the configuration before larger customer complaints emerged. While we still deal with unstable Square Online syncing and limited segmentation capabilities, SuprSend drastically reduces the number of support inquiries caused by disjointed messaging. Our small team spends less time managing scattered notification tools and can focus more on creative work, seasonal collection planning and improving the overall customer shopping experience.

What do you like best about the product?

Extremely customizable — from tenant to template! The ability to run mock notifications is great! Yes!

What do you dislike about the product?

At times can be a little confusing when it comes to downloading reports or changing template mock data, especially in the new UI. But that could also be just me taking more time to get used to it.

What problems is the product solving and how is that benefiting you?

We get to batch our emails on the platform, lowering the noise in people's inbox. Plus customize emails with branding for each customer.

What do you like best about the product?

I like that SuprSend has a nice UI. The integration is really nice and technical support on Slack has been really useful. It's great to have help available in the Slack channel to sort things out. They fix issues quickly when things aren't working properly. The translation integration is really nice because we can automatically send and fully transfer things to our users without much overhead. It's easy to work with, and I also think the SDK made the setup pretty easy, especially for phone user registration. The documentation is good as well, and it works well with other tools like Phrase for notification setup.

What do you dislike about the product?

It's a pretty new platform, and it shows its age at times with things not working properly in places. However, they tend to fix issues quickly when brought to their attention.

What problems is the product solving and how is that benefiting you?

I use SuprSend for sending push notifications, registering devices, and handling non-existent devices.

What do you like best about the product?

Easy to use platform for managing all of our communications.
Low on cost.
Responsive team.
Easy intuitive integrations.
Quick development time for requested features.
They have been quite helpful on many fronts including helps in debuggin and responding to external incidents.

What do you dislike about the product?

No major recommendation here. It does what it is intended for.
If they can adds monitoring / alarm features that would be helpful.

What problems is the product solving and how is that benefiting you?

Managing our email, notifications. Translations for these messagings. Logging and trails for emails + notification.

What do you like best about the product?

The platform is quite easy to use, there are plenty of options and metrics where we can analyze what is happening, as well as search for errors in the creation and execution of workflows.
As I work as a QA, I am always analyzing the execution of workflows and the information displayed there is quite useful.

The test mode in the test environment also helps with the creation of test users, as well as the easy change of environment, where we can analyze how the workflows were executed in the production environment and how we can reproduce them in the test environment.

The support team is also very helpful, always responding when we find a bug. Workflow execution is also quite fast, maintaining highly optimized performance.

The integration with our platform was also done quickly, and whenever we need to make updates, we can do so in a short amount of time.

What do you dislike about the product?

The cost per additional notification can feel a bit steep, but the batching system lets us optimize both the sending process and the overall number of notifications we send.

I haven’t used the AI system yet, so I don’t have a clear opinion on it at this point.

What problems is the product solving and how is that benefiting you?

Suprsend handles workflow construction and data reception from our platform in a highly optimized, straightforward way. Before using it, we struggled to manage the massive volume of notification data being generated. Now, with Suprsend’s UI, everything is much clearer and easier to organize.