Customer.io Pricing 2026: Plans, Overages and Trial

Customer.io Essentials starts at $100 per month, billed monthly, for 5,000 profiles and one million emails per month. Premium starts at a $1,000 monthly equivalent with an annual commitment, while Enterprise is quote-based. A documented 14-day trial exists, but there is no general free-forever plan. We checked current official information on November 6, 2026 UTC.

How Customer.io pricing actually works

Customer.io sells customer engagement software for businesses that send messages in response to user behavior. A SaaS business might send onboarding email after a signup event, push a reminder after an abandoned task, or trigger a renewal notice when an account reaches a particular state.

The platform has a visual journey builder, but the underlying data often comes from a website, application, warehouse, or developer-connected event feed. That difference matters for cost. A business may pay for messaging capacity while also funding the engineering and data work needed to make journeys accurate.

Its standard subscription model combines a platform fee, billable profiles, and email volume. Other channels can add costs. Customer.io's profiles include people and custom objects; an object might represent an account, subscription, organization, or item rather than an individual recipient.

Those objects count toward the same profile capacity as people. A startup with 4,800 customers and 400 billable objects may therefore exceed an entry allowance of 5,000 profiles. The buyer cannot assume the plan counts email addresses alone.

The same person can also count more than once if they exist in separate workspaces. Customer.io's billing article says workspaces are counted together, including development and test workspaces. Counting rules should be part of implementation planning, not an accounting surprise later.

See the Customer.io profile on Toollers for the product overview. The official vendor pages, not a static catalog snapshot, provide the pricing basis for this article. Dollar figures here are published US references, not a personalized checkout quote.

Customer.io plans and headline pricing

Essentials: $100 monthly at the entry level

The Essentials entry tier is $100 each month with monthly billing. It includes 5,000 profiles across people and objects, one million emails per month, two custom-object types, and the visual workflow builder. The vendor also lists basic data integrations and email/community support.

Customer.io's comparison page lists unlimited user seats for all three standard paid plans. Essentials instead differentiates through profile allowances, object types, workspace counts, advanced integrations, and support. Adding more marketing editors does not automatically require a seat upgrade under this published structure.

Essentials includes two workspaces, according to current plan-feature documentation. A company separating production, staging, and multiple brands into distinct workspaces may need to reconsider its architecture or discuss Premium. It should also check duplicated profiles across workspaces before assuming the same contact count is billed once.

Essentials supports event-triggered journeys, segments, email, in-app messages, and documented application integrations. However, the starter subscription alone cannot guarantee an instant high-volume launch. New Essentials email senders have a documented warm-up period and rolling daily sending caps.

The plan is most attractive when a business already has usable first-party events and needs product-linked campaigns. It may be expensive for a basic newsletter with few triggered journeys, even though one million monthly emails is a generous-looking headline number.

Premium: from $1,000 monthly equivalent, billed yearly

Premium starts at $1,000 per month in the vendor's published price comparison, billed annually. At the displayed starting equivalent, 12 months corresponds to $12,000 before add-ons or overages. That arithmetic does not prove every negotiated Premium contract costs exactly $12,000.

Premium offers custom profile and email volume terms, ten object types, enhanced agent capabilities, premium integrations, and premium chat/email support. Customer.io advertises a 90-day onboarding support period. Exact negotiated allowances must appear in the sales agreement.

Premium can be relevant when a company models multiple relationships, such as users linked to companies, plans, and subscriptions. The jump from two to ten object types can remove a structural constraint, but more object types do not eliminate the cost of each profile created.

The vendor lists eligibility for a Business Associate Agreement on qualifying Premium and Enterprise arrangements. Buyers working with regulated health information need to review the contract and supported implementation, not simply assume the public security page covers every workflow.

Annual billing is a meaningful commitment. Ask how usage overages are invoiced during the term, whether pricing tiers reset, and what happens at renewal. Customer.io's documentation says annual plan fees can be invoiced while usage overages continue to be calculated and charged monthly.

Enterprise: a negotiated contract

Enterprise does not publish one universal subscription price. The official comparison emphasizes custom profile and email volumes, higher governance, priority throughput, audit logging, and specialist implementation or customer-success options. Some services have qualifying footnotes rather than universal inclusion.

A large product organization should request a line-item quote specifying its profile high-water mark, email volume, object model, workspace needs, support response terms, migration help, and data residency. An Enterprise label without those details is inadequate for procurement.

