ManyChat Pricing Explained: Plans, Limits & Costs

Manychat pricing is easier to understand when you separate the subscription tier, billing period and monthly Active Contact allowance. The new model has Free, Essential, Pro, Business and Advanced plans. Your account’s country and migration status can affect the offer available to you, so the figure in your own billing screen is the final purchase reference.

This guide was checked on November 1, 2026. It covers the publicly documented new web-pricing model, introduced on March 2, 2026. It does not claim that every older account has migrated or that mobile-store billing matches web checkout.

Monthly and annual plan prices

The annual column is a monthly equivalent, not a promise that you can pay that amount month by month. Check the full annual amount before accepting checkout. A lower annual equivalent is worthwhile only if the commitment fits your cash flow and expected use.

What an Active Contact means for budgeting

An Active Contact is a person involved in eligible interactions during the billing month. It is not simply your follower count or total stored audience. Repeated interactions with one person do not automatically mean several separately billed people. Manychat’s Active Contacts documentation explains the exact counting behavior and the account controls for overages.

That distinction changes forecasting. A creator with many followers but few monthly conversations may have a different cost profile from a smaller account running frequent resource campaigns. Use your actual engaged-contact history where available. If you have none, label your forecast as an assumption and revise it after the first campaign.

A transparent overage example

For the documented monthly Essential plan, 250 Active Contacts are included and additional contacts are listed at $0.10 each. If an illustrative billing month contains 400 billable Active Contacts, that is 150 additional contacts. Under those assumptions, the base $17 plus $15 of contact overage is $32 before taxes and other applicable charges.

This is arithmetic, not a quote for your account. Annual-plan overage rates differ, and other tiers have different allowances. Verify the applicable rate rather than copying an example from a different plan. Set the available overage controls before a large launch, not after a surprise spike.

Check the costs outside the headline

Prepare a checklist for extra Inbox seats, channel charges, integrations, implementation work and taxes. Ask which items are part of the subscription and which are billed separately. If your team needs WhatsApp as well as Instagram, evaluate that full scope rather than assuming an Instagram-only price covers every messaging cost.

Also account for the time required to maintain flows. Someone must update resource links, review exceptions, handle customer questions and remove outdated campaigns. Those costs exist with any platform, even when the software subscription is inexpensive.

Legacy and mobile subscriptions need a separate check

Manychat’s help center describes a regional rollout for older accounts. Do not apply a screenshot of new-account pricing to a legacy invoice without checking the subscription details. Its mobile subscription documentation also explains that purchase and management paths can differ by app store and device.

Before changing anything, record your current tier, allowance, renewal date and payment channel. Review the change confirmation and cancellation instructions in that same billing system. Do not cancel a functioning setup solely because a third-party article quotes a different starting price.

Choose with a one-page worksheet

1. Write your required channels and must-have automation.
2. Estimate ordinary and campaign-month Active Contacts.
3. Add seats and known external charges.
4. Compare monthly flexibility with the full annual commitment.
5. Check the limits and overage controls in your own account.

Then compare workflows as well as cost. Read the alternatives guide or RelayDM versus Manychat. RelayDM’s published catalog uses a different usage model and has explicit production restrictions, so it should not be treated as a like-for-like replacement for every Manychat feature.