- ManyChat
- India pricing
- Instagram automation
- Active Contacts
- USD to INR
- SaaS costs
ManyChat Pricing in India: How to Calculate a Comparable Monthly Cost
On this page
ManyChat pricing India cannot be calculated reliably by copying a US-dollar sticker price into rupees. Plan availability may differ by region and account age; the bill depends on the month's Active Contacts, annual plans are charged upfront, extra contacts can create overages, and the final rupee amount can change through foreign-exchange conversion, tax, card-network treatment and issuer or cross-border fees. SlideReply publishes this guide and is one of the products used in the comparison examples.
The direct answer is to begin with the plan and billing cycle actually offered inside your ManyChat account, estimate unique people rather than messages, add any overage, and only then convert the dollar total into rupees. The INR figures below are dated reference estimates, not official ManyChat INR prices and not promises of what a card statement will show.
This guide owns that calculation only. It does not decide which product's functions fit your workflow, rank alternatives or name a winner. For that separate decision, use the ManyChat versus SlideReply India fit guide.
ManyChat pricing India: build the bill from the meter, not the headline
A region and account-age check comes before any table. ManyChat says its new five-plan model was introduced on 2 March 2026, can vary by region, and initially applies to accounts created on or after that date. An older account may remain on the prior model. That means a public article can provide a calculation framework, but the plan names, allowances and checkout shown inside your own account are the purchase-time authority.
The following snapshot covers the verified Free, Essential and Pro facts requested for this calculation. It was last checked on 25 July 2026. Dollar amounts are ManyChat's published figures; rupee conversions appear later and are explicitly dated estimates.
| Plan | Monthly billing | Annual billing | Included Active Contacts per month | Overage | Calculation note |
|---|---|---|---|---|---|
| Free | $0 | Not applicable | 25 | No paid-overage rate stated in the cited Free-plan facts | 1 user, 1 Inbox seat, up to 2 eligible channels, 4 live automations and first-message branding |
| Essential | $17/month | $168 charged upfront, presented as $14/month equivalent | 250 | $0.10 per extra Active Contact on monthly billing; $0.08 on annual billing | Keep the annual cash charge separate from its monthly equivalent |
| Pro | $39/month | $348 charged upfront, presented as $29/month equivalent | 2,500 | $0.05 per extra Active Contact on monthly billing; $0.038 on annual billing | Includes a 14-day trial; that trial is not a permanent free plan |
The word “equivalent” matters. Essential's $14 and Pro's $29 annual figures are monthly budgeting views of twelve-month commitments. The stated base cash charges are $168 and $348 upfront, respectively. Monthly equivalent is a budgeting label, not the cash collected today. Overage, excluded tax and payment-side effects must not be silently treated as part of those equivalents.
ManyChat's public pricing page also says tax is excluded, pricing is determined by billing country, and the final price is shown at purchase. Therefore, record the checkout currency and final charge rather than assuming every India-based reader will see exactly the same presentation.
Active Contacts are people in a month, not message volume
ManyChat defines an Active Contact as a person interacting through ManyChat in the current billing month. Repeat interactions by that same person during the month count once. Cross-platform identity can vary, so activity by what appears to be the same human on different channels should not automatically be assumed to collapse into one record.
This meter creates several practical counting illustrations:
- If one person interacts eight times during July, those repeat interactions count as one July Active Contact, not eight, provided they are recognized as the same person.
- If 300 different people each interact once during July, the starting estimate is 300 Active Contacts even if none buys anything.
- A commenter who asks for a link and leaves can still be an Active Contact. The counter measures interaction, not customer status, qualified-lead status or revenue.
- If the same human interacts on two platforms and the identities are not joined, the resulting count can differ from a simple one-person assumption. Use ManyChat's account reporting rather than manually deduplicating names.
- A conversation can contain several incoming and outgoing messages while contributing one recognized person to that month's Active Contact total. Message or DM volume can therefore be much higher than the contact count.
A contact counter is not a customer counter. It is also not a lifetime database total: the cited definition is tied to interaction in the current billing month. For a forecast, use unique monthly interacting people as the input, then keep messages in a separate column for operations and for comparisons with products that bill or limit by DMs.
Estimate a normal month and a spike month. A creator who usually sees 180 unique interacting people but reaches 420 during a launch has a different overage exposure from someone with a steady 180, even when their annual totals match.
Reproduce the dated USD-to-INR reference
The reference used here is INR96.5390 per USD at 1:00 pm on 24 July 2026, published through the Reserve Bank of India/FBIL reference-rate material. It is a dated arithmetic input, not a card settlement rate and not an official INR price from ManyChat.
Use this formula:
Reference INR estimate = USD amount × 96.5390
Keep all decimals while calculating and round only the reader-facing approximation. Applying that rule gives:
| Item | Reproducible arithmetic | Dated reference estimate |
|---|---|---|
| Essential monthly base | $17 × ₹96.5390 = ₹1,641.163 | Approximately ₹1,641 before tax and card/FX effects |
| Essential annual monthly equivalent | $14 × ₹96.5390 = ₹1,351.546 | Approximately ₹1,352 per month equivalent |
| Essential annual cash due upfront | $168 × ₹96.5390 = ₹16,218.552 | Approximately ₹16,219 upfront |
| Pro monthly base | $39 × ₹96.5390 = ₹3,765.021 | Approximately ₹3,765 before tax and card/FX effects |
| Pro annual monthly equivalent | $29 × ₹96.5390 = ₹2,799.631 | Approximately ₹2,800 per month equivalent |
| Pro annual cash due upfront | $348 × ₹96.5390 = ₹33,595.572 | Approximately ₹33,596 upfront |
Every rupee number in this table is a dated reference estimate as of 24 July 2026, never an official ManyChat INR price. The annual-equivalent rows help compare recurring budget levels. The annual-upfront rows show the base cash commitment used in the conversion. For cash planning, do not replace ₹16,218.552 with twelve monthly charges of ₹1,351.546; the cited annual plan is billed $168 upfront. The same distinction applies to Pro's $348 upfront amount.
If reviewing the calculation later, replace 96.5390 with a newly dated reference input and recompute every row. Do not update only the rounded result because that makes the worksheet impossible to audit.
Add the layers between a reference estimate and a card statement
A comparable India cost has several layers. Keep them visible instead of compressing them into one unexplained rupee figure:
- Vendor, region and account layer. Confirm which plan model your account receives, its billing country, the quoted currency, included Active Contacts and overage rates. Older and newer accounts may not share the same model.
- Base and overage layer. Calculate the dollar plan base plus overage from actual or forecast Active Contacts. For annual billing, distinguish the upfront base from any later overage entries shown on invoices.
- Reference FX layer. A dated RBI/FBIL rate is useful for a repeatable comparison at one point in time. It is not the rate guaranteed for a commercial card transaction.
- Card conversion layer. The card network or payment path may use a different settlement-time conversion. Timing and the currency actually presented at checkout can change the result.
- Tax layer. ManyChat states that tax is excluded from public pricing. Use the tax shown at checkout or on the invoice; this guide does not invent a tax percentage.
- Issuer and cross-border layer. A card issuer may apply its own foreign-currency or cross-border treatment. Check the issuer's terms and statement rather than assuming a rate or fee.
A clean worksheet therefore has separate cells for vendor USD subtotal, dated reference conversion, checkout tax, issuer/card effects and final statement amount. Unknown values should remain marked “check at purchase,” not replaced with zero.
Fill in the requirements worksheet before calculating
Use one row per account and one column per month. This prevents a blended estimate from hiding a high-volume account or a seasonal spike.
| Input | What to record | Why it changes the calculation |
|---|---|---|
| Account count | Number of Instagram or other channel accounts/logins being budgeted | A displayed plan price should not be assumed to cover an unverified account structure |
| Unique people | Normal and spike-month people who interact through ManyChat | This is the closest planning input for Active Contacts |
| DMs/messages | Incoming and outgoing monthly message estimate | Useful operationally, but not interchangeable with Active Contacts |
| Channel and team breadth | Channels needed, users and Inbox seats | Record what must be checked against the plan actually offered; do not infer it from price alone |
| Required functions | The specific automation, inbox and workflow functions that must be present | Keeps price arithmetic separate from the fit review |
| Spike and overage | Peak unique people, included allowance, extra contacts and rate | Shows exposure that a base sticker price omits |
| Billing cycle | Monthly or annual; renewal date; annual upfront amount | Separates monthly flexibility from upfront cash due |
For each account, collect the last three to six months of unique interacting-person counts if available. Mark campaigns, launches or seasonal periods rather than averaging them away. Then calculate both a normal case and a spike case. This is not a recommendation to choose one plan; it is a way to see which inputs drive the invoice under each plan shown in your account.
Keep required functions in the worksheet but outside the arithmetic result. Once the numbers are prepared, assess those functions in the separate India product-fit comparison. That boundary prevents a lower numerical estimate from being mistaken for a complete product decision.
Keep the SlideReply INR reference on a non-equivalent meter
For a local-currency reference, SlideReply's public pricing page currently presents the following. This row is included only to make a comparable-cost worksheet possible; it is not a value verdict.
| Product reference | Public INR and allowance snapshot | Meter and scope warning |
|---|---|---|
| SlideReply | Free: 2,500 DMs/month; Pro: ₹249/month with 50,000 DMs/month; Ultimate: ₹499/month with the current ceiling/fair-use qualification | Metered in DMs, not Active Contacts; one Instagram account per login |
DMs and Active Contacts are not equivalent units. Do not place “2,500 DMs” beside “2,500 Active Contacts” and treat them as equal capacity. One person can exchange multiple messages, while ManyChat's cited monthly rule counts repeat interactions by the same recognized person once. Conversely, account structure, channels, team access and required functions must be recorded separately rather than inferred from either volume number.
The defensible comparison is two parallel worksheets: calculate ManyChat from unique monthly Active Contacts and its dollar rules, calculate SlideReply from the currently published INR price and DM allowance, then carry account count and requirements alongside both. The separate fit article can evaluate those non-price fields without turning this guide into a ranking.
Reader formulas and a hypothetical overage calculation
Let:
A= forecast Active Contacts for the monthI= Active Contacts included in the selected planR= overage USD per extra Active Contact for that billing cycleB= base USD amount relevant to the invoiceF= dated INR-per-USD reference input
Then:
Extra Active Contacts = max(0, A − I)
Overage USD = Extra Active Contacts × R
Reference pre-tax INR estimate = (B + Overage USD) × F
For a monthly plan, B is the monthly base. For annual cash planning, show the stated annual upfront base in the purchase month rather than substituting the monthly equivalent. Add tax and card/issuer effects only when known; until then, label the result pre-tax and before card/FX effects.
Hypothetical overage example — not a quoted invoice: suppose an Essential account on monthly billing records 320 Active Contacts in one month. The cited included allowance is 250, so the hypothetical extra count is max(0, 320 − 250) = 70. At the cited monthly overage rate, 70 × $0.10 = $7. Add the $17 monthly base to get a $24 pre-tax vendor subtotal. At the dated reference input, $24 × ₹96.5390 = ₹2,316.936, approximately ₹2,317 before tax and card/FX effects.
This example assumes all 320 records meet ManyChat's Active Contact definition and that the cited Essential model is the one offered to the account. It does not assume the reference rate will equal the card rate.
Refresh these checks immediately before purchase
- Sign in and confirm the plan model offered to this specific account, especially whether it predates 2 March 2026.
- Confirm billing country, checkout currency, included Active Contacts and current overage rate.
- Toggle monthly and annual views; write down both the monthly equivalent and the actual upfront cash charge.
- Re-estimate unique interacting people for a normal month and a spike month; do not substitute DM count.
- Recalculate with a newly dated USD-to-INR reference and retain the date, time and source.
- Check the checkout for final price and tax, then check the card issuer's current foreign-currency and cross-border terms without assuming a percentage.
- Revisit the vendor source pages for changed allowances, plan availability or billing rules.
- If using the SlideReply reference, recheck
/pricingand preserve the warning that DMs and Active Contacts are different meters.
Stop before payment if a worksheet cell that affects cash due still says “assumed.” Replace it with the account's checkout value or leave it clearly unresolved.
Sources and review date
Last reviewed: 25 July 2026. The currency reference is INR96.5390 per USD at 1:00 pm on 24 July 2026.
- ManyChat subscription: how to choose the right plan — model introduction, regional availability and account-age caveat.
- ManyChat Free plan — Free allowance and limits.
- ManyChat Essential plan — monthly, annual, allowance and overage figures.
- ManyChat Pro plan — monthly, annual, allowance, overage and trial figures.
- ManyChat Active Contacts — monthly person-based counting, repeat interaction and cross-platform caveats.
- ManyChat public pricing — tax exclusion, billing-country basis and purchase-time final price.
- Reserve Bank of India — RBI/FBIL dated USD-to-INR reference material.
- SlideReply pricing — INR plan and DM-allowance reference.