Knock Reviews & Product Details

I like how Knock empowers marketing to run their own campaigns with its features and allows engineers to contribute significantly to marketing workflows. The design system is a plus, with well-defined environments and workflows promoted easily between development, staging, and production with Git storage support. This setup makes collaboration more efficient, and leveraging their CLI or opening repositories in VS Code makes modifications simple. I appreciate the way Knock has resolved issues I had with other platforms, and the speed at which the team responds to bugs and feedback is impressive, often within minutes during business hours. Their customer service is phenomenal, prioritizing customer needs and communication. One of Knock’s standout features is the option to bring your own API keys for communication services like email and SMS, which is more flexible than being restricted to a specific platform's service. This scalability and modular approach is a game changer for my operations. Review collected by and hosted on G2.com.

Honestly, nothing. 11/10 service. I wanna use it for all my projects. Review collected by and hosted on G2.com.

I think the product is really easy to use, optimizing both for developers and non-developers. The MCPs and AI tooling are really nice because they enable me to build things fast, and the nontechnical team members can edit easily. I find the commit system well thought out because it helps prevent things from breaking and allows for multiple people to work together via branching. I really value their support, as I'm getting fast response times over Slack, which allows me to resolve most of my issues quickly. Review collected by and hosted on G2.com.

We've had transient slowdown issues and small bugs, which is of expected from a company moving very fast. We use our own custom CRM to send SMS, so I had to build the integration myself and it was slightly annoying. There are also minor inconsistencies with say how webhooks are signed (ie. outbound vs channel). None of these are major issues, just expected immaturity at this size. Review collected by and hosted on G2.com.

I find Knock invaluable for centralizing and streamlining all our product notifications across multiple applications and environments, eliminating slow, error-prone processes of managing custom notification logic, templates, and delivery channels. I appreciate the clean, consistent, and well-documented APIs, which make integration seamless even without the SDK. The workflow builder is a fantastic feature, allowing us to visually manage notification workflows with steps, delays, batching, and conditional logic. This functionality saves a huge amount of engineering time and removes the necessity for a custom pipeline. Additionally, I value the excellent support provided by Knock, particularly the Slack support channel, where Jeff offers outstanding assistance. The initial setup of Knock was incredibly easy, facilitating a timely integration into our systems. Review collected by and hosted on G2.com.

The only concern I have is about the logging and debugging aspects of Knock. However, I haven't checked their latest releases, so it might have improved since then. Review collected by and hosted on G2.com.

I really like the scheduling feature; I like how it removes most of the complexities of running jobs on my backend and thinking about how to fully manage notification schedules. I like the other additional add-ons (like throttling), which is something I use a lot right now for my unique needs. It was nice talking to support and sharing ideas on how to set up the workflows that I use for schedules so that they tailor to my system's specific needs. It was fairly easy to set up and integrate with my backend, and I use this feature the most.

Another honorable mention is user preferences, another powerful feature! Review collected by and hosted on G2.com.

I don't think I have found the documentation the most useful in some cases. For example, when I was setting up/thinking about throttling on some of my workflows, the documentation didn't explain using and setting it up well enough in my opinion. I ended up having to reach out to support just to be sure I had set it up the right way. I don't think the AI model that is currently there answers my questions enough.

I also noticed that the API for setting user preferences doesn't merge preferences properly; instead of relying on the user's current preferences to merge with the update, it falls back to the default. I had to implement the merging on my backend to avoid all of this. Review collected by and hosted on G2.com.

Very developer and PM friendly (assuming your technical) compared to some product focused at marketers that are too complex to integrate, works with our existing email sender, easy to get started, and quick implementation, outstanding support from the Knock team via both email and Slack (and they fixed issues we ran into). Beyond just support, knowing that items that are important to your success are a priority on their roadmap makes me feel comfortable with a long-term relationship.

I was tasked with finding a solution that could help us manage email and push notifications, user preferences, and keep our templates/content our of the code base. It needed to be developer-friendly and easy to implement quickly, and Knock stood out for what we needed at the time. Our engineering team was happy with it compared to solutions some have used in the past.

As a PM, I love how much I can do myself without engineering changes. The different environments make it easy to test things.

API support is great, and with some help from Claude I have even been able to script some things I needed to do vs ask my engineering team.

Template and content management is good, and ite easy to build and modify workflows.

I use knock a lot to manage onboarding and engagement notification workflows, send broadcasts, etc. Review collected by and hosted on G2.com.

