OneSignal

My main use case for OneSignal is in-app messaging and push notifications in our app.

A specific example of how I use in-app messages or push notifications with OneSignal involves the Journey feature, where I create certain campaign scenarios and set them up as CRM message campaigns.

A typical example of those campaigns would be onboarding, where if a user signs up but does not complete a key action, I can wait for a certain period and send a push notification. If they still do not engage, I can follow up with another message or a different channel.

I also used OneSignal for a retention use case, which involves segmentation of users who visit our website but do not take any specific action there. I then target those cohorts and send reminder in-app messages or in-web browser messages if they return.

The best feature OneSignal offers is the Journey feature, which is the most powerful function.

What makes the Journey feature so powerful for me is that it includes both automation and customization. It can be the automated campaign for a certain user scenario, so if I imagine something, I can make it happen as automatically set campaigns with the Journey feature.

OneSignal has positively impacted my organization as it was the very first CRM messaging SaaS in our company, making it really easy to implement.

I can share specific outcomes from using OneSignal. I first used it from the very beginning of the establishment of the CRM messaging system itself, and all those results were our first step, which improved significant results through certain CRM activity.

I am not certain how OneSignal can be improved, but recently there are so many good CRM systems and software in the field that I can name more than five of them that I have not even experienced. This indicates a need for some special distinction through special features or values that only OneSignal can provide to the field or customers.

In marketing, when a company tries to search for CRM tools, there can be uncertainty about the reasons behind the decision to start with OneSignal. I think this is definitely related to the pricing system, which is relatively cheaper than other well-known CRM messaging tools. While the price does not pose any problems, the question remains on how OneSignal can become more famous among CRM marketers in the field who are willing to use it and partially have decision-making rights. From my experience, OneSignal's product marketing is not as powerful compared to much more well-known CRM messaging tools, so improvements can be made.

I have used OneSignal for around one year.

When I used OneSignal in my country, South Korea, there was no localized customer service, so I had to communicate in English. Fortunately, I can speak English, so it was no problem, but if there were no one who could speak English, that could have been trouble. That was a few years ago, and I am sure that OneSignal currently has some localized customer support systems or teams in South Korea.

Before OneSignal, I did not use other CRM tools in that company.

Before choosing OneSignal, I wanted to adopt Braze first because at that time, that was the only tool that I knew. However, our superior, who was the decision-maker, decided to adopt OneSignal instead, so I had no other choice.

My advice for others looking into using OneSignal is to recommend it to mobile-first companies, SaaS businesses, or e-commerce companies that want to improve activations, retention, and engagement through push, in-app messages, emails, or SMS, as it can be serviced by itself. It is especially suited for companies that want to launch quickly without building their own messaging infrastructure.

OneSignal is a great tool that is really easy to adopt, and I especially recommend it for the beginning of a business.

OneSignal is deployed in my organization on our private servers. I rate this product a 9 out of 10.