Customer.io vs Intercom

Two products with different centres of gravity

Customer.io describes itself in its docs as a platform for sending email, push, SMS, in-app messages and webhooks based on customer behaviour and data attributes. Everything on the Essentials plan is arranged around that: workflows, segments, events, objects and the Liquid templating language. The pricing page sells it by profile bands, and the unit you manage is a person or an account in your workspace.

Intercom's pricing page sells a customer service platform: three plans (Essential, Advanced, Expert), each priced per seat, with Fin AI Agent and usage charges on top. Its own FAQ describes the pricing as seats plus usage, and says live chat, support email, in-app chats, banners and tooltips are included in every plan, while email campaigns, SMS, WhatsApp and phone are pay-as-you-go. Outbound email is therefore a channel Intercom lets you rent, not the product it sells.

That framing explains most differences below. Customer.io wants you to describe your customer through data and then compose messages; Intercom wants you to talk to the customer, then automate the repeatable parts. A B2B SaaS can use either to send an onboarding sequence, but the choice shows up in who is authorised to change it.

How events and attributes get in

Customer.io's custom events guide says a track call carries an event name and a free-form property dictionary, including nested objects and arrays, and that order does not matter: you can send an event before or after the person is identified. The workflows page lists event, attribute or segment, form, date, object and webhook triggers.

Intercom's event endpoint is a POST to api.intercom.io/events with an event name, a Unix timestamp and an identifier for the contact. Metadata is limited to 10 tracked keys per event, the first ten in the order you send them, and the keys cannot be changed after the event exists; the docs say new metadata on an existing event may take up to 24 hours to show. Attributes used in an outbound audience must already be tracked, which happens once at least one contact has a value for them, per the email FAQ.

For B2B SaaS the practical difference is volume and shape. A product that sends many properties per event, or fires events at high frequency, fits Customer.io's looser model. A product that sends a handful of well-named milestones (invited teammate, connected data source, exported report) fits Intercom's limits comfortably.

Where Series and the add-on fit

Intercom's multi-step builder is called Series. The Proactive Support Plus article says Series is not sold separately and is only available with that add-on, at $99 a month including 500 'Messages Sent'. It also says the add-on is not required to use email, SMS, WhatsApp or phone, which are sold on usage alone. In practice, one-off and triggered Outbound emails work without it, and a branching onboarding journey needs it.

The Series FAQ sets the operating limits: 250 blocks per series, up to 10 entry rule blocks, 500 live series, entry rules checked once an hour (or when the person pings through the Messenger), and a single entry per person unless you enable re-entry for scheduled or event-triggered rules. Those limits are generous for lifecycle journeys but remember the hourly check: a trial-ending email is not minute-accurate.

Customer.io's workflow builder is included in Essentials, so a multi-step journey does not move you up a plan. Its triggers page documents re-entry frequency settings and exit conditions, and geofence triggers are reserved for Premium and Enterprise.

Support-side context and the Customer.io to Intercom bridge

A support-heavy B2B SaaS often wants the person writing the onboarding email to know what the same customer told support last week. Intercom is better at that because the conversation, the contact record and the outbound message live in one workspace, and its Fin AI Agent can answer from your help content at $0.99 per outcome.

Customer.io does not try to replace that inbox, and on the pages we read it lists no helpdesk. What it does provide is an Intercom destination with three default actions: Identify Contact (create or update a contact), Identify Company (create or update a company and attach the contact) and Track Event. That lets Customer.io hold the lifecycle logic while Intercom still shows the support team who the person is and what they did. Customer.io also warns that there are two versions of the integration and recommends the standard one rather than the Web one.

Mirroring has a cost: every event you push is data Intercom stores, and every email Intercom sends is a billed send. Keep the bridge to identity and the few events support actually reads.

Cost at three team and list sizes

All prices are list USD read on 2026-10-07. Customer.io: Essentials $100 at 5,000 profiles, $145 at 10,000, $235 at 20,000, $325 at 30,000, billed monthly. Intercom: Essential $29 per seat with annual billing and $39 monthly, email charged per send on the tiered table from its usage-based channels article, which states $39 for 3,000 emails and $25.50 for 1,200.

Small program: 5,000 contacts, 20,000 emails a month, 2 support seats. Customer.io costs $100. Intercom costs 2 x $29 = $58 for seats, plus $109 for 20,000 emails ($79 for the first 10,000 and 10,000 x $0.003 = $30 for the next), a total of $167. Add the $99 Proactive Support Plus add-on for Series and it is $266.

