March 2026 Summaries

In a detailed overview of conducting a notification audit using Courier's CLI and MCP server, the text explains how teams can evaluate the effectiveness of their notification systems by inventorying templates, pulling logs, tracing messages, and mapping data dependencies. The audit process involves examining the status of notifications, identifying issues such as undeliverable messages, and ensuring proper data flow and template integrity. For B2B products, it is crucial to assess notification health per customer organization, checking for delivery failures and outdated configurations. Preference coverage is also emphasized to mitigate churn risk, ensuring users can opt out of non-transactional notifications. The text advises creating a hit list to categorize notifications for actions such as revision or investigation based on engagement and delivery metrics. It further highlights the importance of integrating Courier's AI tools for enhanced notification management and suggests obtaining a Courier API key and setting up the MCP server to streamline the auditing process.

In a comprehensive comparison between Courier and Customer.io, two leading customer engagement platforms, Courier stands out as a robust solution for product teams, growth engineers, and developers focusing on B2B customer journeys driven by product events and user profiles. It offers an intelligent messaging infrastructure that integrates with various channels like email, SMS, Slack, and Teams, while providing features such as omnichannel orchestration, an in-app notification center, AI-assisted operations, and granular preference management. Courier charges based on message sends, which suits businesses with high-frequency notifications. In contrast, Customer.io caters to marketing and CRM lifecycle teams, emphasizing deep segmentation, object-based data models, and experimentation tools suited for lifecycle campaigns. It charges based on customer profiles, appealing to companies with large databases engaging in profile-centric campaigns. Both platforms support in-app messaging and transactional notifications, but they differ in their pricing models, core focus, and the depth of their preference management capabilities.

Courier's MCP server is designed to handle customer messaging end-to-end by allowing AI agents to perform tasks such as sending, tracking, debugging, and managing messages, user profiles, and preferences seamlessly. It supports integration with various tools like Cursor, Claude Code, Claude Desktop, Windsurf, VS Code, and the OpenAI Responses API, requiring only an API key and minimal configuration for setup. This server offers a structured tool interface that is beneficial when building chatbots or support tools that need programmatic access to Courier's functionalities. While the MCP server provides an interface for tool integration, the Courier CLI is another option for terminal-first environments, offering comprehensive API access suitable for shell scripts and CI/CD pipelines. Both the MCP server and CLI cover the same API functionality, allowing users to choose the option that best fits their workflow needs, whether they connect through a tool interface or directly via a terminal.

In the evolving landscape of customer journey platforms, the shift from traditional marketing data to product behavior data has transformed how companies engage users. Originally, platforms relied heavily on marketing metrics like open rates and click-throughs, which often led to inefficient and overly complicated processes requiring extensive coordination and engineering resources. However, advancements in the data and orchestration layers, notably through tools like Twilio Segment and Courier's Journey builder, have simplified the integration of product event data, enabling more sophisticated, behavior-driven engagement strategies without the need for extensive technical involvement. These new platforms allow non-engineers to design and implement complex workflows using drag-and-drop interfaces, incorporating AI for real-time personalization and multi-channel orchestration with fallback options. This democratization of data access and workflow creation empowers teams to launch lifecycle programs rapidly, significantly reducing the time and resources needed compared to previous methods, which is exemplified by Courier's approach that natively understands product data and integrates seamlessly with existing systems.

With the advent of iOS 27, Apple is enforcing a mandatory transition from the AppDelegate lifecycle to the UISceneDelegate lifecycle, a change that has been signaled since iOS 13. This shift will significantly impact app functionality, especially push notifications, as apps without scene support will crash on launch, preventing the acquisition of APNs tokens necessary for notification delivery. Developers using native UIKit, Flutter, or React Native must ensure their apps are updated to comply with this requirement by September 2026, when the final iOS 27 SDK is released. During this transition, developers are encouraged to reassess their notification strategies, considering multi-channel approaches to enhance communication resilience across platforms. Services like Courier can facilitate this by managing token lifecycle and offering multi-channel routing, ensuring notifications continue even amidst platform changes.

Courier has launched "Journeys," an AI-powered orchestration tool designed to enhance customer messaging by allowing users to create complex, multi-step notification workflows using a visual editor. This new feature enables businesses to design comprehensive customer experiences by integrating AI agents directly into workflows, facilitating personalized communication without the need for extensive custom engineering. Journeys supports the creation of adaptive flows that respond to user actions, manage sequence timing, and personalize messages based on real-time data, all within a single canvas. Additionally, the inclusion of AI nodes allows for advanced tasks such as user classification, personalized notifications, and profile enrichment, utilizing models like GPT-5.4. While Journeys represents a significant advancement over Courier's previous Automations offering, it currently coexists with it, providing users the flexibility to choose the best fit for their needs.

Courier's Design Studio streamlines the process for product managers and growth teams to build, test, and ship multichannel notifications by providing an all-in-one workspace that integrates template building, channel routing, testing, and publishing. Unlike traditional messaging tools that require coordination across multiple platforms and tools, Design Studio consolidates the entire notification workflow, allowing users to create tailored content for channels like email, SMS, push, and in-app messages while sharing common personalization data. The platform features a visual routing map to manage delivery paths and failovers, and it supports omnichannel testing to ensure message accuracy before publishing. While initial setup, such as provider integrations and API configuration, requires some engineering input, ongoing management is self-serve, empowering teams to handle transactional, product, and marketing notifications efficiently without the need for continual engineering involvement.

