# Throughput and Daily Caps

### T-Mobile Brand daily cap&#x20;

A Brand's total traffic towards T-Mobile network (and T-Mobile network alone) is limited by a daily cap based on the Brand's Trust Score. The brand's traffic cap is enforced when the maximum number of messages is achieved by any combination of this brand's campaigns and enforced until midnight Pacific time of the same calendar day.

{% hint style="danger" %}
The daily cap is assigned to a TAX ID, if you utilized multiple vendors, reaching a threshold on one vendor, may block traffic via the other.&#x20;
{% endhint %}

<figure><img src="/files/c82dWzEdbQdNFlUkxdYw" alt=""><figcaption></figcaption></figure>

**Messages will be blocked when your Brand is sending volumes above the daily cap. These will be charged and will fail with source**`sms-messagebird` and  code 1`06: EC_CAMPAIGN_VOLUME_EXCEEDED`

### AT\&T Campaign Throughput limit&#x20;

The traffic towards AT\&T will be throttled, and **Bird will buffer any message  (both SMS or MMS) above the limits** recognized as direct towards the AT\&T network at no extra cost, but this is an **best effort service, and some traffic may slip through and be rejected by the carrier.** Those messages will be charged and will fail with source `sms-messagebird` and  code `107: EC_CAMPAIGN_THROUGHPUT_EXCEEDED`

AT\&T throughput limitation is on a campaign level and depends on the type of the campaign see schema below:

<figure><img src="/files/2XCFw8Zkw1Am4j6NF5kb" alt=""><figcaption></figcaption></figure>

### Other networks

Verizon, US Cellular, Interop and ClearSky Groups do not provide any information about their throttling strategy; however, experience shows sending at a high rate usually results in the sender number being blacklisted by the carriers. In order to preserve functionality for all customers' numbers, Bird does enforce the same AT\&T limitation for the above mentioned mobile networks.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/applications/channels/channels/supported-channels/sms/concepts/united-states-sms-registration/sms-10dlc/throughput-and-daily-caps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
