Knock

Join us for our Knock 101 livestream, today at 1 PM ET (10 AM PT)! We'll cover how to use Knock to send cross-channel product notifications that reach users on email, SMS, and within your app. https://lnkd.in/eSJHyUeh

📨 The line between a feed and an inbox can be blurry, but with Knock you can power both types of experiences using the same realtime API and React library. In my mind, the real difference comes down to data density and the actions you build on top of those messages. I built out an example app using Next.js and ShadCN UI to explore some of these concepts and show how Knock can form the base of some pretty intricate product features. Stay tuned for some more resources around this...

🤠 Happy Friday from Knock! A few weeks ago, we flew the entire team out to Nashville for our Fall 2024 offsite. We worked, had some fun, and reflected on our favorite shared value: shipping tools to help software communicate with its users. We asked our team about their favorite new feature of 2024. Between SlackKit, Command + K, Knock mobile, and Partials, there’s a ton to choose from. We think you’ll be surprised by some of their answers and our line dancing skills 👢

📺 ICYMI, last week we published an interview with Mike Molinet 🦉 from Thena that digs into their new inbox feature. But this interview also touched on the benefits of sending product updates to shared Slack channels. Knock has been sending its own product updates out via Slack for several months, and the engagement has been fantastic. As individual channels become saturated or less effective, teams need to be looking at how they can create cross-channel experiences for both their transactional and promotional messaging. You can check out the full interview in the comments 👇

🛳️ Shipping today: User and preference data can now sync to your data warehouse. It's now possible to receive a stream of user and preferences changes directly into your data warehouse. This makes it easy to build models that analyze your notification opt-out rates and how user profile information in Knock changes over time. Read more: https://lnkd.in/ebCkmEzf

As Thena’s customer base expanded into larger organizations with higher support ticket volume, they needed a way to surface a centralized view of support tasks, notifications, and ticket updates. Using Knock’s in-app infrastructure, Thena created a configurable inbox in their product to consolidate all interactions into a single interface. This streamlines the support workflow, reduces response time, and ultimately improves customer satisfaction. Our Developer Advocate Jeff Everhart sat down with Thena founder Mike Molinet 🦉 to discuss how this new inbox feature is driving results for their customers. Check out the full video or read the blog post in the comments 👇

We like this Build vs. Buy diagram from the founder of Knock. Before going the homegrown route (or investing more in homegrown), ask yourself: Is this something you're even good at? Is this what you want your devs burning hours on to build? Sometimes the answer is yes, especially if there's nothing on the market that does what you need. A couple of the boxes in this diagram hit a nerve for us because they're highly related. Keeping your build secure is major. Keeping it maintained is major. And if maintenance starts falling off, it threatens security. There's a stage of a company where we think the Build vs. Buy decision becomes really real: the scale-up phase. You're transitioning out of start-up mode and are trying to establish stable, repeatable operations. When you're scaling up, the stakes are higher because you have a lot of established customers. You have a substantial backlog of customer requests hitting engineering, and maybe even some tech debt to unwind. At that point it might be time to buy best-of-breed, and keep your builders focused on the things that only they can do. What are some other moments when Build vs. Buy gets really real? #developers #buildvsbuy

In-app messaging provides product teams with powerful levers to engage and notify users. But teams have to be careful. Without a notification strategy, it’s easy to clutter your UI, create noise, and annoy users. At Knock we dug into the existing UX research around notifications and user attention to create an outline of when, where, and how different types of in-app messaging should be used. Check out the full blog post in the comments 👇

🛳️ Shipping today: support for validating workflow trigger data. You can now provide a JSON schema that describes your workflow trigger data. When provided, Knock will validate your workflow trigger so that your workflows don't run with incorrect data. Read more in our changelog: https://lnkd.in/ee55Jrwj

Excited to be at LeadDev New York today and tomorrow. Come by to talk about notification best practices, chat with the team and grab some swag.