Lumail vs Customer.io
Lumail
Customer.io
Customer engagement and lifecycle messaging platform
Lumail and Customer.io pricing and feature comparison
Free allowance
Lumail
$0
Customer.io
No free plan
$0 · 3,000 emails · Unlimited subscribers
No free plan
Paid entry
$20/month, 40,000 included, then $0.60/1,000
$100/month
Pricing basis
Unlimited subscribers; pricing follows email volume
Profiles (people + objects) plus email volume on Essentials/Premium; Builder is prepaid usage at $0.40 per 1,000 messages
Automation
Graph workflows with triggers, branches, goals, exits, and A/B paths
Visual workflow builder with segment, event, date, webhook, relationship, and form triggers; branching, delays, A/B tests, conversion…
AI and developer access
ChatGPT OAuth, MCP, skills, CLI, SDK, REST API, and visual editor
In-app AI Agent on paid plans (included, no AI-credit cost). Hosted MCP for Claude, ChatGPT, and Cursor. CLI (@customerio/cli) for coding…
Transactional email
Included through API, SMTP, SDK, CLI, and agent tools
Transactional email and push via the App API (and CLI); included on Essentials+ and counted toward monthly email volume unless you use…
Publishing surface
Capture pages and custom web domains; not a general website builder
Broadcasts and one-time sends for newsletters and API-triggered blasts. Not a hosted publication, blog, or paid-newsletter platform.
Choose Lumail if…
- You store a large list and want unlimited subscribers with pricing by emails sent, not profiles
- You want 89 named organization-scoped MCP tools, a ChatGPT OAuth plugin, CLI, TypeScript SDK, and REST API as first-class operators
- You need transactional SMTP (smtp.lumail.io:587 STARTTLS) in the same org as campaigns, without SMS/CRM/CDP
Choose Customer.io if…
- Your program is product lifecycle messaging across email, SMS, push, in-app, and WhatsApp
- You need objects, reverse ETL, warehouse sync, ad-audience sync, or HIPAA/BAA (Premium+)
- You want a visual journey builder with event triggers, branching, and send-time LLM Actions
Where Customer.io is strong
A real alternative, not a straw man.
Event-driven, cross-channel journeys (email, SMS, push, in-app, WhatsApp) billed on profiles plus email volume, with a usage-based Builder SKU for transactional sends. People pick Customer.io when they need product-led SaaS and lifecycle teams that want event-driven, cross-channel journeys on first-party customer data..
- Cross-channel journeys: email, SMS, push, in-app, WhatsApp, LINE, and webhooks in one visual builder
- Data model billed as people + objects, with reverse ETL, warehouse destinations (Premium+), and a CDP (Data Pipelines)
- Agent surface: in-app AI Agent, hosted MCP wrapping Journeys and CDP APIs, and an LLM-first CLI
Don't trust the table. Run one journey.
Checklists lie by flattening the work. Build one real path: a trigger, a wait, a branch, a goal, an exit. Then open one subscriber and see what actually happened. That tells you more than any feature row.
- 1. Import a small, consented sample. Not the whole list.
- 2. Recreate one campaign and the audience it actually hits.
- 3. Publish one automation with a goal you can measure.
- 4. Fire a test and read every event on one person.
- 5. Compare the weekly work, not the setup afternoon.
Try it on a real send
Keep the whole list. Pay when you send.
3,000 emails free, no card. Rebuild one campaign, one workflow, and one transactional message before you move anyone. If it feels worse than Customer.io, stay.
The questions people actually ask
Is Lumail cheaper than Customer.io?
Sometimes. Lumail is $0 for 3,000 emails, then $20 for 40,000. Customer.io's number only makes sense after you know what they cap: contacts, seats, a daily send limit, or a feature they hide behind a paid plan. Read the honest take above, then price a normal month and a launch month on both pages.
What is the main difference between Lumail and Customer.io?
Choose Customer.io when you need behavioral journeys across email, SMS, push, in-app, and WhatsApp plus a CDP. Choose Lumail when you want unlimited stored subscribers, email-volume pricing, graph workflows, transactional SMTP in the same org, and 89 named MCP tools.
Can I migrate from Customer.io to Lumail?
Yes. Don't move the whole list on day one. Export a small consented sample, rebuild one campaign and one automation, authenticate your domain, then watch one subscriber go through the run. If that feels right, move the rest.