March 2021 Summaries

Transactional emails are critical to business apps' success, sharing important alerts and valuable information with customers. With a higher open rate than marketing emails, transactional emails provide an opportunity to upsell, retain, and engage customers who already use services. A good transactional email template should include strong metadata, clear subject lines, preheaders, personalization, and a well-structured message that guides the reader from top to bottom. The design and content should capitalize on the reader's attention, leveraging graphics and creative design to convey the brand identity. Templates should be reusable, customizable with brands, and include multiple variables for personalization. A good template should also cater for consistent rendering across mobile devices and email clients. Everyday use cases for transactional emails include account creation, welcome emails, ecommerce messages, confirmations, reminders, proactive support, and workflow messages. Examples of effective transactional emails include welcome emails from Asana, shipping confirmation emails from Tradesy, reminder emails from Fullscript, invitation requests from Twist, email verification emails from Republic, and workflow notifications from DocuSign. Transactional email templates can be created with tools like Courier's notification design studio, empowering teams to quickly create on-brand, engaging templates that meet the needs of customers.

Sending email notifications is crucial for maintaining strong relationships with customers, improving user productivity, and driving engagement. However, building an email notification system can be complex due to its five core components: content creation, rules engine, customer preferences, deliverability, and tracking. Empowering the product team through templates, enabling intelligent routing with a rules engine, respecting customer preferences, ensuring deliverability, and tracking behavior are essential for creating a scalable and effective email notification service. Leveraging existing services or solutions can also save time and money by not reinventing the wheel.

Creating a perfect notification strategy is challenging due to constantly changing user preferences and behaviors. Notifications must contribute to the overall user experience, improve productivity, and help users accomplish their goals without annoying them. A well-defined notification system with a clear purpose adds value for users, improving their experience within an application. Designing such a system requires identifying the outcomes desired, defining triggers for notifications, grouping them based on importance, selecting channels, designing individual notifications, giving users control over their preferences, and adapting to changing user needs through data-driven approaches and A/B testing. Best practices include personalizing messages, ensuring they relate to the user's current activity and offer immediate value, tailoring messages as relationships with users develop, and avoiding common notification design missteps such as sending multiple notifications for a single message or disrupting users' routines.

Several push notification services are available, including Airship, Expo, Firebase FCM, OneSignal, Amazon SNS, and Catapush. Each service has its own strengths and weaknesses, with varying levels of documentation, pricing, and features. For example, Airship is a comprehensive platform that offers reliable delivery of billions of notifications in real-time, while Expo is a free framework for React Native-based applications. OneSignal is known for its powerful analytics tools and flexible pricing, while Amazon SNS offers a simple API and flexible pricing. Catapush is designed specifically for sending data-driven notifications and offers a unique two-way communication feature. The choice of service ultimately depends on the app's requirements, team resources, and budget.

Transactional email is complex, and many software teams assume building their own notification system without considering the complexities and size of the undertaking. While sending transactional emails is crucial for delivering important information from products, it's more complicated than expected, requiring ongoing development tasks such as implementing a job queue to counter performance impacts. A clear view of the scope and resources required are essential before deciding whether to build or buy an email notification system. Key features of a successful system include fast integration with an email service provider, easy templating and template management, intuitive orchestration, respecting recipients' preferences, and robust logs and retry mechanisms. Buying a notification system provides immediate value, frees up engineering teams to focus on core product development, and offers advanced capabilities such as reusable templates, multichannel functionality, and optimized deliverability. It also gives businesses a competitive advantage by empowering their product teams from the start, improving customer interaction, and allowing them to quickly implement new opportunities to engage with users.

Sending emails is a crucial aspect of software development, and Python offers several ways to achieve this. The three main options are using SMTP, a transactional email service like SendGrid or Mailgun, and a multichannel notifications service like Courier. SMTP is a cost-effective and readily accessible channel for reaching users, but it has its limitations, such as security concerns and slower send times. Transactional email services offer more features and better deliverability rates, but require integration with third-party APIs and may have a learning curve. Multichannel notifications services provide a single API to notify users across multiple channels, making it easy to manage cross-channel delivery and reduce code maintenance. Python's built-in smtplib module can be used to send emails via SMTP, while transactional email services like SendGrid offer easy integration with Python through APIs. Courier provides a multichannel notifications service that allows developers to send programmatic emails using Gmail or other email providers. With these options, developers can choose the best approach for their software product's needs and start sending notifications efficiently.

We've released an in-app support center to help users get started with integrations and provide information about new feature releases, updates, and roadmap plans. Our recipients list now allows searching, sorting, and editing of recipient data, while 7 new channel integrations have been added, including Apple Push Notification and Pushbullet. A Java SDK is now available for developers to send notifications faster. Additionally, we've introduced plain text rendering for emails and showcased recent developments such as the Slack notification system and a Twitch notification tutorial. The Courier community has also grown on Discord, where users can get help, share ideas, and chat with the team about building notifications and upcoming product changes.