AWS Security ChangesHomeSearch

AWS sms-voice: Rewrites 10DLC throughput, MPS limits, and vetting guidance

Service: sms-voice · 2026-09-27 · Documentation low

File: sms-voice/latest/userguide/registrations-10dlc.md

Summary

Replaces the old 10DLC throughput documentation: clarifies that campaign throughput is applied automatically (no separate MPS increase request), explains that the send rate limit is shared at the campaign level across associated numbers, updates carrier limit wording, describes the T-Mobile advisory daily cap, and advises vetting the company/brand before creating campaigns since vetting scores are not applied retroactively. Removes the throughput flowchart image.

Security assessment

The change is purely operational documentation about SMS throughput limits, campaign-level rate sharing, and vetting timing. No authentication, encryption, credential, or vulnerability content is present; the closest security-adjacent mention is Verizon's spam/abuse filtering, which is pre-existing text and unchanged in substance.

Evidence

+Throughput is applied at the _campaign_ level. All phone numbers associated with the same campaign share a single send rate limit, rather than each number having its own.

Diff

diff --git a/sms-voice/latest/userguide/registrations-10dlc.md b/sms-voice/latest/userguide/registrations-10dlc.md
index 0a6a8212b..b710eadcd 100644
--- a//sms-voice/latest/userguide/registrations-10dlc.md
+++ b//sms-voice/latest/userguide/registrations-10dlc.md
@@ -63 +63 @@ If you have an existing unregistered long code in your AWS End User Messaging SM
-**Important:** Brand registration and external brand vetting alone does not automatically increase the default of 1 MPS limit per number associated to an approved 10DLC campaign. To get the eligible throughput from your campaign applied to the associated 10DLC numbers, you need to submit a request to increase SMS sending rates.
+When your 10DLC campaign is approved, AWS End User Messaging SMS automatically applies the message throughput that the campaign qualifies for to the phone numbers associated with that campaign. You do not need to submit a separate request to increase the message parts per second (MPS) for those numbers.
@@ -65 +65 @@ If you have an existing unregistered long code in your AWS End User Messaging SM
-The capabilities of 10DLC phone numbers depend on which mobile carriers your recipients use. AT&T provides a limit on the number of message parts that can be sent each minute for each campaign. T-Mobile provides a daily limit of messages that can be sent for each company, with no limit on the number of message parts that can be sent per minute. Verizon hasn't published throughput limits, but uses a filtering system for 10DLC that is designed to remove spam, unsolicited messages, and abusive content, with less emphasis on the actual message throughput.
+The capabilities of 10DLC phone numbers depend on which mobile carriers your recipients use. AT&T provides a per-second send rate for each campaign. T-Mobile provides a daily limit on the number of messages that can be sent, with no separate per-second send rate. Verizon has not published throughput limits, but uses a filtering system for 10DLC that is designed to remove spam, unsolicited messages, and abusive content, with less emphasis on the actual message throughput.
@@ -67 +67 @@ The capabilities of 10DLC phone numbers depend on which mobile carriers your rec
-New 10DLC campaigns that are associated with _unvetted_ companies can send 75 message parts per minute to recipients who use AT&T, and 2,000 messages per day to recipients who use T-Mobile. The company limit is shared across all of your 10DLC campaigns. For example, if you have registered one company and two campaigns, the daily allotment of 2,000 messages to T-Mobile customers is shared across those campaigns. Similarly, if you register the same company in more than one AWS account, the daily allotment is shared across those accounts.
+Throughput is applied at the _campaign_ level. All phone numbers associated with the same campaign share a single send rate limit, rather than each number having its own. Each associated phone number shows the campaign's send rate as its limit. Because the limit is shared, messages sent from multiple numbers on the same campaign count toward the same limit. For example, if a campaign has a send rate limit of 8 message parts per second (MPS), you can send up to 8 MPS from a single number on that campaign. You can also split that throughput across multiple numbers, such as 4 MPS from each of two numbers. In both cases, the combined rate across the campaign cannot exceed 8 MPS before messages are throttled.
@@ -69 +69 @@ New 10DLC campaigns that are associated with _unvetted_ companies can send 75 me
-If your throughput needs exceed these limits, you can request that your company registration be vetted. When you vet your company registration, a third-party verification provider analyzes your company details. The verification provider then provides a vetting score, which determines the capabilities of your 10DLC campaigns. There is a one-time charge for the vetting service. For more information, see [10DLC brand vetting form](./registrations-10dlc-vetting.html).
+The T-Mobile daily message cap is advisory and is applied per campaign for T-Mobile recipients. After a campaign reaches its daily message cap, additional messages to T-Mobile recipients fail until the cap resets. For instructions on viewing the current send rate limits and daily message caps for a phone number, see [View your current messaging limits](./sms-limitations-mps-view.html).
@@ -71,3 +71 @@ If your throughput needs exceed these limits, you can request that your company
-Your actual throughput rate will vary depending on various factors, such as whether or not your company has been vetted, your campaign types, and your vetting score. The following flowchart shows the throughput rates for various situations.
-
-![Message throughput based on carrier and reputation.](/images/sms-voice/latest/userguide/images/registrations-10dlc-capabilities.png)
+To increase the throughput that a campaign qualifies for, you can request that your company registration be vetted. When you vet your company registration, a third-party verification provider analyzes your company details and provides a vetting score. A higher score can raise the throughput tier that your campaigns qualify for. Vetting scores are not applied retroactively: if you vet your company registration after you have already created a campaign, the new score is not applied to that existing campaign. For this reason, vet your company or brand _before_ you create your 10DLC campaigns. There is a one-time charge for the vetting service. For more information, see [10DLC brand vetting form](./registrations-10dlc-vetting.html).