Mid program: 10,000 contacts, 50,000 emails, 3 seats. Customer.io costs $145. Intercom costs 3 x $29 = $87, plus $199 for emails, a total of $286, or $385 with the add-on.

Larger program: 25,000 contacts, 150,000 emails, 6 seats. Customer.io's selector shows $235 at 20,000 profiles and $325 at 30,000, so a 25,000 list bills between those. Intercom costs 6 x $29 = $174, plus $424 for emails ($324 for the first 100,000 plus 50,000 x $0.002 = $100), a total of $598, or $697 with the add-on.

The comparison is not like for like: Intercom's figure includes a Messenger, an inbox and a help center that Customer.io does not sell. If you would have bought Intercom for support anyway, the marginal cost of its email is the emails line, not the total. If the seats exist only to send email, Customer.io is cheaper for a list of up to 5,000 people from about 8,400 emails a month, where one seat plus the email tiers ($29 + $71) reaches Customer.io's $100 floor.

At very low volume the order flips. A list of 1,000 people mailed three times is 3,000 emails, which Intercom prices at $39; with one Essential seat the total is $68, below the $100 Customer.io entry plan.

• Fin AI Agent is billed per outcome at $0.99 and is not part of any figure above.
• Monthly seat billing raises Essential to $39 per seat; the Intercom pricing FAQ gives a three-seat example of $39 x 3 = $117.
• Intercom's Early Stage program is advertised at 93% off for companies under $10M raised with 15 employees or fewer, and the add-on is bundled in it.
• If you raised under $10M, Customer.io's Startup Program makes the first 12 months free, which at 5,000 profiles saves $1,200 in year one.

What each entry plan leaves out

• Customer.io Essentials: managed deliverability is not included, HubSpot and Salesforce integrations and warehouse export need Premium, and only two object types and two workspaces are available.
• Customer.io new accounts start under a daily sending limit of 500 emails that rises as sending history builds, so a large first broadcast must be staged.
• Intercom Essential: no multiple team inboxes, no round robin assignment and no Workflows builder; those start on Advanced at $85 per seat per month with annual billing.
• Intercom core plans: Series, product tours, surveys, posts, mobile push and carousels all need the $99 add-on, and Intercom outbound email cannot copy a participant by CC or BCC.
• Intercom emails built in HTML mode do not report link clicks, because links cannot be extracted from raw HTML.

Moving lifecycle email from Customer.io to Intercom

1. Confirm that you want to pay per send. List your 12-month email volume and run it through the tier table in the usage-based channels article before you commit.
2. Export people and companies from Customer.io, with attributes, and decide which become Intercom custom data attributes. An attribute only becomes usable in outbound audience rules once at least one contact holds a value for it.
3. Import opted-out people so they are not mailed again. The Intercom email FAQ describes a CSV with an Email column and an 'unsubscribed_from_emails' column set to true, mapped to a new boolean attribute of the same name.
4. Re-create your events with the events endpoint, keeping each to 10 metadata keys. Name events in past-tense verb-noun form, as Intercom's docs suggest.
5. Rebuild one-off sends as Outbound emails and journeys as Series, after adding Proactive Support Plus. Rebuild audience rules, since Series entry is checked hourly.
6. Authenticate the sending domain under Settings, Channels, Email, Domains & Addresses by adding the DMARC, DKIM and SPF records shown there.
7. Keep password resets and receipts out of this move. The Intercom pages we read cover Outbound and Inbox email, not a transactional email API.

Moving lifecycle email from Intercom to Customer.io

1. Export your contacts and companies from Intercom's Contacts list, and write down which Series, Outbound emails and event names are live. Decide what stays in Intercom: most teams keep the Messenger and inbox.
2. Create the profile attributes in Customer.io and object types for companies, then relate people to their company object so account-level triggers work.
3. Send events through the data-in API and rebuild each Series as a workflow. Intercom entry rules map to Customer.io's attribute or segment triggers, and its audience rules map to segments.
4. Warm up your sending. Customer.io Essentials starts new accounts at 500 emails a day and raises the cap as healthy sending history builds, so ramp rather than move your whole list at once.
5. Turn on the Intercom destination if the support team still needs identity and events. Map Identify Contact, Identify Company and Track Event to the data you want mirrored, and leave out events support never reads.
6. Cut over by pausing the Intercom Outbound emails and Series after the Customer.io workflows go live, and check that unsubscribed contacts were carried across.