Manage sender IDs - Amazon Pinpoint SMS

Manage sender IDs

Before you request a sender ID verify that they are available, see Supported countries and regions for SMS messaging.

Note

Some countries require you to register your sender ID or open a support case to request the sender ID.

  • India sender ID registration – Register a sender ID for use in India. For more information on completing the registration for see India sender ID registration process.

  • Singapore sender ID registration – Register a sender ID in Singapore. For more information on completing the registration for see Singapore registration form.

  • Request a Sender ID from AWS Support Senders are required to use a pre-registered alphabetic sender ID. To request a Sender ID from AWS Support, Open an Amazon Pinpoint SMS support case to request a sender ID. Some countries require senders to meet specific requirements or abide by certain restrictions in order to obtain approval. In these cases, AWS Support might contact you for additional information after you submit your sender ID request. For a list of countries that require a support ticket to request a sender ID, see the Supports Sender IDs column in Supported countries and regions for SMS messaging.

Request a sender ID (Console)

To request a sender ID using the Amazon Pinpoint SMS console, follow these steps:

Request a sender ID
  1. Open the Amazon Pinpoint SMS console at https://console.aws.amazon.com/sms-voice/.

  2. In the navigation pane, under Configurations, choose Sender ID and then Request originator.

  3. On the Select country page you must choose the country from the dropdown that messages will be sent to.

    Choose Next to continue defining the use case and for a suggested phone number or sender ID type.

  4. On the Messaging use case section, enter the following:

    • Under Number capabilities, choose either SMS, Voice or both depending on your requirements.

      • SMS – Choose if you need SMS capabilities.

      • Voice (text to audio) – Choose if you need voice capabilities.

  5. Under Estimated monthly SMS message volume per month – optional, choose the estimated number of SMS messages you will send each month.

  6. For Company headquarters - optional, choose either of the following:

    • Local – Choose this if your companies 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 companies headquarters is not in the same country as your customers who will revive SMS messages.

  7. Choose Next.

  8. Under Originator type, choose Sender ID.

    If sender ID isn't available then choose Previous to go back and modify your use case. Also check the Supported countries and regions for SMS messaging to sender IDs are supported in the destination country.

    In the Sender ID field enter a sender ID. The sender ID must be 1-11 alphanumeric characters including letters (A-Z), numbers (0-9), or hyphens (-). The sender ID must begin with a letter.

  9. Choose Next.

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

  11. A Registration Required window might appear depending on the type of number you requested. For more information about registrations requirements see Registrations.

    1. For Registration form name enter a name.

    2. Choose Complete registration to finish registering the sender ID or Register later.

      Important

      You are still billed the recurring monthly lease fee regardless of registration status.

Release a sender ID (Console)

If you don't need a sender ID anymore, you can remove it from your account. When you remove a sender ID, we stop charging you for it in your bill for the next calendar month.

Release a sender ID
  1. Open the Amazon Pinpoint SMS console at https://console.aws.amazon.com/sms-voice/.

  2. In the navigation pane, under Configurations, choose Sender Ids.

  3. Choose the sender ID that you want to release and then choose delete.

  4. On the Release Sender ID dialog enter release and choose Release sender ID.

Open an Amazon Pinpoint SMS support case to request a sender ID

If you plan to send messages to recipients a country where sender IDs are required, you can request a sender ID by creating a new case in the AWS Support Center.

Important
To request a sender ID
  1. Open the Support Center Console at https://console.aws.amazon.com/support/home.

  2. On the Your support cases pane, choose Create case.

  3. Choose the Looking for service limit increases? link, then complete the following:

    • For Service, choose Pinpoint SMS.

    • (Optional) For Provide a link to the site or app which will be sending SMS messages, provide information about the website, application, or service that will send SMS messages.

    • (Optional) For What type of messages do you plan to send, choose the type of message that you plan to send using your long code:

      • One Time Password – Messages that provide passwords that your customers use to authenticate with your website or application.

      • Promotional – 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.

    • (Optional) For Which AWS Region will you be sending messages from, choose the AWS Region that you will be sending messages from.

    • (Optional) For Which countries do you plan to send messages to, enter the country or region that you want to purchase short codes in.

    • (Optional) In the How do your customers opt to receive messages from you, provide details about your opt-in process.

    • (Optional) In the Please provide the message template that you plan to use to send messages to your customers field, include the template that you will be using.

  4. 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 Sender ID Registration.

    • For Quota, choose the type of messages that you plan to send.

    • For New quota value, enter the number of sender IDs that you're requesting. Typically, this value is 1.

  5. Under Case description, for Use case description, provide the following information:

    • The sender ID that you want to register.

    • The template that you plan to use for your SMS messages.

    • The number of messages that you plan to send to each recipient per month.

    • Information about how your customers opt in to receiving messages from you.

    • The name of your company or organization.

    • The address that's associated with your company or organization.

    • The country where your company or organization is based.

    • A phone number for your company or organization.

    • The URL of the website for your company or organization.

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

  7. Under Contact options, for Preferred contact language, choose the language that you prefer to use when communicating with the AWS Support team..

  8. 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.

If we're able to provide you with a Sender ID, we send you an estimate of the amount of time that's required to provision it. In many countries, we can provide you with a Sender ID within 2–4 weeks. However, in some countries, it can take several weeks to obtain a Sender ID.

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