AI

How to Build B2B Customer Journeys

Courier Journeys is an AI-native journey builder for multi-step customer messaging. Build on a visual canvas with branching, delays, live data fetching, AI nodes, and omnichannel sends. Define your payload schema so variables autocomplete throughout the flow. Branch on product events and profile data. Use AI to enrich profiles, drive branching logic, or generate personalized message copy. Throttle messages so customers aren't overwhelmed. Compare draft changes against the live version before publishing. Invoke and test from the CLI or MCP server. Scaffold growth patterns with Courier Skills.

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.

Courier vs Customer.io: 2026 messaging platform comparison

Courier and Customer.io both send across multiple channels, but they're built for different jobs. Courier is a customer messaging platform for product teams: it turns the events and user data your app already produces into notifications across journeys, broadcasts, Inbox, preferences, and AI internationalization. Customer.io is built for marketers running profile-driven campaigns, segmentation, and A/B testing. This comparison covers pricing, workflows, in-app messaging, localization, and which one fits your use case.

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.

Best Email API Providers for Developers in 2026: SendGrid vs Postmark vs Mailgun vs SES vs Resend

Your email provider sticks with you longer than most technical decisions. Courier handles notification infrastructure for thousands of teams, so we went deep on the six email providers that show up most: SendGrid, Postmark, Mailgun, Amazon SES, Resend, and SMTP. This guide covers real API primitives, actual code from each provider's docs, Courier integration examples with provider overrides, and an honest read on where each developer experience holds up and where it breaks down. We also asked Claude to review every API and tell us which one it would wire up first. The answer surprised us.

I Built an AI Board Member in Cursor. Here's How.

Every month I send a board update—and every month I wish someone would tell me what’s wrong before it goes out. Investors are busy, feedback comes late, and most people soften the punch. So I built an AI board member using Cursor Rules: three markdown files, a basic project layout, and no plugins. Drop in your board deck, get an immediate review, and walk into the meeting with fewer surprises.

The Courier MCP Server Is Open Source. Here's How It Actually Works.

Courier's MCP server is open source at github.com/trycourier/courier-mcp. It connects AI coding tools like Cursor and Claude Code to your Courier account so they can send messages, manage users, and install SDKs without hallucinating API details. This post walks through the actual codebase: how 16 tool classes are registered (and how a config allowlist gates most of them), why we pull installation guides from GitHub at runtime instead of bundling them, how the DocsTools class generates live JWTs alongside setup instructions, and what the SdkContextTools class does in the repo to prevent v7/v8 SDK conflicts (even though it isn't wired into the server yet).