Setting up a password reset workflow inside your web application can be challenging. At a minimum, you need to build the logic to update the user’s password with a new hash, send the appropriate emails with the right content, and manage different user sessions across browsers. If you’re responsible for managing password reset emails, it’s likely that you also have to manage all aspects of authentication and password management for your application.

Transactional emails are automated emails triggered by a user (or group of users) taking action on your web or mobile application. Some examples include password reset emails, confirmation emails for purchases or reservations, welcome and onboarding emails, and shipping notifications.

When you’re building a web application, there’s an immediate decision to make about how to handle Users and Authentication. There are lots of services (Auth0, Clerk) and libraries (Passport.js) to choose from, and the right choice will depend on the requirements of the application that you’re building.

Send limits are a new addition to the Courier app that allow you to manage notification rate limits. This means you can set a maximum limit on the number of notifications you can send over a certain time period. The advantages of using send limits are twofold: you can save money by imposing spending caps on notifications, and you can improve the customer experience of your app by avoiding bombarding users with too many notifications at once.

We are excited to announce the official launch of One-Time Send, a powerful feature designed to simplify and expedite the process of sending one-time notifications through Courier. It's one piece of a web app redesign that we started recently (dark mode shown coming soon). Based on invaluable feedback from our customers during the closed beta, we have refined and improved One-Time Send to make it even more efficient and user friendly.

Today, we are embarking on a significant redesign of Courier's interface consisting of some new things, some old things in new places, and an overall reorganization of the information architecture. This redesign aims to address the challenges that come with the growth of our platform, where increased size and number of features leads to increased complexity, resulting in a product that may not be as intuitive for new users.

We are excited to introduce Guard Rails, now in open beta for Courier, a feature that allows you to set upper limits on the number of messages sent per time period. Courier business plan customers can configure these limits globally, or per user, or per user per subscription topic. Exclusions for certain subscription topics can also be set up, ensuring essential messages are always delivered.

We added the ability to customize the message icon for inbox messages. That means you can set a different icon for each type of notification that you send. To do this, Message Icons needs to be enabled in your brand’s in-app settings (they should be by default). Then you can add an icon to your notification template.

All apps need a solid, automated notifications system. Whether it’s reminders, updates, or alerts, some notifications can be urgent and time-sensitive, in which case SMS is the most effective communication channel. Let’s take a moment to talk about what that means for you as a developer. You need to: Realistically, building this feature from scratch can be time-consuming and complicated.

The ability to unify all notification metrics and logs across channels and providers into an easy-to-use dashboard is a core advantage of Courier’s notification infrastructure. However, with product notifications so critical to the entire application experience, it’s important to connect that data back to central cloud observability platforms that look across the entire stack.