Notifications Landscape

Notification Platform for Developers: API, CLI, and MCP

One API for every channel. A native CLI and an MCP server your coding agent can use to test what it builds. Typed server SDKs in seven languages. Journeys for batching, throttling, and digests. Here's how Courier fits into your stack.

Build notifications with Claude Code, Cursor, and Courier

Ask an AI coding agent to add notifications and it starts building infrastructure. This tutorial sets up Courier Skills, the Courier MCP server, and the CLI in Claude Code or Cursor, then builds an order-shipped notification across Inbox, push, and SMS, tests it against a Test workspace, and hands the copy to your product team.

The Complete Guide to B2B Customer Engagement

Courier provides the notification infrastructure layer for B2B customer engagement, routing messages across email, SMS, push, in-app, Slack, and Teams based on user preferences and product events. Unlike building notification systems in-house—which takes months of engineering time for features like multi-channel routing, preference management, and delivery tracking—Courier handles this infrastructure so product teams can focus on engagement strategy. B2B customer engagement requires multiple layers: notification infrastructure (Courier), customer data platforms (Segment), product analytics (Mixpanel/Amplitude), and channel-specific tools. Companies with strong engagement programs see 15-25% churn reduction. The key is connecting product events to customer communication at the right moment through the right channel, handling complexity like multiple users per account with different notification needs across work channels.

How Top Notification Platforms Handle Quiet Hours & Delivery Windows in 2026

No platform offers per-template delivery windows in 2026—it's either per-workflow (Customer.io, Knock), per-campaign (Braze), or global settings. This comparison shows exactly how six platforms handle quiet hours and send time controls based on their documentation and API specs. Braze leads on AI timing (23% open rate lift from Intelligent Timing across their customer base). Novu is the only platform letting subscribers set their own delivery windows. Customer.io and Knock require manual workflow configuration. OneSignal's strength is push-specific optimization across 300K+ apps. Courier combines per-node flexibility with API control. Includes feature matrix, timezone handling, and frequency capping differences.

Multichannel Notification Template Management: Version Control, Migration, and Cross-Channel Previews

AI agents are reshaping how products communicate with users. By 2026, 40% of enterprise applications will embed agents that need to send notifications across email, SMS, push, Slack, Teams, and in-app channels autonomously. Managing templates across all these channels with Git-based workflows doesn't scale. This guide covers how teams handle version control and rollback for multichannel templates, which platforms enable designer collaboration without deploys, whether Figma design systems can connect to notification builders, how to migrate templates using APIs and MCP-assisted workflows, how to preview messages across channels side-by-side, open-source options that integrate with SendGrid, Twilio, Firebase, and Slack, and how to localize content from one dashboard. Platforms covered include Courier, Novu, Knock, SuprSend, Dyspatch, Email Love, and React Email.

TCPA SMS Opt-Out Rules and the Cross-Channel Gap

The FCC's new TCPA opt-out order takes effect November 25, 2026. Informational opt-outs can be scoped to a category, marketing opt-outs still cover all marketing, and STOP still doesn't reach your email, push, or chat. Here's what changes and how to close the cross-channel gap.

Customer engagement platform vs CRM: key differences

A CRM is a system of record. It stores who your customers are and what they've done, written by people and read by people. A customer engagement platform is a system of action: your product fires an event, and the platform decides who should hear about it, picks a channel they read, and delivers it. You'll likely end up running both, and the handoff between them is smaller than it sounds. Here's what separates the two on data, timing, preferences, and analytics, why their pricing models diverge more than their feature lists do, and how to tell which one your next problem needs.

Flutter notifications: add an in-app inbox and push

Most Flutter apps don't need hand-rolled notification infrastructure. Add Courier's SDK and you get a real-time inbox widget, push for iOS and Android over APNs and FCM, a preference center, and digests. Courier syncs push tokens, tracks read state, enforces preferences at send time, and can mark the inbox message read when the recipient opens the email. The same notification infrastructure Twilio runs on.

Your Notifications Now Have Two Audiences: Humans and AI Agents

AI agents are now filtering, summarizing, and acting on notifications before users ever see them. In late 2024, Anthropic released the Model Context Protocol. By mid-2025, MCP had become the connective tissue for AI agents that take actions on behalf of users. Google followed with A2A. Agentic browsers like Perplexity Comet and Opera Neon started treating the web as something to navigate programmatically. Your notification strategy needs to account for machine interpretation, not just human attention.