AWS Security ChangesHomeSearch

AWS social-messaging documentation change

Service: social-messaging · 2025-11-07 · Documentation low

File: social-messaging/latest/userguide/billing.md

Summary

Updated WhatsApp pricing model to volume-tiered system and added detailed SKU examples

Security assessment

This change relates to billing structure and pricing tiers, not security features or vulnerabilities. No security controls or vulnerabilities are mentioned.

Diff

diff --git a/social-messaging/latest/userguide/billing.md b/social-messaging/latest/userguide/billing.md
index 972cb8411..c2c7a38a9 100644
--- a//social-messaging/latest/userguide/billing.md
+++ b//social-messaging/latest/userguide/billing.md
@@ -13 +13 @@ You are billed on a per message basis when you use AWS End User Messaging Social
-Starting on July 1 2025, AWS End User Messaging Social, charges per message instead of per conversation for WhatsApp messages, inline with Meta’s change. This means that you are charged a `MetaTemplateMessageFee` instead of `ConversationFee` for the Meta fee, in addition to the AWS `MessageFee`. These changes are included in your monthly bills, starting from the bill for July 2025 that you receive in August 2025. To understand prior bills based on `ConversationFee`, see [Charged per conversation (Deprecated)](./charged-per-conversation.html).
+Starting November 2025, AWS End User Messaging Social will start implementing volume-tiered pricing for the Meta message fee, consistent with Meta's change. Any volume discounts for November 2025 will appear in November month-end invoices generated in December 2025. The volume-tiered prices, tier thresholds, and discounts are set by Meta, and subject to change by Meta. AWS will make reasonable efforts to notify you of changes to volume-tiers. For more information about tier thresholds and current rates, see [Meta's WhatsApp Business Platform pricing documentation](https://developers.facebook.com/docs/whatsapp/pricing/).
@@ -72 +72 @@ Meta `FeeType` |  This field displays the `MetaTemplateMessageFee` fee type for
-  
+Volume-tiered pricing is applicable on `Authentication`, `Authentication-International`, and `Utility` message types. For information about volume-tiered pricing, see Volume-tiered pricing.  
@@ -149,0 +150,44 @@ A service conversation is created when a business responds to a user's inbound m
+### Volume-tiered pricing
+
+AWS End User Messaging Social uses Meta's volume tiered pricing for WhatsApp template messages. When your monthly volume crosses tier thresholds, you benefit from lower per-message rates for Meta message fees for the remainder of that billing period. Currently, volume tiers apply to authentication, authentication-international and utility template messages by country, and do not apply to marketing template messages. The volume-tiered prices, tier thresholds, and discounts are set by Meta, and subject to change by Meta. AWS will make reasonable efforts to notify you of changes to volume tiers.
+
+Key pricing considerations include the following:
+
+  * Only template messages count toward volume calculations—non-template messages sent within customer service windows are always free.
+
+  * Tiers vary by country and message type (authentication versus utility), and reset monthly.
+
+  * Multiple WABAs in your account are aggregated together for tier determination.
+
+  * Mid-month tier changes apply discounted rates only to subsequent messages.
+
+
+
+
+Volume tiers on ongoing monthly usage are determined solely by Meta. AWS applies the volume tiers to ongoing usage as and when Meta informs us of tier changes. For more information about tier thresholds and current rates, see [Meta's WhatsApp Business Platform pricing documentation](https://developers.facebook.com/docs/whatsapp/pricing/).
+
+The following SKU examples show the volume-tiered pricing for `Authentication`, `Authentication-International`, and `Utility` message types.
+
+The following are examples of actual billing SKU names. These examples show `Meta FeeType` for messages sent or received from the `APS3` Region code (ap-south-1, Asia Pacific (Mumbai) Region), and sent to the ISO code IN (India).
+    
+    
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_Regular
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_Regular_TIER_1
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_Regular_TIER_2
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_Regular_TIER_3
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_Regular_TIER_4
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_Regular_TIER_5
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_International_Regular
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_International_Regular_TIER_1
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_International_Regular_TIER_2
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_International_Regular_TIER_3
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_International_Regular_TIER_4
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Authentication_International_Regular_TIER_5
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Utility_Regular
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Utility_Regular_TIER_1
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Utility_Regular_TIER_2
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Utility_Regular_TIER_3
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Utility_Regular_TIER_4
+    APS3-WhatsApp-IN-MetaTemplateMessageFee-Utility_Regular_TIER_5
+    
+