Product Documentation could be improved, though I have used Claude and ChatGPT with pretty good success to get past those gaps; otherwise, ask their customer service team or test things out.

We encountered some limitations with user preferences regarding commercial unsubscribe, and it would be beneficial to have a Knock preferences UI that we can direct people to from an email to help manage compliance.

Lack of dynamic audiences is a limitation that is in the roadmap.

I wish more integrations could bring in user properties, as I would love to import properties from our PostHog instance, not just events.

Sometimes I wish it could do a bit more on the marketing side - the longer I can hold off on ANOTHER system in our stack the better. Review collected by and hosted on G2.com.

I like how easy it is to just have an endpoint we can call to schedule notifications. It's especially beneficial when dealing with notifications that need to be sent in the future. Within those workflows, it feels pretty easy. Review collected by and hosted on G2.com.

I think that I would like to be able to use codebase interface, maybe through the CLI. Handling a notification engine, we pretty much have to build that part of the infrastructure ourselves. I would like to have more of a condition-based event approach. Let's say that whenever an event happens, then look for other conditions to see if the user met that requirement so that we can build an identification engine. Right now, I don't know if it's possible to do. So that part of the infrastructure we built ourselves. Review collected by and hosted on G2.com.

Knock has been a boon for us. It’s easy to set up, powerful, and clearly built for both PMs and engineers. We started out manually coding every email in our SaaS app, but once we needed multi-channel support and more complex workflows, it became unmanageable. I randomly came across Knock on Twitter, checked out the demo, and with just me (a product lead) and one engineer, we had over 10 workflows running across email, SMS, and in-app within weeks. Review collected by and hosted on G2.com.

There is nothing I dislike. I would highly recommend this. Review collected by and hosted on G2.com.

I lead the implementation of Knock in our stack, and it’s one of those rare tools that gets the balance right between being developer-friendly and marketing-team friendly.

From an engineering perspective, my job is to simply wire up triggers and send data from our app. From there, our copywriters and marketers can own the templates without needing me in the loop. That separation of concerns has been a huge productivity boost.

Knock has also gone far beyond just "send a notification." Features like schedules and delayed notifications mean we don’t have to waste time setting up cron jobs ourselves. The logging is excellent too, it’s easy to debug and see exactly what’s happening.

The development workflow is one of the standout parts for me. Multiple environments, the ability to incrementally push changes, and even seeing commit diffs on workflows, it feels like Knock was built with real engineering teams in mind.

Other highlights:

- The free tier was more than generous enough to cover our POC.

- Sandboxing notifications helps us avoid burning through third-party usage.

- Support has been unreal, even from the other side of the world, questions in their Slack community get answered quickly.

- The workflow builder is incredibly powerful, with branching, batching, conditions, and customisations that make it easy to design complex flows that were simply not possible when we were using a different product and we had to add a bunch of messy workarounds

Ultimately, Knock is a tool that knows what it’s good at and does that really well. That’s exactly what I want as an engineer, and it’s exactly how I’d describe our experience with it. Review collected by and hosted on G2.com.

I would really like to be able to access the data for more than just 10 activities in my templates.

Being able to edit delayed workflows instead of cancelling them and triggering them again would also be helpful.

But that is splitting hairs. Review collected by and hosted on G2.com.

Knock has been our go to for all of our notifications and has been our trusted service in communicating alerts and messages to our customers.

Integrating with knock was a breeze and their documentation has been good enough for any one to easily pickup.

In the few times I had emailed for support, I have always gotten excellent support from them and currently I cant see a world where I woudlnt use them Review collected by and hosted on G2.com.

** The analytics page needs to provide more information with better filters

** The new UI is not as intutive as the old one when it comes to selectiing environment

** Would be nice to have a sandbox mode per worflow instead of a channel

** Review collected by and hosted on G2.com.

We've been using Knock since its early days, and it is one of the best infrastructure messaging tools out there. Its intuitive setup and seamless integrations make it incredibly easy to get our own tools up and running quickly. The documentation is comprehensive and easy to navigate, and the customer support team is outstanding—responsive, knowledgeable, and among the fastest we've encountered. Review collected by and hosted on G2.com.

One of our key feature requests is for ticketing integrations—as a customer‑facing company, this would help us avoid the constant cycle of building custom ticketing solutions, and let us define a ticket once and see it across all our apps.

We’d also like more environment decoupling. Currently, promoting changes requires applying them in all environments, which becomes overly complex for heavy customisations and dedicated or on‑prem deployments. Review collected by and hosted on G2.com.