This article originally described conversation-based billing. That description was outdated and has been corrected; the original URL and publication date are retained.
Current billing basis
Meta’s WhatsApp Business Platform pricing page describes charges per delivered message, with category and recipient market affecting the rate. Do not estimate a bill by counting conversations alone.
The pricing page distinguishes marketing, utility, authentication and service messages. Service messages are free within the customer-service window, and utility messages sent in response to a user within that window can also be free. Special entry-point rules and volume tiers may apply. Check the live rate card and your account’s applicable terms before committing a budget.
Model the complete cost
Build a worksheet with delivered billable messages by category and recipient market, the applicable rate, provider charges, software subscriptions, implementation and model usage. Keep taxes and currency assumptions explicit.
Do not use a generic worldwide rate or assume an unlimited-message window covers all categories. Separate free-window traffic from billable templates and reconcile your estimate against actual delivery records.
Provider and integration decisions
Compare a direct integration with any provider-managed option that fits your support and technical needs. A provider may charge subscription or usage fees in addition to Meta charges; ask for those layers separately. Do not assume a BSP is mandatory for every integration.
Before signing, clarify account ownership, templates, consent processes, data export, support responsibility and migration arrangements. Document how failures are handled and who can pause a campaign.
AI automation does not remove message charges
An assistant can help handle recurring questions, but its value should be measured through resolution quality, safe handoff and total operating cost. It also adds model usage and maintenance considerations. Do not claim that every automated response is cheaper or clinically appropriate.
At Iyara Labs, the base Engage package covers a website chatbot—not WhatsApp deployment. WhatsApp, voice and additional channels require separately agreed scope. Read the conversational AI service and contact us to scope a specific workflow.
Pre-launch checklist
- Confirm current rates and recipient-market assumptions.
- Separate delivered message charges from provider and software fees.
- Agree template, consent and account responsibilities.
- Test against isolated recipients and backends before any approved launch.
- Reconcile usage and costs after launch rather than relying on a static article.
This is budgeting guidance, not a quote or a substitute for Meta’s current terms.