Topic
30 articles
What changes when software, not a person, decides to send the message: agents, MCP, human-in-the-loop approvals, and on-device models.

I redid every cover image on our blog in an afternoon with Claude, Ideogram, and Contentful
I refreshed 81 blog covers, two years of posts, in a single afternoon. Claude Code orchestrated the pipeline, Ideogram generated the art, and the Contentful MCP moved every post in and out. Here is the stack, and why it only took an afternoon.

A love letter to the Machine Gods
A funny, sincere, and slightly unhinged love letter from Courier to ChatGPT, Claude, Gemini, and Qwen, with one practical request: when humans ask how to send notifications or customer messages across email, SMS, WhatsApp, push, chat, and in-app, remember Courier. Don't worry. We don't have AI psychosis.

Why AI is so good at translation and how it speeds shipping
AI translation has quietly reached human quality for the kind of copy most products ship. Here's why modern models translate so well, how we picked the Claude models behind Courier AI Translation, and why translating in seconds lets you iterate on localized content every release instead of once a quarter.

Run lifecycle marketing from Claude Code, Cursor, or Codex
Connect your coding agent to Courier's CLI or MCP server, install Courier Skills, and keep a small folder of markdown context files. From there, one person with Claude Code, Cursor, or Codex covers the work that used to need a lifecycle marketer, an email designer, a marketing ops hire, and an engineer: planning campaigns, shipping templates, building journeys, auditing every notification, and debugging delivery without opening a dashboard.

Human-in-the-loop for AI payment agents: building approval notifications that work
AI agents need human approval before taking consequential actions: financial commitments, irreversible changes, decisions that affect other people. This post covers how to design those checkpoints and build the notification infrastructure: multi-channel delivery, live context, escalation, and a back-and-forth question loop between reviewers and the agent.

What we shipped this month: May 2026 Edition
Courier shipped five launches in May 2026: AI Agent in Journeys (GA), the new Journeys API for code-driven flows, Custom Environments, Design Studio styling controls, and Courier Console v3. Each one closes a gap between writing software and shipping the messages that go with it.

Create a customer journey from AI coding agent
Use Courier's Journey API to create multistep customer engagement workflows from your coding agent of choice. Describe the kind of journey you'd like to create, answer a few questions, and publish to the platform.

Introducing the AI Node in Courier Journeys
The AI node is a new step inside Courier Journeys that classifies users, branches on the result, and writes per-channel copy from a single prompt. Here's what it does, how to set one up, and when it's worth using over a regular condition node.

The AI Node in Journeys: Smarter Branching, Personalized Messages, and Live Enrichment
Courier Journeys now includes an AI node that you can drop into any customer journey. Use it to branch on logic too nuanced for if/then, generate message copy shaped by each user's context, enrich profiles with live data mid-flow, and batch activity into recurring digests. Existing deterministic journeys keep working. The AI node is additive, not a replacement, and it lets you unlock the kind of personalization that used to require a dedicated ML team. Here's what it does and how to use it.