Knock offers valuable insights that help non-developers clearly understand how outbound communications will look and feel before they're sent. The post-send preview and the ability to adjust for different email clients make it easy to see exactly what users will receive. Additionally, Knock consistently delivers thoughtful quality-of-life improvements that benefit both developers and non-developers alike.

Additionally, the Knock team has helped us at every turn in getting our integration set up. We are now up and running with Knock & our users are loving the look and feel of our new emails. Review collected by and hosted on G2.com.

Definitely a developer first platform so it takes a bit of learning to make small tweaks to workflows and messaging. Some of the tooling and actions are double nested so it can take some time to find what you are looking for. Review collected by and hosted on G2.com.

It's helped us orchestrate all of our notifications in a simple scalable way. Review collected by and hosted on G2.com.

I wish there was a better way to filter and search. Review collected by and hosted on G2.com.

Knock is very developer-friendly. Its packages for Node and React make it easy to code both the UI and the logic behind sending notifications. Knock also documents its product well, making it very easy to use and implement.

At my company, we use Knock daily to send users notifications about topics to which they subscribe. Knock made this surprisingly easy; I only had to write a minimal amount of code. Knock also made it easy for me with guides and API references that provided exactly the information I needed. Review collected by and hosted on G2.com.

I dislike the way Knock's environment system works. Most other services treat environments like a collection of separate settings. Although Knock does do this, it also ties environments to its commit system. This makes it difficult to promote/implement changes because it means I must push each one through each environment. This also means that developers might need to share a single environment unless the company wants to create one for each developer. In some cases, this means developers could accidentally send test notifications to each other. Knock also lacks a few basic features for environments, such as the ability to edit environments' names. These factors deter me from using Knock's environment feature. Review collected by and hosted on G2.com.

After evaluating several notification providers, Knock was the clear winner on several fronts. The level of customization that can be achieved due to their very well-thought out APIs and SDKs made it an absolute dream. While many other providers force particular approaches, Knock allowed us to completely tailor the experience in line with our vision. On the backend side of things, they provided SDKs for many different environments which was also a huge plus for us. Finally, from a conceptual point of view, the well-thought out concepts, entities, and workflows meant that our imaginations were really the only limit for how to leverage the platform. Review collected by and hosted on G2.com.

This could be a pro or con depending on how you view it, but because the system is so flexible, there are quite a few different ways you could make use of some of the concepts. You need to spend some time really thinking through your own business case to ensure you're picking the best way. Thankfully, Knock's team were very helpful with clarification and running an approach by to validate it. Review collected by and hosted on G2.com.

Simple cross-channel notifications, minimal effort required to ship new alerts once configured Review collected by and hosted on G2.com.

Template management, difficult to implement complex template designs Review collected by and hosted on G2.com.

It's easy to get started and start sending notifications Review collected by and hosted on G2.com.

I found the data model with tenants/objects/collections confusing. Also whenever I am in the knock app looking for errors/logs it's hard to find what I am looking for. Review collected by and hosted on G2.com.

Great dashboard and tracking of messages and notifications. The implementation for the api was super quick and easy to set up. Review collected by and hosted on G2.com.

Editing templates can be time consuming, and we've found that the visual editor does not usually give us the flexibility we need, but using the HTML editor means really only our engineers can edit the templates. Review collected by and hosted on G2.com.

the knock setup was fairly intuitive and easy to navigate. Their help team was also always online to support whatever we needed to achieve. The features for automation available was also plentiful and we were able to achieve exactly what we needed. Review collected by and hosted on G2.com.

Figuring out the format of emails was a bit challenging at first, but after some walkthroughs it was easy to replicate. Review collected by and hosted on G2.com.

Clear documentation, easy to implement, reliable notification delivery, very good customer support. Review collected by and hosted on G2.com.

Statistics could be more detailed. It takes some time to dig through the logs. Review collected by and hosted on G2.com.

1. The knock team is readily available to answer any and every question someone might have. I have witnessed this first hand, as we had 3 sessions - and in each of the sessions, they were both very helpful and really excited to help.

2. The knock team is quite responsible and quick to react - I noticed a few issues in their react-native SDK (that were issues because we were using a non-expo, legacy react native project), and they within two weeks fixed the issue for us and also added some additional features that were quite useful for us, as we're transitioning to them.

3. The knock integration is quite easy - and the platform itself is super powerful if you're looking to establish serious and well-versed notification streams. The game changer feature I think for them is the ability to with ease add custom payload "on the fly" (i.e. we wanted to add a field to our mobile notifications without implementing it on our BE, and it was a breeze). Such a great feature, that isn't even highlighted.

4. The implementation itself is a bit of a process, just because you receive so much power to configure heaps of things, but once you complete it, you realize how easy it actually was. Might seem daunting at first but over time it becomes second nature. Review collected by and hosted on G2.com.

1. The documentation is really long and challenging. Of course, all software goes through this, manuals get better over time, but reading it feels like terminology is all over the place and not so clearly defined. I feel like some things are called one thing on one page and on a different page they have a different name. But of course, once you actually read it and let it digest, you get a hang of it.

2. The docs are lacking a little in the react-native examples, as I feel like - given the usage of JS worldwide, it could be more example-rich, as well as include a few sections on common scenarios and recommended best practices. Didn't read the other docs so much (for other languages. Review collected by and hosted on G2.com.