Product Management

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.

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.

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.

Customer Engagement Platforms Are Splintered. Message Orchestration Is the Fix

Customer engagement platforms are splintered. Some are built for campaigns, others for support automation, and others treat messaging as a transactional delivery problem. The result is collisions, blind spots, and message fatigue. The highest-leverage fix is solving the lifecycle-to-product and transactional vector with a message orchestration layer: one system that routes, suppresses, prioritizes, and observes messages across channels. Think air traffic control for user communications.

What are transactional notifications? Transactional email examples, transactional push, and more.

Transactional notifications are automated messages triggered by user actions or system events, like password resets, order confirmations, and payment alerts. Unlike marketing messages, they require no opt-in and have legal protections under CAN-SPAM. This guide covers what transactional notifications are, how they work across email, SMS, and push channels, real-world examples for each, and how to stay compliant. Whether you're building your first notification system or auditing an existing one, this breakdown will help you understand what belongs in each category and how to route messages correctly.

What's the Difference Between Omnichannel & Multichannel

Most teams say "omnichannel" when they mean "multichannel," and in most cases the distinction doesn't matter much. But if you truly want to provide an exceptional customer engagement experience you should know the difference. Both involve sending messages across email, push, SMS, Slack, and in-app. They terms diverge when those channels know about each other. Multichannel means you can reach users on multiple channels. Omnichannel means those channels share state, so a user who reads a push notification won't get the same message via email an hour later. This guide breaks down the real distinctions, when the difference actually matters, and which messaging platforms deliver true omnichannel coordination.

Personalization Beyond "Hello {{firstName || "there"}}!"

Using someone's name matters, just not for the reason most teams think. It builds familiarity over time but doesn't change what people do. The teams getting real results have moved past names to sending based on what users do and when it matters to them. This guide breaks down five tiers of personalization, shows where the gains actually come from, and helps you figure out where to focus. No machine learning needed for the tiers that matter most.