AI

Build a Multichannel Onboarding Series in 30 Minutes

A walkthrough of building a four-part multichannel onboarding series (email, in-app inbox, mobile push, and Slack) in 30 minutes: Claude Code and Cowork to orchestrate, Claude Design to mock each channel, Courier Skills to turn mocks into Elemental templates, the Courier MCP server to publish them, and the Courier CLI to send tests. Covers the strategy behind the sequence and how to wire it into a Journey.

Throttling notifications across product, transactional, and marketing streams

A notification throttle that drops every event over a limit works fine for marketing nurtures and fails for product notifications, because product events carry context users actually need. The fix is pairing throttling with auto-batch: overflow events feed a batch node that rolls them up into a single digest, optionally rewritten by an AI node that prioritizes and summarizes the contents. This guide covers per-stream throttle setups for transactional, product, and marketing flows, and how the Courier Journeys AI node and fetch-data node fit into the pattern.

How to Send Notifications from an AI Agent with Courier's MCP Server

AI agents handle support tickets, monitor pipelines, run onboarding flows, and sync CRM data. When they do, someone needs to know what happened. Courier's MCP server gives agents direct access to the full notification API: send across email, push, SMS, Slack, and in-app. Check user preferences before sending. Trigger batch and digest Journeys so high-volume agents don't spam users. This guide covers MCP server setup, CLI tooling, Courier Skills for your IDE, and five real-world patterns with starter prompts.

How to Use Claude Code on Mobile to Design, Test, and Ship Multichannel Notifications

A walkthrough of using Claude Code's mobile app with Courier's MCP server and CLI to design, test, and ship a multichannel product announcement from a phone. Covers the full workflow: drafting the content outline, creating notification templates using Courier's elemental format, building channel-specific variants for email, Slack, push, and SMS, customizing brand styling through the API, iterating on design with test sends, getting team approval, and publishing with custom routing rules. The whole thing took a couple hours, mostly cold start and design iterations.

Debug Delivery Issues in Your AI Editor with MCP

Between quarterly audits, delivery issues don’t wait. When emails fail or alerts fire, you need answers fast. Courier’s MCP server lets you debug notifications conversationally—find the message, trace its timeline, and inspect user data in minutes. Instead of jumping between dashboards, your AI agent pulls everything on demand, surfaces root causes, and even automates investigations. The result: faster fixes, less guesswork, and a smarter, always-on reliability workflow.

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.

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.

Give your AI agents access to your notification infrastructure with the Courier CLI

The rebuilt Courier CLI lets AI agents send notifications, debug delivery issues, and manage users, lists, and tenants across every channel. If your agent has shell access, it has access to Courier.