Do not extrapolate a rate from the Premium minimum and treat it as Enterprise pricing. Custom service agreements can change the commercial model. Customer.io's public billing guide offers general overage references, but your signed service order takes precedence over a comparison built from public figures.

Startup Program: conditional, temporary access

Customer.io currently advertises up to 12 months free for eligible early-stage companies. The published application requires less than $10 million in total funding, non-purchased contact lists, and no previous Customer.io subscription. Approval is not automatic.

The program advertises up to 30,000 included profiles and access to core messaging products during the free term. It is time-limited promotional eligibility, not a permanent Free plan available to everyone. The company also describes a graduation offer after the program ends.

A founder should apply early enough to review the approval conditions, included messaging amounts, support, and the date charging begins. An accepted startup can still incur implementation labor and may outgrow usage allowances before the free period ends.

Real overage rates and why profile counting matters

Customer.io's October 2026 billing document lists Essentials profile overages at $0.009 per additional profile. The same document lists $0.004 per additional profile for Premium/Enterprise references and email overages of $0.12 per 1,000 emails across plans.

The site pricing matrix calls Premium profile pricing custom, which means those general documentation rates should not replace a signed Premium rate. Confirm contract applicability before using them to forecast a large account. The Essentials public example is more straightforward.

Customer.io uses a high-water-mark counting approach. A profile that existed during the billing cycle can count even after deletion. Adding and removing profiles in the same month does not necessarily reduce the billable total for that month.

Its billing example describes deleting 20,000 people and re-importing those same records soon afterward. The integration can cause the individuals to count again. A data pipeline that repeatedly deletes and recreates identities therefore creates financial risk alongside its technical faults.

People and objects stored in a development workspace count toward account totals, too. For a realistic estimate, inventory production, sandbox, staging, archived tenants, and relationship objects. A marketing contact count alone can understate the billable entity count.

Customer.io counts messages reaching the email service provider toward email usage, including emails that bounce or are suppressed downstream. The sending number on a marketing dashboard can differ from successfully delivered mail. Avoid calculating overages only from opened or delivered emails.

The vendor says monthly accounts are billed for the current subscription plus the previous cycle's overages. This means a spike in one period can appear as an extra charge on the following invoice. Finance teams should keep usage-date and invoice-date labels distinct.

Worked monthly cost examples

Example one: a small product with room to grow

Imagine an Essentials account storing 3,600 people and 400 account objects, or 4,000 total profiles. Suppose it sends 100,000 emails in the billing month. Both quantities fit the 5,000-profile and one-million-email published entry allowances.

Under those assumptions, the platform fee is $100 for that month, before taxes, SMS, AI credits, optional services, or implementation labor. This is a hypothetical calculation from vendor list prices, not an invoice or a claim that Toollers opened an account.

Example two: a modest overage month

Suppose an Essentials organization records a 6,000-profile high-water mark and sends 1,050,000 billable emails in one month. The first 5,000 profiles and first million emails are included in the entry reference tier.

The extra 1,000 profiles cost 1,000 × $0.009 = $9. The extra 50,000 emails cost 50 × $0.12 = $6. Adding those to the $100 base yields a hypothetical $115 monthly total before other charges.

This example assumes Customer.io's published Essentials overage rates apply and that the buyer has not changed its included package. It does not include SMS, AI, taxes, or any customized terms. The calculation is deliberately auditable; you can change its profile and email assumptions.

Example three: annual Premium commitment

At the advertised $1,000 monthly equivalent, Premium represents a $12,000 one-year base commitment. That is $1,000 × 12, not a claim that Premium can be bought one month at a time for $1,000.

Premium profile and email volumes are negotiated. A fair total-cost estimate must therefore add the quoted allowances, monthly overage rules, custom support or implementation terms, and channel charges. There is no responsible way to calculate one universal Premium invoice from the public price alone.

Email warm-up and technical restrictions

One important limit sits outside the headline million emails. Customer.io documents that new Essentials accounts begin at a rolling limit of 500 emails per day. The limit typically rises toward 10,000 per day after roughly two weeks of healthy sending history.

The documentation says trusted senders can reach their plan's standard sending limit after about six weeks. These are vendor-described typical timelines, not guarantees. Account reputation and sending patterns can slow progression or lead to adjustments.

The rolling window looks back over the prior 24 hours rather than resetting at midnight. A launch announcement that uses most of today's capacity can affect tomorrow morning's automation and notification traffic. That matters for apps with bursts of onboarding or transactional messages.

When a normal message hits the daily compliance cap, Customer.io can mark it undeliverable without retrying later. Its guide describes a different continuation rule for unfinished one-time sends. A team must understand these differences before routing critical authentication messages through a new account.

