# Request a phone number in AWS End User Messaging SMS
Request a phone number

Using the AWS End User Messaging SMS console, we’ll recommend one of the below origination identities depending on your use-case. Recommendations are based on your input criteria including if you require SMS, MMS, and/or voice capabilities, a two-way number, and estimate monthly messages. 

**Note**  
Depending on the country, the following phone number types have to be requested in the Support Center Console.  
**Short codes** – [Requesting dedicated short codes](phone-numbers-request-short-code.md).
**Long codes** – [Requesting dedicated long codes](phone-numbers-request-long-code.md).

**Note**  
You must use a **Resource policy** to share the phone number with Amazon Pinpoint or Amazon SNS even if you are using the same AWS account.

You can use either the AWS End User Messaging SMS console or AWS CLI to request a new phone number.

------
#### [ Request a phone number (Console) ]

**Important**  
To request a new phone number for the United States through the AWS End User Messaging SMS console follow the directions in the [Request a phone number for the United States (Console)](#request-us) tab.

To request a phone number using the AWS End User Messaging SMS console, follow these steps:

**Request a phone number (Console)**

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 **Phone numbers** and then **Request originator**.

1. On the **Select country** page you must choose the **Message destination country** from the dropdown that messages will be sent to. Choose **Next**.

1. On the **Messaging use case** section, enter the following:
   + Under **Number capabilities**, choose any combination of available capabilities:
**Important**  
Capabilities for SMS, MMS, and Voice can't be changed after the phone number has been purchased.
     + **Text messages (SMS)** Choose this if you need SMS capabilities.
     + **Text and media messages (SMS, MMS)** – Choose this if you need SMS and/or MMS capabilities. 
**Note**  
MMS capabilities are only available in certain countries and are only supported on certain origination types. **Text and media messages (SMS, MMS)** is only present if MMS is supported in the **Message destination country**. For more information, see [Supported countries and regions for MMS messaging in AWS End User Messaging SMS](phone-numbers-mms-by-country.md) and [Choosing an origination identity](phone-number-types.md). 
     + **Text to audio messages (Voice)** – Choose this if you need voice capabilities.
   + Under **Estimated monthly message volume – optional**, choose the estimated number of SMS messages you will send each month.
   + For **Company headquarters - optional**, choose either of the following:
     + **Local** – Choose this if your company's headquarters is in the same country as your customers who will revive SMS messages. For example, you would choose this option if your headquarters is in the United States and your users who will receive messages are also in the United States.
     + **International** – Choose this if your company's headquarters is not in the same country as your customers who will revive SMS messages.
   + For **Two-way messaging**, choose **Yes** if you require two-way messaging.

1. Choose **Next**.

1. Under **Select originator type**, choose either the recommend phone number type or one of the available number types. The available options are based on the use case information you filled out in the previous steps. 
   + If you choose 10DLC and already have a registered campaign you can choose the campaign from the **Associate to registered campaign** to add the 10DLC phone number to the 10DLC campaign.
   + If the number type you want isn't available you can choose **Previous** to go back and modify your use case. Also check the [Supported countries and regions for SMS messaging with AWS End User Messaging SMS](phone-numbers-sms-by-country.md) to make sure the originator type you want is supported in the destination country.
   + If you want to request a short code or long code you may need to open a case with Support. For more information, see [Requesting dedicated short codes](phone-numbers-request-short-code.md) and [Requesting dedicated long codes](phone-numbers-request-long-code.md).

1. Use **Resource policy** to share your phone number other AWS accounts or AWS services. To share the phone number at a later time, see [Sharing a phone number, pool, opt-out list, or sender ID](shared-resources.md#sharing-share). For more information on **Resource policy**, see [Working with shared resources in AWS End User Messaging SMS](shared-resources.md).
**Note**  
You must use a **Resource policy** to share the phone number with Amazon Pinpoint or Amazon SNS even if you are using the same AWS account.

   1. Choose **Pinpoint campaign orchestration(Amazon Pinpoint)** to share the pool with Amazon Pinpoint

   1. Choose **Simple notification Service (Amazon SNS)** to share the pool with Amazon SNS

1. Choose **Next**.

1. On **Review and request** you can verify and edit your request before submitting it. Choose **Request**.

1. A **Registration Required** window might appear depending on the type of phone number you requested. Your phone number or sender ID is associated with this registration and can't send messages until your registration has been approved. For more information about registrations requirements see [Origination identity registration in AWS End User Messaging SMS](registrations.md).

   1. For **Registration form name** enter a friendly name.

   1. Choose **Begin registration** to finish registering the phone number or **Register later**.
**Important**  
Your phone number or sender ID can't send messages until your registration has been approved.  
 You are still billed the recurring monthly lease fee for the phone number regardless of registration status. For more information about registrations requirements see [Origination identity registration in AWS End User Messaging SMS](registrations.md).

------
#### [ Request a phone number for the United States (Console) ]

**Important**  
Follow these directions to request a new phone number for the United States through the AWS End User Messaging SMS console.   
Before requesting a 10DLC phone number you must have an approved 10DLC registered brand and 10DLC registered campaign to associate with the 10DLC phone number. For more information on registering a 10DLC registered brand and 10DLC registered campaign, see [10DLC brand registration form](registrations-10dlc-company.md) and [10DLC campaign registration form](registrations-10dlc-register-campaign.md).  
The **Messaging capabilities** (SMS, MMS, or VOICE) are specified in the 10DLC registered campaign and applied to your 10DLC phone number request.

**Request a phone number for the United States (Console)**

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 **Phone numbers** and then **Request originator**.

1. On the **Select country** page you must choose the **United States (US)** from the **Message destination country** dropdown. Choose **Next**.

1. On the **Messaging use case** section, enter the following:
   + Under **Estimated monthly message volume – optional**, choose the estimated number of SMS messages you will send each month.
   + For **Company headquarters - optional**, choose either of the following:
     + **Local** – Choose this if your company's headquarters is in the same country as your customers who will revive SMS messages. For example, you would choose this option if your headquarters is in the United States and your users who will receive messages are also in the United States.
     + **International** – Choose this if your company's headquarters is not in the same country as your customers who will revive SMS messages.
   + For **Two-way messaging**, choose **Yes** if you require two-way messaging.

1. Choose **Next**.

1. Under **Originator type**, choose either the recommend phone number type or one of the available number types. The available options are based on the use case information you filled out in the previous steps. 
   + For a 10DLC phone number you have to choose the registered brand and registered campaign to associate with the 10DLC phone number request.
     + Use **Associate to registered brand** to choose a brand.
     + Use **Associate to registered campaign** to choose a campaign.
   + If you want to request a short code or long code you need to open a case with Support. For more information, see [Requesting dedicated short codes](phone-numbers-request-short-code.md) and [Requesting dedicated long codes](phone-numbers-request-long-code.md).

1. Use **Resource policy** to share your resources with other AWS accounts or AWS services. To share the phone number at a later time, see [Sharing a phone number, pool, opt-out list, or sender ID](shared-resources.md#sharing-share). For more information on **Resource policy**, see [Working with shared resources in AWS End User Messaging SMS](shared-resources.md).
**Note**  
You must use a **Resource policy** to share the phone number with Amazon Pinpoint or Amazon SNS even if you are using the same AWS account.

   1. Choose **Pinpoint campaign orchestration(Amazon Pinpoint)** to share the pool with Amazon Pinpoint

   1. Choose **Simple notification Service (Amazon SNS)** to share the pool with Amazon SNS

1. Choose **Next**.

1. On **Review and request** you can verify and edit your request before submitting it. Choose **Request**.

1. A **Registration Required** window might appear depending on the type of phone number you requested. Your phone number or sender ID is associated with this registration and can't send messages until your registration has been approved. For more information about registrations requirements see [Origination identity registration in AWS End User Messaging SMS](registrations.md).

   1. For **Registration form name** enter a friendly name.

   1. Choose **Begin registration** to finish registering the phone number or **Register later**.
**Important**  
Your phone number or sender ID can't send messages until your registration has been approved.  
 You are still billed the recurring monthly lease fee for the phone number regardless of registration status. For more information about registrations requirements see [Origination identity registration in AWS End User Messaging SMS](registrations.md).

------
#### [ Request a phone number (AWS CLI) ]

You can use the [request-phone-number](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/request-phone-number.html) command to add new phone numbers to your account. Phone number availability and supported features vary by country.

**Important**  
You might need to register the phone number or sender ID after you complete the request. You are still billed the recurring monthly lease fee for the phone number regardless of registration status. For more information about registrations requirements see [Origination identity registration in AWS End User Messaging SMS](registrations.md).  
MMS capabilities are only available in some countries. For more information on supported countries for SMS and MMS, see [Supported countries and regions for SMS messaging with AWS End User Messaging SMS](phone-numbers-sms-by-country.md) and [Supported countries and regions for MMS messaging in AWS End User Messaging SMS](phone-numbers-mms-by-country.md).

**To request a phone number**
+ At the command line, enter the following command:

  ```
  $ aws pinpoint-sms-voice-v2 request-phone-number \
  > --iso-country-code XX \
  > --message-type TRANSACTIONAL \
  > --number-capabilities VOICE \
  > --number-type LONG_CODE \
  > --pool-id poolId \
  > --deletion-protection-enabled \
  > --opt-out-list-name optOutListName \
  > --registration-id CO123EX
  ```

  In the preceding command, make the following changes:
  + Replace *XX* with the two-letter ISO-3166 alpha-2 code for the country of the phone number (such as `CA` for Canada).
  + If you want to use the phone number to send promotional or marketing-related content, replace *TRANSACTIONAL* with `PROMOTIONAL`. Otherwise, use `TRANSACTIONAL`.
  + If you want to request a phone number for sending SMS messages, replace *VOICE* with `SMS`. You can request a phone number with SMS, MMS, and voice message capabilities by specifying `SMS MMS VOICE`.
  + Replace *LONG\$1CODE* with the type of phone number you want to request. Acceptable values are `LONG_CODE`, `TOLL_FREE`, `TEN_DLC`, or `SIMULATOR`. 

    When you request a `SIMULATOR` phone number, you must set `message-type` as `TRANSACTIONAL`. 
  + Replace *poolId* with the ID or Amazon Resource Name (ARN) of the pool that you want to add the phone number to. This parameter is optional. If you don't want to add the phone number to a pool, omit this parameter.
  + If you want to enable deletion protection for this phone number, add the `--deletion-protection-enabled` parameter. Deletion protection is disabled by default. If deletion protection is enabled, you can't delete the phone number using the [ReleasePhoneNumber](https://docs.aws.amazon.com/pinpoint/latest/apireference_smsvoicev2/API_ReleasePhoneNumber.html) API, unless you update the configuration of the phone number to disable this feature.
  + Replace *optOutListName* with the name or ARN of the opt-out list that you want to associate with the phone number. This parameter is optional. If you don't want to associate the phone number with an opt-out list, omit this parameter.
  + If you're requesting a phone number to use with a 10DLC campaign, replace *CO123EX* with the ID of the 10DLC campaign that you want to use.
**Note**  
If you plan to use a 10DLC phone number, you must first register your company and campaign. Currently, the only way to complete these registration processes is to use the AWS End User Messaging SMS console. For more information about 10DLC registration, see [United States 10DLC registration](registrations-10dlc.md).

If the number is successfully added to your account, you see output similar to the following:

```
{
    "PhoneNumberArn": "arn:aws:sms-voice:us-east-1:111122223333:phone-number/phone-615790209ea34aea8da9b729fexample",
    "PhoneNumberId": "phone-615790209ea34aea8da9b729fexample",
    "PhoneNumber": "+12045550123",
    "Status": "PENDING",
    "IsoCountryCode": "CA",
    "MessageType": "TRANSACTIONAL",
    "NumberCapabilities": [
        "SMS"
    ],
    "NumberType": "LONG_CODE",
    "MonthlyLeasingPrice": "1.00",
    "TwoWayEnabled": false,
    "SelfManagedOptOutsEnabled": false,
    "OptOutListName": "Default",
    "DeletionProtectionEnabled": false,
    "CreatedTimestamp": 1645568542.0
}
```

**Note**  
When you first purchase a phone number, the value of the `Status` attribute is `PENDING`. When the phone number is ready to use, the value of `Status` changes to `ACTIVE`.

If a phone number that meets the parameters you specified isn't available, the request fails with an error.

------

**Topics**
+ [Requesting short codes](phone-numbers-request-short-code.md)
+ [Requesting long codes](phone-numbers-request-long-code.md)

# Requesting dedicated short codes
Requesting short codes

A short code is a number that you can use for high-volume SMS and MMS message sending. Short codes are often used for application-to-person (A2P) messaging, two-factor authentication (2FA), and marketing. A short code typically contains between five and seven digits, depending on the country that it's based in.

You can request a short code for the below countries through the End User Messaging console. If you require a short code in a country not included in the below list you can request a short code by opening a case in the Support by following the below process.

For information about short code pricing, see [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/).

## Important considerations


Before you request a short code, consider the following information:
+ If you plan to use the short code to send messages that contain Protected Health Information (PHI), you should identify this purpose in the **Case description** field of your support case.
+ AWS End User Messaging SMS currently only supports standard short codes. Free-to-End-User (FTEU) short codes aren't supported.
+ If you're new to SMS and MMS messaging with AWS End User Messaging SMS, you should request a monthly SMS and MMS spending threshold that meets the expected demands of your SMS and MMS use case. By default, your monthly spending threshold is \$11.00 (USD). You can request to increase your spending threshold in the same support case that includes your request for a short code. 

## Requesting a short code


You can only use short codes to send messages to recipients in the same country where the short code is based. If your use case requires you to use short codes in more than one country, you must request a separate short code for each country that your recipients are located in.

Countries support through console and APIs:
+ Chile (CL)
+ Finland (FI)
+ Germany (DE)
+ India (IN)
+ Netherlands (NL)
+ Spain (ES)
+ United Kingdom (GB)
+ United States (US)

## Step 1: Open a support case


The first step in requesting a short code is to open a Service Limit Increase case in the Support Center Console.

**To request a short code**

1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase).

1. On the **Create Case** page, complete the following:
   + Select **Account and Billing**.
   + For **Service**, choose **Service Quotas**.
   + For **Category** choose either **AWS End User Messaging SMS (Pinpoint)** or **AWS End User Messaging Voice (Pinpoint)**, depending on your request.
   + For **Severity**, choose **General Limits**.

1. In the **Requests** section, do the following:
   + For the **Region**, choose the AWS Region that you plan to send messages from.
**Note**  
The Region is required in the **Requests** section. Even if you provided this information in the **Case details** section you must also include it here.
   + For **Resource Type**, choose **Dedicated SMS Short Codes**.
   + For **Quota**, choose the message type that you plan to send using your short code.
     + **One Time Password/Two-Factor Authentication** – Messages that provide passwords that your customers use to authenticate with your website or application.
     + **Promotional/Marketing** – Noncritical messages that promote your business or service, such as special offers or announcements.
     + **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content.
     + **Transactional/Notifications/OTP/2FA** – All message types. 
   + For **New quota value**, enter the number of short codes that you want to purchase for the target country and use case.
**Note**  
If you want to request a short code for a different country, or for a separate use case in the same country, open a separate case in the Support Center Console. By creating separate cases, all communications for a particular country or use case are restricted to a single Support case, which reduces the potential for miscommunications.

1. Under **Case description**, for **Use case description**, provide details about your use case.

1. Choose **Next Step: Solve now or Contact us**. For **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**.

1. When you finish, choose **Submit**.

Support acknowledges your request within 24 hours of receipt. If we're able to provide you with a short code, we provide you with a short code registration form as an attachment to your Support case. Complete the registration form in its entirety. The information in this form is required in order to set up a short code with the mobile carriers. For more information about completing this form, see [Obtaining a short code for sending text messages to US recipients](https://aws.amazon.com/blogs/messaging-and-targeting/obtaining-a-short-code-for-sending-text-messages-to-us-recipients-part-1/) on the AWS Messaging and Targeting Blog. This blog post covers the process of applying for US short codes, but the information it provides is also useful when applying for short codes in other countries.

**Note**  
There is no Service Level Agreement for the time required to obtain a short code. The amount of time required depends on whether or not your use case is compliant with the requirements of the carriers. 

 There may be additional time in the request while our support teams work to ensure your application is compliant. Any provided estimated timelines would start once we have confirmation your application is in a state that can be submitted to carriers for review. If the carriers do not think that your use case is compliant, they will reject your application and provide information about the reasons for the rejection. If this happens, you will find this information in your Support case. You can address the issues with your application in your Support case. When you do, we send this updated information back to the carriers so that they can reconsider your application.

The fees associated with using short codes begin immediately after we initiate your short code request with carriers. You're responsible for paying these charges, even if the short code hasn't been completely provisioned yet. In order to prevent our systems from being used to send unsolicited or malicious content, we must consider each request carefully. We might not be able to grant your request if your use case doesn't align with our policies.

## Step 2: Update your SMS settings in the AWS End User Messaging SMS console


After we notify you that your short code has been provisioned, complete the following steps.

**Note**  
You can't complete this step until the short code request has been approved and the short code has been added to your AWS account.

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 **Phone number**.

1. On the **Phone number** page, choose the short code.

1. On the **Keywords** tab, verify that the responses for the *HELP* and *STOP* keywords match the values that you specified in your request.

# Requesting dedicated long codes
Requesting long codes

A long code (also referred to as a long virtual number, or LVN) is a standard phone number that contains up to 12 digits, depending on the country that it's based in. Long codes are typically meant for low-volume, person-to-person communication. In some countries, you can use long codes for sending test messages, or for sending low volumes of messages to your customers. In other countries, including the United States, senders are prohibited from using long codes to send Application-to-Person (A2P) messages, which includes the messages that you send from AWS End User Messaging SMS.

**Note**  
If you're new to SMS messaging with AWS End User Messaging SMS, you should also request a monthly SMS and MMS spending threshold that meets the expected demands of your SMS and MMS use case. By default, your monthly spending threshold is \$11.00 (USD). For more information, see [Requesting an SMS, MMS, or voice spending quota change for AWS End User Messaging SMS](awssupport-spend-threshold.md).

## Requesting a long code


You can request a long code for the below countries through the End User Messaging console. If you require a long code in a country not included in the below list you can request a long code by opening a case in the AWS Support by following the below process.

Countries support through console and APIs:
+ Australia (AU)
+ Austria (AT)
+ Chile (CL)
+ Denmark (DK)
+ Finland (FI)
+ Hong Kong (HK)
+ Hungary (HU)
+ Italy (IT)
+ Netherlands (NL)
+ Norway (NO)
+ Poland (PL)
+ Portugal (PT)
+ Spain (ES)
+ Sweden (SE)
+ United Kingdom (GB)

**Important**  
To send messages to recipients in the United States or the US territories of Puerto Rico, US Virgin Islands, Guam and American Samoa, you must use either a short code, a 10DLC phone number, or a toll-free number. If you complete the following steps and request a long code for the United States or US territories of Puerto Rico, US Virgin Islands, Guam and American Samoa, your request will be rejected.

**To request a dedicated long code by opening a case in the AWS Support Center**

1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase).

1. On the **Create Case** page, complete the following:
   + Select **Account and Billing**.
   + For **Service**, choose **Service Quotas**.
   + For **Category** choose either **AWS End User Messaging SMS (Pinpoint)** or **AWS End User Messaging Voice (Pinpoint)**, depending on your request.
   + For **Severity**, choose **General Limits**.

1. Under **Requests**, complete the following sections:
   + For the **Region**, choose the AWS Region from which you will be sending messages. 
**Note**  
The Region is required in the **Requests** section. Even if you provided this information in the **Case details** section you must also include it here.
   + For **Resource Type**, choose** Dedicated SMS Long Codes**.
   + For **Quota**, choose the type of messages that you plan to send using your long code.
   + For **New quota value**, enter the number of long codes that you want to purchase.

1. Under **Case description**, for **Use case description**, provide details about your use case.

1. (Optional) If you want to submit any further requests, choose **Add another request**. 

1. Choose **Next Step: Solve now or Contact us**. For **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**.

1. When you finish, choose **Submit**.

After we receive your request, we provide an initial response within 24 hours. We might contact you to request additional information. Once approved, you can add keywords and response messages to your long code. 

If we're able to provide you with a long code, we send you information about the costs associated with obtaining it. We also provide an estimate of the amount of time that's required to provision the long code. In many countries, we can provide you with a dedicated long code within 24 hours. However, in some countries and regions, it can take several weeks to obtain a dedicated long code for the SMS channel.

In order to prevent our systems from being used to send unsolicited or malicious content, we must consider each request carefully. We might not be able to grant your request if your use case doesn't align with our policies.