AtServiceTech

WHATSAPP · GUIDE

WhatsApp Business API Pricing, Consent, and Launch Checklist

WhatsApp costs and messaging eligibility depend on Meta's current pricing, message category, recipient market, and the provider model. Build transparent usage reporting and consent controls before offering WhatsApp sending to clients.

Understand who bills whom

Under the Tech Provider model, the client business generally adds its own payment method and Meta bills WhatsApp usage to the client. AtServiceTech may separately charge for its software or services under its own published terms. Solution Partner credit lines and direct WhatsApp usage billing are separate capabilities and should not be assumed.

  • Meta's current pricing documentation says eligible business-to-user messages are charged based on delivery, category, and the recipient's market; user-to-business messages are not charged under the same business-message pricing model. Verify the current rate card and exceptions before quoting prices.
  • Display Meta charges, AtServiceTech subscription/service fees, taxes, and any markup as separate line items with clear attribution.
  • Do not hard-code rates into UI or docs without an effective date and a process for updating them.
  • Review Meta's current WhatsApp pricing and provider-model comparison before defining plans.

Consent, opt-out, and policy controls

Before enabling sends, require clients to confirm that they have the rights and permissions needed to message their recipients. Keep product controls aligned with the latest WhatsApp Business Messaging Policy and applicable local privacy and consumer-protection laws.

  • Record opt-in source, time, purpose, and scope where appropriate; honor opt-outs and suppression promptly.
  • Use approved templates for applicable outbound messages and respect the customer service window for non-template replies.
  • Provide complaint handling and a process to pause sending for policy, quality, account, or recipient-protection issues.
  • Publish privacy disclosures for WhatsApp data and define data retention, deletion, user access, and incident-response procedures.

Production readiness checklist

Launch gradually. Start with internal test businesses, verify account connections and webhook delivery, and expand only after tenant isolation and operational controls have been checked.

Steps

  1. Meta provider status, business verification, App Review, required Advanced Access, and Embedded Signup v4 are confirmed.
  2. Authorization-code exchange and token storage happen only on the server; secrets are encrypted, redacted, and revocable.
  3. A tenant-isolation test suite covers API routes, database access, webhooks, queues, exports, and support tooling.
  4. Webhook signature verification, deduplication, retries, delivery-state reconciliation, and alerting are operational.
  5. Template eligibility, consent, opt-out, customer-service window, and rate-limit checks run before every send.
  6. Client terms, privacy policy, Meta billing explanation, support escalation, disconnect, export, and deletion procedures are published.
  7. Run a limited pilot, monitor failures and user experience, then enable production access in stages.