The Courier Blog

How to build B2B customer journeys

In B2B the account is the unit of value, not the person. Twelve people share one login, the person who trips the event is rarely the one who should hear about it, and consumer lifecycle flows get all of that wrong. Here's how to build customer journeys in Courier that reason about accounts: account fields on the payload schema, the four trigger types, per-customer settings read from tenant data, a send node addressed to an admin instead of the user who clicked, experiments bucketed by account, and one call that cancels every run on an account the moment it converts.

Audit Notifications with Cursor or Claude Code

Most teams can't answer a basic question about their own product: what notifications are you sending, and are they working? This post walks through a full notification audit using Courier's CLI and MCP server from inside your coding environment. You'll inventory every template, pull delivery logs to surface failures, trace messages end to end, inspect rendered content for stale copy, map the data feeding each notification, break down delivery health by tenant, check preference coverage, and build a hit list of notifications to kill, revise, or batch. All from the command line. Takes about an afternoon.

Design Studio + Journeys: The Engineering Integration Guide

This is the engineering guide for setting up Design Studio and Journeys. When you move notification logic to Courier, your architecture shifts from a push model to an event model. Your backend stops rendering templates and managing provider APIs directly, and starts emitting events. This guide covers both integration paths (direct API and Segment), how to structure the data object so PMs can build without asking for backend changes, error handling and idempotency, how to use test environments safely, and the specific code you can delete from your repo once it's running.

Courier MCP: Let your AI agent handle customer messaging end to end

The Courier MCP server lets your AI agent send notifications, manage users, debug delivery, and trigger automations. If you can do it in Courier, your agent can too.

Customer Journeys Then and Now

Most customer journey platforms don't use product data. They use marketing data. Open rates. Click-throughs. Maybe a segment based on what plan someone's on. That's not a journey. That's a drip campaign with extra steps. I spent years building behavior-based lifecycle programs at Yahoo. The decisioning was sophisticated. The organizational overhead to ship it was not. The infrastructure layer has finally caught up. Here's what behavior-based journeys looked like then, what most teams settled for, and what's actually possible now.

iOS 27 UISceneDelegate push notification deadline: What breaks and how to prepare

Apple is making UISceneDelegate mandatory with the iOS 27 SDK, expected September 2026. Apps that don't adopt the scene lifecycle will crash on launch, killing APNs token registration and all push notification delivery. This guide covers the full timeline, cross-platform impact for Flutter and React Native, and a practical action plan.

Journeys: AI-powered orchestration for customer messaging

Journeys is Courier's visual workflow builder for multi-step customer messaging. Orchestrate flows with branching, timing, personalization & built-in AI agents, then deliver across every channel and debug each run node by node.

Your AI agent already knows how to use a terminal. Why CLIs beat MCP servers

LLMs already know how to use a terminal. We maintain both an MCP server and a CLI at Courier, and the difference tells you something about where AI tooling is heading.

How Product Teams Build, Test and Ship Multichannel Notifications in Design Studio

Product teams need to build, test, and ship notifications across multiple channels without filing an engineering ticket every time. Courier's Design Studio is the workspace for that: a template builder, visual channel routing, omnichannel testing, and publishing in one place. This post walks through the traditional template designer paradigm, how it splits effort across too many tools, and outlines a path for product and growth teams to ship transactional, product, and marketing notifications from a single workspace.