# United States 10DLC registration United States 10DLC registration **Important** The following table has the expected times for each 10DLC registration step based on if your business is located in the United States or internationally. **** | 10DLC registration step | US based companies | International based companies | | --- | --- | --- | | Register your brand/company | 1-2 business days | Up to 3 weeks | | Apply for vetting | 1-2 business days | Up to 3 weeks | | Register your campaign | Up to 4 weeks | Up to 4 weeks | | Request your 10DLC number | Up to 10 days | Up to 10 days | If you use AWS End User Messaging SMS to send messages to recipients in the United States or the US territories of Puerto Rico, US Virgin Islands, Guam and American Samoa, you can use 10DLC phone numbers to deliver those messages. The abbreviation *10DLC* stands for "10-digit long code." A 10DLC phone number is registered for use by a single sender and for a single use case. This registration process gives the mobile carriers insight into the approved use cases for each phone number that is used to send messages. As a result, 10DLC phone numbers can offer high throughput and deliverability rates. A message that you send from a 10DLC phone number appears on the devices of your recipients as a 10-digit phone number. You can use 10DLC phone numbers to send both transactional and promotional messages. If you already use short codes or toll-free numbers to send your messages, then you don't need to set up 10DLC. To set up 10DLC, you first register your company or brand. You should then externally vet your 10DLC company to ensure you get the highest eligible throughput. Next, you create a *10DLC campaign*, which is a description of your use case. This information is then shared with the Campaign Registry, an industry organization that collects 10DLC registration information. **Note** For more information about how the Campaign Registry uses your information, see the FAQ on the [Campaign Registry website](https://www.campaignregistry.com/resources/). After your company and 10DLC campaign are approved, you can purchase a phone number and associate it with your 10DLC campaign. Associating a phone number with a 10DLC campaign can take approximately 14 days to complete. Although you can associate multiple phone numbers with a single campaign, you can't use the same phone number across multiple 10DLC campaigns. For each 10DLC campaign that you create, you must have at least one unique phone number. Throughput for 10DLC phone numbers is based on the company and campaign registration information that you provide. Each 10DLC number associated to a campaign supports 1 message part per second (MPS). In order 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. If you have an existing unregistered long code in your AWS End User Messaging SMS account, you can request that it be converted to a 10DLC number. To convert an existing long code, complete the registration process, and then create a case in the AWS Support Center. In some situations, it isn't possible to convert an unregistered long code to a 10DLC phone number. In this case, you must request a new number through the AWS End User Messaging SMS console and associate it with your 10DLC campaign. For more information about using 10DLC with existing long codes, see [Associating a long code with a 10DLC campaign](registrations-10dlc-associate.md). **Topics** + [ ## 10DLC capabilities ](#registrations-10dlc-capabilities) + [ # 10DLC registration process ](registrations-10dlc-setup.md) + [ # 10DLC brand registration form ](registrations-10dlc-company.md) + [Resend a 10DLC brand email authentication](registrations-10dlc-auth.md) + [ # 10DLC brand vetting form ](registrations-10dlc-vetting.md) + [ # 10DLC campaign registration form ](registrations-10dlc-register-campaign.md) + [ # Associating a long code with a 10DLC campaign ](registrations-10dlc-associate.md) + [ ## 10DLC registration and monthly fees ](#registrations-10dlc-fees) + [ # 10DLC cross-account access ](registrations-10dlc-configure-cross-account-access.md) ## 10DLC capabilities **Note** **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. In order 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. 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. 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. 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.md). 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.\]](http://docs.aws.amazon.com/sms-voice/latest/userguide/images/registrations-10dlc-capabilities.png) Throughput rates for 10DLC are determined by the US mobile carriers in cooperation with the Campaign Registry. Neither AWS End User Messaging SMS nor any other SMS sending service can increase 10DLC throughput beyond these rates. If you need high throughput rates and high deliverability rates across all US carriers, we recommend that you use a short code. # 10DLC registration process You can set up 10DLC directly in the AWS End User Messaging SMS console. To set up 10DLC, you must complete all of the following steps. 1. **Register your brand/company** The first step in setting up 10DLC is to register your company or brand. For information about company registration, see [10DLC brand registration form](registrations-10dlc-company.md). There is a one-time registration fee to register your company. This fee is shown on the registration page. 1. **(Optional, but recommended) Apply for vetting** If your company registration is successful, you can begin creating low-volume, mixed-use 10DLC campaigns. These campaigns can send 75 messages per minute to recipients who use AT&T, and your registered company can send 2,000 messages per day to recipients who use T-Mobile. If your use case requires a throughput rate that exceeds these values, you can apply for vetting of your company registration. Vetting your company registration can increase the throughput rates for your companies and campaigns, but it isn't guaranteed to do so. For more information about vetting, see [10DLC brand vetting form](registrations-10dlc-vetting.md). 1. **Register your campaign** If the Campaign Registry is able to verify the company information that you provided, you can create a 10DLC campaign. A 10DLC campaign contains information about your use case. Each 10DLC campaign can be associated with one company. AWS End User Messaging SMS sends this campaign information to the Campaign Registry for approval. In most cases, 10DLC campaign approval is instantaneous. In some cases, the Campaign Registry can require additional information. It can take up to 4 weeks to receive a response on if your 10DLC campaign was approved or needs to be revised. You're charged a recurring monthly fee for each 10DLC campaign that you register. The monthly fee varies depending on your use case. The recurring fee for your campaign is shown on the registration page. 1. **Request your 10DLC number** After your 10DLC campaign is approved, you can request a phone number and associate that number with the approved 10DLC campaign. Each phone number can only be associated with a single 10DLC campaign. For more information on requesting a 10DLC phone number, see [Request a phone number in AWS End User Messaging SMS](phone-numbers-request.md) and [Associating a long code with a 10DLC campaign](registrations-10dlc-associate.md). There is a monthly recurring fee for leasing the phone number. This fee is shown on the purchase page. **Note** You are charged the monthly 10DLC number lease price regardless of status. For example, 10DLC numbers in a **Pending** state still generate a month fee. For more information about pricing, see [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/). # 10DLC brand registration form **Note** With our updated console experience you are now seeing a registration **Name** field for your registration. This field is set to "–" as we do not manually backfill any of your service values to prevent interruption to your service and let you maintain your security posture. A registration **Name** is an optional friendly name field that can be updated using the tags on the registration details page. For more information on how to add a **Name** tag, see [Change a registration's name in AWS End User Messaging SMS](registrations-friendly-name.md). Before you can request a 10DLC phone number, you must register your company or brand. Brand registrations are managed by an industry organization called the Campaign Registry. You need to register your company per each AWS account and AWS Region that will use the company. **Note** Campaign Registry has implemented a two-factor authentication (2FA) for brand registrations. If your **Legal form of organization** is PUBLIC\$1PROFIT you have to provide the email address of a person who works at the brand who can complete the email authentication. Email distribution lists are not allowed and the email domain must match the domain of your business. The email authentication is sent from **noreply@auth.campaignregistry.com** and we recommend you add the email address to your spam list allow rules. After you've created your 10DLC brand registration you need to complete the form and submit it for approval. If your 10DLC brand registration is successful and you want to register for higher throughput capabilities, then you must vet your 10DLC brand registration. For more information on 10 DLC brand vetting, see [10DLC brand vetting form](registrations-10dlc-vetting.md). **Note** For more information on expected registration times, see [United States 10DLC registration](registrations-10dlc.md). **Complete a 10DLC brand registration** 1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/). 1. In the navigation pane, under **Registrations**, choose the 10DLC brand registration to complete. 1. In the **Brand Registration Information** section, enter the following: + For **Legal company name**, enter the name that the company is registered under. The name that you enter must be an exact match for the company name that's associated with the tax ID that you provide. **Important** Make sure to use your company's exact legal name. Incorrect or incomplete information might result in your registration being delayed or denied. + For **Country of tax registration**, enter the two letter ISO country code for the country where your company is registered. For a list of ISO country codes, see [Supported countries and regions for SMS messaging with AWS End User Messaging SMS](phone-numbers-sms-by-country.md). + For **Tax ID or Business Registration Number**, enter your company's tax ID. The ID that you enter depends on the country that your company is registered in. + If you're registering a US or non-US entity that has an IRS Employer Identification Number (EIN), enter your nine-digit EIN. The legal company name, EIN, and physical address that you enter must all match the company information that is registered with the IRS. + If you're registering a Canadian entity, enter your federal or provincial Corporation number. Don't enter the Business Number (BN) provided by the CRA. The legal company name, Corporation number, and physical address that you enter must all match the company information that is registered with Corporations Canada. + If you're registering an entity that is based in another country, enter the primary tax ID for your country. In many countries, this is the numeric portion of your VAT ID number. + For **Legal form of organization**, choose the option that best describes your company. **Note** The **US government** and **Not-for-profit** options can only be used to register United States-based organizations. If your organization is based in a country other than the US, you must register as **Private for-profit**, regardless of the actual legal form of your organization. + For **Stock symbol - optional** enter your companies stock symbol. For **Stock exchange - optional**, choose the stock exchange your company is listed on **Note** If you chose **Public for profit** in the previous step, the company's stock symbol and the stock exchange fields are required. + For **Physical business address – Address/Street**, enter the physical street address associated with your company. + For **Physical business address – City**, enter the city where the physical address is located. + For **Physical business address – State or region**, enter the state or region where the address is located. + For **Physical business address – Zip Code/Postal Code**, enter the ZIP or postal code for the address. + For **Physical business address – Country**, enter the two digit ISO country code. + For **Brand verification email**, enter the email of a person who works at the brand who can complete the email authentication. Email distribution lists are not allowed and the email domain must match the domain of your business. 1. Choose **Next**. 1. In the **Additional company and contact info** section, enter the following: + For **Doing Business As (DBA) or brand name**, enter any other names that your company does business as. + For **Vertical**, choose the category that best describes the company you're registering. + For **Company website**, enter the full URL of your company's website. Include "http://" or "https://" at the beginning of the address. + For **Support Email**, enter the email address of the person who will be your business's point of contact. + For **Support Phone Number**, enter the phone number of the person who will be your business's point of contact. The phone number must start with a '\$1' and can't contain any spaces, hyphens, or parentheses. For example, `+1 (206) 555-0142` is not in the correct format, but `+12065550142` is. Choose **Next**. 1. On the **Review and submit** page verify the information you are about to submit is correct. To make updates choose **Edit** next to the section. 1. Choose **Submit registration**. **Important** If your **Legal form of organization** is PUBLIC\$1PROFIT then once you submit your brand registration the authentication email is sent to the email address specified in **Brand verification email**. Your registration can not be approved until you complete brand authentication. The authentication email is valid for 7 days and after that you have to [request a new authentication email](registrations-10dlc-auth.md#registrations-10dlc-auth.title). **Note** After your registration has been approved you need to either register for the optional **US 10DLC Brand vetting** or [10DLC campaign registration form](registrations-10dlc-register-campaign.md). For more information on registering for 10DLC, see [United States 10DLC registration](registrations-10dlc.md). # Resend a 10DLC brand email authentication in AWS End User Messaging SMS Resend a 10DLC brand email authentication The email authentication is sent from **noreply@auth.campaignregistry.com** and we recommend you add the email address to your spam list allow rules. The link in the email authentication is valid for 7 days. Follow these directions if it has been less than 30 days since you submitted for 10DLC brand registration. If it has been longer than 30 days you need to [discard the registration](registrations-discard.md#registrations-discard.title) and resubmit it. **Resend authentication email** 1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/). 1. In the navigation pane, under **Configurations**, choose **Registrations**. 1. Choose the 10DLC brand registration that you need to resend the 2FA email for. 1. Choose resend email in the banner. # 10DLC brand vetting form If your company's registration is successful and you want to register a 10DLC campaign with higher throughput capabilities, then you must vet your company registration. When you vet your registration, a third-party organization analyzes the company details that you provided and returns a vetting score. A high vetting score can lead to higher throughput rates for your 10DLC company and the campaigns associated with it. However, vetting isn't guaranteed to increase your throughput. Vetting scores aren't applied retroactively. In other words, if you've already created a 10DLC campaign, and you later vet your company registration, your vetting score isn't automatically applied to your existing campaign. For this reason, you should vet your company or brand *before* you create any of your 10DLC campaigns. **Note** There is a \$140 non-refundable fee for vetting your company or brand. **Note** For more information on expected registration times, see [United States 10DLC registration](registrations-10dlc.md). **To vet your company registration** 1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/). 1. In the navigation pane, under **Registrations**, choose **Create registration**. 1. For **Registration form name** enter a friendly name. 1. For **Registration type**, choose **US 10DLC brand vetting**. 1. For **Available 10DLC brands**, choose the 10DLC brand to vet. 1. Choose **Create**. # 10DLC campaign registration form **Note** With our updated console experience you are now seeing a registration **Name** field for your registration. This field is set to "–" as we do not manually backfill any of your service values to prevent interruption to your service and let you maintain your security posture. A registration **Name** is an optional friendly name field that can be updated using the tags on the registration details page. For more information on how to add a **Name** tag, see [Change a registration's name in AWS End User Messaging SMS](registrations-friendly-name.md). AWS End User Messaging SMS’s vendors perform a manual review processes on 10DLC (10 Digit Long Code) campaigns to address SMS spam concerns raised by US carriers. Reviews are triggered when a number is associated to a 10DLC campaign. Reviews take at least 4 to 6 weeks to process. When you register a 10DLC campaign, you provide a description of your use case, as well as the message templates that you plan to use. Before you can create and register a 10DLC campaign, you must first register your company. For information on registering your company, see [10DLC brand registration form](registrations-10dlc-company.md). **Note** For more information on expected registration times, see [United States 10DLC registration](registrations-10dlc.md). For more information on 10DLC campaign registration issues, see [Gen-AI Feedback on Registrations (Preview)](registrations-genai-feedback.md). In this section, you provide additional details about your 10DLC campaign. **To register a 10DLC campaign** 1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/). 1. In the navigation pane, under **Registrations**, choose the 10DLC campaign registration to complete. 1. On the **10DLC campaign registration information** page, do the following: 1. For **Campaign description**, enter a name for the 10DLC campaign and description of the campaigns purpose. 1. For **Vertical**, choose the option that represents your company. 1. For **Company Terms & Conditions** choose either: 1. **Enter URL** – Enter the publicly accessible URL that contains the **Terms & Conditions**. 1. **Upload file** and then **Choose file** – Choose a file that contains the **Terms & Conditions**. The file can be up to 500KB and valid file formats are PNG, JPEG, and PDF. 1. For **Privacy Policy** choose either: 1. **Enter URL** – Enter the publicly accessible URL that contains the **Privacy Policy**. 1. **Upload file ** and then **Choose file** – Choose a file that contains the **Privacy Policy**. The file can be up to 500KB and valid file formats are PNG, JPEG, and PDF. 1. For **Campaign opt-in workflow**, enter a description of how users consent to receive SMS and MMS messages. The description has to be between 40 – 2048 characters and must not contain leading or trailing spaces. For example, by filling out an online form on your website. If you have multiple opt-in methods, they have to be listed as well. Your **Opt-in workflow** should include the following: + Program or product description + Identify your organization and service being represented in the initial message sent to your end users + Clear and thorough information about how your end-users opt-in to your SMS service and any associated fees or charges + Include a link to the Terms & Conditions (which must be publicly accessible). + Include a link to the Privacy Policy (which must be publicly accessible). **Note** If you don't have publicly accessible links to your Company Terms & Conditions or Privacy Policy documents then you can provide a copy of those as a document in the attachment fields for **Company Terms & Conditions** or **Privacy Policy**. + Explain if the Opt-in/Call to Action requires service log-in, is not yet published publicly, is a verbal opt-in, or if it occurs on printed sources such as fliers and paper forms. + The Call to Action/Opt-in location must include the following: + Comprehensive terms and conditions might be presented in full beneath the call-to-action, or they might be accessible from a link in proximity to the call-to-action. + Program (brand) name. + Message frequency disclosure. + Product description. + Customer care contact information. + Opt-out information. + “Message and data rates may apply” disclosure. 1. For **Campaign opt-in screenshot**, upload a file showing how users consent to receiving messages, as described in the **Campaign opt-in workflow** field. The supported file type are PNG, JPEG, and PDF and the maximum file size is 500KB. A screenshot or mockup is required unless you provide a publicly accessible URL to your opt-in location or call-to-action in the **Campaign opt-in workflow** field. If your opt-in process requires a login, is not yet public, is a verbal opt-in, or occurs on printed forms or fliers, you must provide a screenshot or mockup showing the complete opt-in process. Additional information and examples of a compliant opt-in workflow can be found at [Obtain permission](best-practices.md#best-practices-sms-obtain-permission). **Important** **Website opt-in**: Mockup or screenshots of a web-form where the client adds their number and agrees to receive messages. **Website Posting (Support)**: Where is the number advertised and where does the customer find the number to text in. **Keyword or QR Code Opt-in**: Where does the customer find the keyword or QR code in order to opt-in to these messages. **2FA/OTP**: Mockup or screenshot of opt-in if applicable, if verbal, provide a mockup or screenshot of the verbal opt-in script. **Informational**: Provide a mockup or screenshot of a verbal consent workflow and provide the messaging content. 1. For **Opt-in keyword – optional** enter the keyword that your customers will send to consent to opt-ing in. 1. For **Opt-in confirmation message** enter the message that your customers receive if they send the Opt-in keyword to your 10DLC phone number. 1. For **Help Message**, enter the message that your customers receive if they send the keyword "HELP" to your 10DLC phone number. The message has to be a minimum of 20 characters. 1. For **Stop Message**, enter the message that your customers receive if they send the keyword "STOP" to your 10DLC phone number. The message has to be a minimum of 20 characters. **Tip** Your customers can reply to your messages with the word "HELP" to learn more about the messages that they're receiving from you. They can also reply "STOP" to opt-out of receiving messages from you. The US mobile carriers require you to provide responses to both of these keywords. The following is an example of a HELP response that complies with the requirements of the US mobile carriers: **ExampleCorp Account Alerts: For help call 1-888-555-0142 or go to example.com. Msg&data rates may apply. Text STOP to cancel.** The following is an example of a compliant STOP response: **You are unsubscribed from ExampleCorp Account Alerts. No more messages will be sent. Reply HELP for help or call 1-888-555-0142.** Your responses to these keywords must contain 160 characters or fewer. 1. Choose **Next**. 1. For the **Messaging capabilities** section, do the following: 1. The capabilities you select are applied to your 10DLC phone number when you create the phone number request. For **Number capabilities**, choose: + Choose **SMS** to enable text messages for the 10DLC campaign. + Choose **SMS and MMS** to enable text and multimedia messages for the 10DLC campaign. + Choose **SMS and Voice** to enable text and voice messages for the 10DLC campaign. **Note** When you choose to enable voice messages, it lengthens the amount of time to review your registration. + Choose **SMS and MMS and VOICE** to enable text and multimedia messages for the 10DLC campaign. 1. For **Message type – optional**, choose either **Transactional** or **Promotional** message type. + **Transactional** – Choose this option if your use case is for time-sensitive content, such as alerts and one-time passwords. + **Promotional** – Choose this option if your use case is for marketing-related content. 1. Choose **Next**. 1. For **Messaging use case** section, do the following: 1. For **Use case**, choose a use case that most closely resembles your campaign from the preset list of use cases. + **Account Notifications** – Standard notifications for account holders, relating to and being about an account. + **Charity** – Communications from a non-religious registered [501(c)(3) charity](https://en.wikipedia.org/wiki/501(c)(3)_organization) aimed at providing help and raising money for those in need. + **Customer care** – All customer interaction, including account management and customer support. + **Delivery notifications** – Information about the status of the delivery of a product or service. + **Fraud alert messaging** – Messaging regarding potential fraudulent activity on an account. + **Higher education** – Campaigns created on behalf of Colleges or Universities. It also includes School Districts and education institutions that fall outside of any "free to the consumer" messaging model. + **Low Volume** – Small throughput, any combination of use-cases. Examples include: test, demo accounts. + **Marketing** – Any communication with marketing and/or promotional content. + **Mixed** – Mixed messaging reserved for specific consumer service industry. + **Public service announcement** – An informational message that is meant to raise the audience's awareness about an important issue. + **Polling and voting** – Requests for surveys and voting for non political arenas. + **Security alert** – A notification that the security of a system, either software or hardware, has been compromised in some way and there is an action the end users need to take. + **Two factor authentication** – Any authentication, verification, or one-time passcode. 1. For **Sub use case – optional**, choose up to five sub use cases. 1. **Subscriber opt-in** – Subscribers can opt in to receive messages about this campaign. 1. **Subscriber opt-out** – Subscribers can opt out of receiving messages about this campaign. 1. **Subscriber help** – Subscribers can contact the message sender after sending the HELP keyword. 1. **Direct lending or loan arrangement ** – The campaign includes information about direct lending or other loan arrangements. 1. **Embedded link ** – Choose **Yes** if the 10DLC campaign includes an embedded link. Links from common URL shorteners, such as TinyUrl or Bit.ly, are not allowed. However, you can use URL shorteners that offer custom domains. 1. **Embedded link sample - optional** – An example of an embedded link that to be sent. Links from common URL shorteners, such as TinyUrl or Bit.ly, are not allowed. However, you can use URL shorteners that offer custom domains. 1. **Embedded phone number** – The campaign includes a phone number that isn't a customer support number. 1. **Age-gated content** – The 10DLC campaign includes age-gated content as defined by carrier and Cellular Telecommunications and Internet Association (CTIA) guidelines. 1. Choose **Next**. 1. In the **Message samples** section, do the following: 1. Enter at least one **Message sample**. This is the sample text message that you plan to send to your customers. Each sample message has to be a minimum of 20 characters. If you plan to use multiple message templates for this 10DLC campaign, include them as well. **Important** Don't use placeholder text for your sample messages. The example messages that you provide should reflect the actual messages that you plan to send as accurately as possible and should not contain any [Prohibited message content](best-practices.md#best-practices-sms-message-content). 1. Choose **Next**. 1. In the **MMS file samples** section, do the following: 1. (Optional) MMS sample files are only required if you plan to send MMS messages. In **MMS file samples** upload at least one sample image. A single MMS media file can be up to 500KB for GIF, JPEG, and PNG, and 600 KB in size for all other media file types, see [MMS file types, size and character limits](mms-limitations-character.md). **Important** Don't use placeholder text in your sample MMS images. The example MMS images that you provide should reflect the actual MMS image that you plan to send as accurately as possible and should not contain any [Prohibited message content](best-practices.md#best-practices-sms-message-content). 1. Choose **Next**. 1. On the **Review and submit** page, verify the information you're about to submit is correct. To make updates choose **Edit** next to the section. 1. Choose **Submit registration**. **Note** After your 10DLC campaign registration has been approved you can request a new 10DLC phone number or use an existing 10DLC phone number and associate it with the 10DLC campaign. For more information on registering for 10DLC, see [Requesting dedicated long codes](phone-numbers-request-long-code.md). # Associating a long code with a 10DLC campaign After your 10DLC campaign is approved, you have provisioned a new long code or have an existing long code you can then associate that long code with the approved 10DLC campaign. The long code that you associate with the 10DLC campaign can only be used with that campaign, and you can't use it for any other 10DLC campaign. 1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/). 1. In the navigation pane, under **Registrations**, choose the 10DLC campaign(US\$1TEN\$1DLC\$1CAMPAIGN\$1REGISTRATION) to associate the long code with. 1. Choose the **Associated resourced** tab and **Add resource**. 1. For **Supported association**, choose **TEN\$1DLC** from the dropdown list. 1. For **Available resources**, choose the 10DLC phone number to add. 1. Choose **Associate resource**. You can associate more than one long code with the 10DLC campaign. ## 10DLC registration and monthly fees There are registration and monthly fees associated with using 10DLC, such as registering your company and 10DLC campaign. These are separate from any other monthly or AWS fees. For more information about 10DLC fees, see the [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/) page. # 10DLC cross-account access Each 10DLC phone number is associated with a single account in a single AWS Region. If you want to use the same 10DLC phone number to send messages in more than one account or Region, you have two options: 1. You can register the same company and campaign in each of your AWS accounts. These registrations are managed and charged separately. If you register the same company in multiple AWS accounts, the number of messages that you can send to T-Mobile customers per day is shared across each of those accounts. 1. You can complete the 10DLC registration process in one AWS account, and use AWS Identity and Access Management (IAM) to grant other accounts permission to send through your 10DLC number. **Note** This option allows for true cross-account access to your 10DLC phone numbers. However, note that messages sent from your secondary accounts are treated as if they were sent from your primary account. Quotas and billing are counted against the primary account and not against any secondary accounts. ## Setting up cross-account access using IAM policies You can use IAM roles to associate other accounts with your main account. Then, you can delegate access permissions from your primary account to your secondary accounts by granting them access to the 10DLC numbers in the primary account. **To grant access to a 10DLC number in your primary account** 1. If you haven't already done so, complete the 10DLC registration process in the primary account. This process involves three steps: + Register your company. For more information, see [10DLC brand registration form](registrations-10dlc-company.md). + Register your 10DLC campaign (use case). For more information, see [10DLC campaign registration form](registrations-10dlc-register-campaign.md). + Associate a phone number with your 10DLC campaign. For more information, see [Associating a long code with a 10DLC campaign](registrations-10dlc-associate.md). 1. Create an IAM role in your primary account that allows another account to call the `SendTextMessage` API operation for your 10DLC phone number. For more information on creating roles, see [Creating IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) in the *IAM User Guide*. 1. Delegate and test access permission from your primary account using IAM roles with any of your other accounts that need to use your 10DLC numbers. For example, you might delegate access permission from your Production account to your Development account. For more information about delegating and testing permissions, see [Delegate access across AWS account using IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html) in the *IAM User Guide*. 1. Using the new role, send a message using a 10DLC number from a secondary account. For more information about using a role, see [Using IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*.