Conversation-based pricing (DEPRECATED) | Developer Documentation

Check an old WhatsApp conversation-based cost estimate

Meta replaced conversation-based pricing on 1 July 2025. An old quote, spreadsheet or exported report may still count 24-hour conversations. Use this guide to identify its counting unit and prepare a current estimate for your ChatArchitect connection. An old conversation rate is not a current price per message or per active customer.

Separate the units before calculating

Illustrative example: if ten contacts each receive three delivered messages, that is thirty delivered messages and ten distinct recipients in that example. It does not establish thirty billable messages, ten billable conversations or the price of a ChatArchitect plan. Apply the relevant category, period and plan conditions before assigning a cost.

Update a worksheet for a current campaign

1. Record the dates, currency and billing unit of the original estimate. Keep it as a historical reference instead of replacing its rates while leaving its old conversation counts.
2. List the messages you now expect to deliver: template name and approved category, recipient destination, number of deliveries and intended billing month. Keep service replies separate from template deliveries.
3. Check the applicable subscription, included usage and additional charges on the ChatArchitect pricing page and in your current contract. ChatArchitect bills you for this connection; Meta's rate table does not by itself determine your ChatArchitect invoice.
4. Include any separate service-reply charge. Since 1 October 2026, Meta's current FAQ specifies an allowance of the first 1,000 service messages per business phone number each month. ChatArchitect charges service replies above that allowance separately. Ask support for the applicable rate and billing terms.
5. Confirm the assumptions using the current ChatArchitect message-cost guide before approving the budget. Do not carry forward an old promise of unlimited free service conversations.

Check an invoice or report that still says “conversations”

Ask which period and counting rule the label represents. A CRM conversation, an active client and Meta's former billing conversation can have different meanings. Preserve the original export and its definitions; do not convert a total to message charges without the underlying message counts and applicable terms.

For a current delivery-based estimate, separate accepted requests from later delivery results. Use the ChatArchitect sending guide and the statuses available in your sending tool. If delivery information is unavailable, record that gap and ask support how it affects the calculation.

When requesting a billing check, provide the connection's business number, invoice or estimate period, currency, plan, source report, counting unit and the disputed line. Include available message references without exposing your App key, Secret or full customer list. Ask support to reconcile the counting rule and applicable charge before treating the estimate as confirmed.

Reference for historical billing

Meta keeps its deprecated conversation-based pricing reference for historical billing data. For current platform rules, use the pricing and billing FAQ, especially its dated service-message allowance. For the amount payable through ChatArchitect, use your current ChatArchitect terms.