The Courier CLI has been revamped to offer full access to the Courier API, allowing developers and AI agents to send and manage messages across various channels directly from the terminal. This new version enables seamless integration with platforms like Cursor and Claude Code, providing a consistent command pattern for handling messages, profiles, lists, and more, with the added benefit of being a standalone binary for macOS, Linux, and Windows. AI agents can perform complex tasks by chaining commands together, such as sending notifications, investigating delivery issues, and managing user profiles, all with machine-readable output for automated decision-making. The CLI is designed for ease of use with no configuration files or complex setup, requiring only the installation of the CLI and setting of an API key to get started, with additional options for structured tool access via the Model Context Protocol (MCP). The CLI also supports CI/CD processes, debugging, and scripting, making it a versatile tool for developers seeking to streamline their notification infrastructure.

In the debate between command-line interfaces (CLIs) and Model Context Protocol (MCP) servers, the text highlights that CLIs are more effective for AI agents due to their extensive documentation and the embedded knowledge in large language models (LLMs), which have been trained on a wealth of terminal-related data available on the internet. While the MCP's vision of creating a universal protocol for tool integration is commendable, its implementation requires loading tool definitions into context, which can be cumbersome and inefficient compared to the inherent understanding that models have with CLIs. Despite MCP's strengths in tool distribution and structured SDK access, especially in environments lacking a terminal, CLIs remain the preferred choice for direct agent interaction due to their simplicity, composability, and transparency. The practical advice for developers is to build robust CLIs with consistent patterns and structured outputs, as these align with how models naturally process information.

Courier has introduced Design Studio, a new multi-channel notification designer currently available in public beta, which aims to streamline the process of crafting customer messages across various platforms such as email, SMS, push, inbox, Slack, and Microsoft Teams. This tool is designed to simplify message creation by allowing users to build notifications using a drag-and-drop editor, offering specific editors for each channel to tailor content without the need for separate tools. Email messages, being complex, receive special attention with features that provide full formatting control and the ability to switch to HTML mode for more intricate customization. Design Studio also includes functionalities for testing and tracking changes, such as previewing templates with real data, sending test messages, and maintaining a complete change history for templates with easy rollback options. Existing users of the Classic Designer can transition to Design Studio at their convenience, with the new tool designed to enhance user experience without disrupting current workflows.

Courier has integrated OpenTelemetry (OTel) to enhance notification observability by exporting logs and metrics directly into users' existing observability stacks, such as Grafana and Datadog, allowing for comprehensive monitoring alongside other application metrics. This integration addresses the often-overlooked area of notifications, which play a critical role in various product functions but can fail silently without proper monitoring. OpenTelemetry, backed by the CNCF, provides a standard protocol for telemetry data that is compatible with most major observability platforms, eliminating the need for proprietary solutions. Courier's implementation of OTel is straightforward, requiring minimal setup, and allows users to track crucial metrics like delivery failure rates and channel performance, thereby transforming notifications into a first-class citizen within the observability framework.

EU data residency is becoming increasingly crucial for notification platforms, particularly for services targeting European users who require compliance with both GDPR and data residency regulations. This is because notifications inherently involve personal data, including recipient identifiers and behavioral signals, making data residency a key compliance factor. Courier, for instance, offers a dedicated EU datacenter in AWS Ireland, ensuring data is processed and stored within the EU, providing full feature parity between US and EU regions. This approach helps avoid cross-border data transfers, which can lead to compliance risks under European regulations such as Schrems II. Additionally, supporting multilingual notifications is vital since users in Europe often speak various languages, necessitating platforms to offer robust localization options. Evaluating a notification provider involves checking not just for GDPR compliance, but also where data is physically stored, ensuring feature parity across regions, and having a seamless migration path for existing infrastructures. Common mistakes include assuming third-party providers cover data residency or overlooking in-app notification data as PII. It's essential to manage translations effectively to maintain compliance and functionality, as these factors are interconnected in serving a European audience effectively.

The landscape of customer engagement platforms is increasingly fragmented, with different tools designed for various purposes such as campaigns, support automation, and transactional notifications, each operating with distinct data models and definitions of "customer." This fragmentation leads to operational inefficiencies, including message duplication, tone inconsistency, and user fatigue due to uncoordinated messaging efforts. The solution lies in introducing a shared message orchestration layer that unifies these disparate systems by managing routing, user preferences, and delivery reliability across all channels and message types. This orchestration approach, likened to air traffic control, coordinates notifications to ensure timely and relevant delivery, thereby enhancing user trust and engagement. By integrating product data into messaging logic and treating both lifecycle and transactional messages within the same framework, organizations can shift towards a more cohesive and effective customer engagement strategy. As the category converges, the focus is moving from isolated campaign or API-driven models to a comprehensive orchestration-centric approach, crucial for product-led growth organizations to maintain a unified messaging experience.