Customer.io also documents a 14-day trial for new users, with up to 5,000 messages across channels during the trial and a lower daily cap. That directly conflicts with this Toollers export's `hasFreeTrial=false` field. The Tool record should be corrected after an editor verifies the public trial terms.

SMS, AI credits, and other costs

SMS spending should be modeled by billable segment, not simply by the number of message bubbles an employee drafts. In Customer.io's billing guide, a long SMS can require multiple segments; inbound replies, media, and sender configurations can also affect the bill.

Where Customer.io bills SMS directly, its published overage rate is $0.012 per segment beyond the plan allowance. The vendor describes additional sender numbers, A2P brand or campaign registration, and certain agency setups as possible extra charges. Rates and registration scope can vary by route.

The public pricing comparison also lists extra AI credits at $10 per 100,000 for Essentials and Premium, while Enterprise pricing can be negotiated. AI Agent remains a changing feature area; document the actual tasks and credit consumption before treating a credit pack as a fixed monthly requirement.

Customer.io says in-app messages, push notifications, and webhooks do not draw additional per-message charges in its base billing description. However, they remain subject to a usage policy and other sender or transport costs can exist. Unlimited in a feature table is not a license to ignore fair-use controls.

For non-US SMS traffic, ask which transport provider and local registration obligations apply. Messages can be priced by destination, sender type, or carrier charges. A product with users across several countries needs a country-by-country forecast, not a single US segment example.

Billing, taxes, support, and cancellation

The vendor says applicable local or state sales taxes can be added to invoices. Premium and Enterprise customers may have annual invoices for the base commitment, while overages are assessed monthly. Finance should reconcile the order form with the account's Plans & Billing screen.

Essentials support is advertised as email and community access. Premium adds chat/email support and onboarding. Enterprise lists priority technical support and optional specialist attention. None of those labels proves a particular response time unless it is specified in the purchased service level.

Customer.io's cancellation guide says Essentials and Startup accounts can initiate cancellation in Plans & Billing. Premium and Enterprise customers must contact their customer success manager. The contract still governs remaining subscription-term fees, so the button location is not a refund promise.

The vendor says cancellation stops messaging and immediately removes access. Account data is then scheduled for deletion after 60 days. Teams should export profiles, consent records, templates, campaign definitions, and reporting before closing the account, with a controlled replacement ready.

No general refund entitlement was verified in the public pricing comparison. Customer.io's legal terms discuss fees owed for the remaining subscription term. Buyers with annual agreements should have legal and procurement review the actual service order before approving a migration or cancellation.

Which Customer.io plan is worth considering?

Essentials makes the most sense for a product team that can reliably send behavioral events and wants several automated customer journeys. At $100 monthly, the platform can be good value when it replaces a collection of manual notifications and incomplete lifecycle messages.

Premium makes sense when the business needs more custom object types, eligible integrations, additional onboarding and support, or negotiated profile and send volumes. The price jump is large, so identify which purchased capability will be used in the next quarter.

Enterprise is a procurement conversation for high-volume or security-sensitive organizations. Ask for clear data residency, backup and export responsibilities, audit access, throughput, regulatory commitments, incident support, and a realistic peak-message scenario before signing.

For a newsletter-first business, compare Brevo or ActiveCampaign. For ecommerce-specific purchase events, inspect Klaviyo and Omnisend. Their pricing units differ, so no one entry number settles the choice.

Research method and verification limits

We examined official Customer.io pricing, profile and email billing, feature access, SMS fees, startup eligibility, warm-up rules, trial policy, cancellation guidance, and legal terms on November 6, 2026 UTC. The amounts cited are public USD figures with the stated billing cadence.

We did not purchase a subscription, enter a payment card, run a live workflow, measure deliverability, or obtain a personalized Premium proposal. The worked examples are calculations. They are not evidence of a hands-on product test or a vendor-issued invoice.

The Toollers export labels Customer.io as tested, yet its FAQ says no production workflows or event delivery were tested. It supplies no dated tester, plan, screenshots, or measurements. That contradiction requires editorial review before publishing any assertion of direct testing.

Before buying, request a written summary of profile high-water rules, object counts, email warm-up, support, annual terms, trial limitations, SMS rates by destination, and likely AI usage. Revisit that summary after implementation changes the data model.

Frequently asked questions

Continue reading about Customer.io

• Customer.io Review 2026: Journeys, Features and Costs
• Customer.io Alternatives: Six Options by Use Case