Limits and quotas
WhatsApp messaging is subject to two kinds of limits: the per-account service quotas that AWS End User Messaging applies, and the messaging limits and quality rules that Meta applies to your WhatsApp Business Account (WABA). Both affect how much you can send, so plan for both when you scale.
Topics
AWS End User Messaging service quotas
AWS End User Messaging applies per-account quotas to the resources and send rates that support WhatsApp messaging. For the account-level quotas that apply across channels, and how to request an increase, see Quotas.
WhatsApp messaging limits and quality tiers
Meta applies a messaging limit to your WhatsApp Business Account that caps how many unique recipients you can start conversations with in a rolling period. Meta also assigns a quality rating to each of your phone numbers based on how recipients respond to your messages, such as blocking or reporting them. Your messaging limit can increase as you send high-quality messages to engaged recipients, and it can decrease, or your number can be restricted, if your quality rating falls. These limits and ratings are managed by Meta, not by AWS End User Messaging, so follow the practices in Best practices to protect them.
Note
The exact WhatsApp messaging-limit tiers, the thresholds at which they increase or decrease, and the quality-rating levels are defined and changed by Meta [needs SME confirmation]. Confirm the current values against Meta's WhatsApp Business Platform documentation before publishing specific numbers.
Template limits
WhatsApp business messaging is template-first: you open a conversation with an approved template, and Meta reviews each template before you can use it. Meta applies limits to the number of templates on a WABA and to how templates are categorized and reviewed. For how to create and manage templates, see WhatsApp Message Templates.
Note
The exact template count limits per WABA and the per-category review rules are defined by Meta [needs SME confirmation].
