Merge pull request #232546 from Prakulka/master

AlphaSenderID docs

Author: Stacyrch140

articles/communication-services/concepts/includes/sms-alphanumeric-sender-id-pricing.md

@@ -0,0 +1,47 @@
+---
+title: Alphanumeric sender ID SMS pricing includes file
+description: include file
+services: azure-communication-services
+author: prakulka
+manager: sundraman
+
+ms.service: azure-communication-services
+ms.subservice: azure-communication-services
+ms.date: 03/28/2023
+ms.topic: include
+ms.custom: Include file
+ms.author: prakulka
+---
+
+The Alphanumeric sender ID service requires enabling alphanumeric sender ID through the Azure portal. Once the alphanumeric sender ID service is enabled, pay-as-you-go pricing applies to the usage fee. The usage fee is determined by the destination of the message.
+
+##  Alphanumeric sender ID  Pricing
+
+### Usage Fee
+SMS offers pay-as-you-go pricing. The price is a per-message segment charge based on the destination of the message. Messages can be sent from an alphanumeric sender ID to phone numbers located within the destinations mentioned below. 
+
+The following prices are exclusive of the required communications taxes and fees:
+
+|Country| Send Message |
+|-----------|---------|
+|Australia| $0.049 | 
+|Austria| $0.0932 | 
+|Denmark| $0.0499 | 
+|Estonia | $0.0845 |
+|France | $0.076 |
+|Germany | $0.0895 | 
+|Ireland| $0.07 | 
+|Italy | $0.0833 | 
+|Lithuania| $0.041 |
+|Latvia | $0.065 | 
+|Netherlands| $0.092 | 
+|Poland | $0.041 | 
+|Portugal | $0.045 | 
+|Spain| $0.0833 | 
+|Sweden| $0.055 | 
+|Switzerland | $0.069 | 
+|United Kingdom | $0.04 |
+
+*See our guide on [SMS character limits](../sms/sms-faq.md#what-is-the-sms-character-limit) to learn more about message segments.
+
+

articles/communication-services/concepts/includes/sms-shortcode-pricing.md

@@ -44,7 +44,7 @@ Fees for short code leasing are charged after provisioning is complete and then
 ### Usage Fee
 SMS offers pay-as-you-go pricing. The price is a per-message segment charge based on the destination of the message. Messages can be sent from a short code to phone numbers located within the United States. 
 
-The following prices include required communications taxes and fees:
+The following prices are exclusive of the required communications taxes and fees:
 
 |Message Type   |Usage Fee |
 |-----------|------------|

articles/communication-services/concepts/includes/sms-tollfree-pricing.md

@@ -31,7 +31,7 @@ Fees for toll-free leasing are charged after provisioning and then recur on a mo
 ### Usage Fee
 SMS offers pay-as-you-go pricing. The price is a per-message segment* charge based on the destination of the message. Messages can be sent by toll-free phone numbers to phone numbers located within the United States, Canada, and Puerto Rico.
 
-The following prices include required communications taxes and fees:
+The following prices are exclusive of the required communications taxes and fees:
 
 |Country| Send Message | Receive Message|
 |-----------|---------|--------------|

articles/communication-services/concepts/numbers/sub-eligibility-number-capability.md

@@ -7,13 +7,10 @@ ms.author: prakulka
 ms.date: 11/30/2021
 ms.topic: conceptual
 ms.service: azure-communication-services
-zone_pivot_groups: acs-tollfree-shortcode
+zone_pivot_groups: acs-tollfree-shortcode-alphanumeric
 ---
 # SMS Pricing 
 
-> [!IMPORTANT]
-> SMS messages can be sent to and received from United States and Canada phone numbers. Phone numbers located in other geographies are not yet supported by Communication Services SMS.
-
 ::: zone pivot="tollfree"
 [!INCLUDE [Toll-Free](./includes/sms-tollfree-pricing.md)]
 ::: zone-end
@@ -22,9 +19,14 @@ zone_pivot_groups: acs-tollfree-shortcode
 [!INCLUDE [Short Code](./includes/sms-shortcode-pricing.md)]
 ::: zone-end
 
+::: zone pivot="alphanumeric-senderid"
+[!INCLUDE [Alphanumeric Sender ID](./includes/sms-alphanumeric-sender-id-pricing.md)]
+::: zone-end
+
 ## Next steps
 
-In this quickstart, you learned how to send SMS messages using Azure Communication Services.
+> [!div class="nextstepaction"]
+> [Learn more about SMS pricing calculation](../concepts/pricing.md)
 
 > [!div class="nextstepaction"]
 > [Learn more about SMS](../concepts/sms/concepts.md)

articles/communication-services/concepts/sms-pricing.md

@@ -13,21 +13,40 @@ ms.service: azure-communication-services
 ms.subservice: sms
 ---
 
-# SMS concepts
+# SMS overview
 
 [!INCLUDE [Regional Availability Notice](../../includes/regional-availability-include.md)]
 
 Azure Communication Services enables you to send and receive SMS text messages using the Communication Services SMS SDKs. These SDKs can be used to support customer service scenarios, appointment reminders, two-factor authentication, and other real-time communication needs. Communication Services SMS allows you to reliably send messages while exposing deliverability and response metrics.
 
+## SMS features
+
 Key features of Azure Communication Services SMS SDKs include:
 
 -  **Simple** setup experience for adding SMS capability to your applications.
 - **High Velocity** message support over toll free numbers and short codes for A2P (Application to Person) use cases in the United States.
 - **Bulk Messaging** supported to enable sending messages to multiple recipients at a time.
 - **Two-way** conversations to support scenarios like customer support, alerts, and appointment reminders.
 - **Reliable Delivery** with real-time delivery reports for messages sent from your application.
-- **Analytics** to track your SMS usage patterns.
-- **Opt-Out** handling support to automatically detect and respect opt-outs for toll-free numbers. Opt-outs for US toll-free numbers are mandated and enforced by US carriers.
+- **Analytics** to track your SMS usage patterns. See [SMS insights](../../concepts/analytics/insights/sms-insights.md) for details.
+- **Opt-Out** handling support to automatically detect and respect opt-outs for toll-free numbers and short codes. Opt-outs for US toll-free numbers are mandated and enforced by US carriers. See [opt-out handling FAQ](./sms-faq.md#opt-out-handling) for details.
+
+## Sender types supported
+
+Sending SMS to any recipient requires getting a phone number. Choosing the right number type is critical to the success of your messaging campaign. Few of the factors to consider when choosing a number type include destination(s) of the message, throughput requirement of your messaging campaign, and the timeline when you want to start sending messages. Azure Communication Services enables you to send SMS using a variety of sender types - toll-free number (1-8XX), short codes (12345), and alphanumeric sender ID (CONTOSO). The following table walks you through the features of each number type:
+
+|Factors              | Toll-Free| Short Code | Alphanumeric Sender ID|
+|---------------------|----------|------------|-----------------------|
+|**Description**|Toll free numbers are telephone numbers with distinct three-digit codes that can be used for business to consumer communication without any charge to the consumer| Short codes are 5-6 digit numbers used for business to consumer messaging such as alerts, notifications, and marketing | Alphanumeric Sender IDs are displayed as a custom alphanumeric phrase like the company’s name (CONTOSO, MyCompany) on the recipient handset. Alphanumeric sender IDs can be used for a variety of use cases like one-time passcodes, marketing alerts, and flight status notifications.    |
+|**Format**|+1 (8XX) XYZ PQRS| 12345  | CONTOSO*       |
+|**SMS support**|Two-way SMS| Two-way SMS  | One-way outbound SMS  |
+|**Calling support**|Yes| No | No |
+|**Provisioning time**| 5-6 weeks| 6-8 weeks  | Instant               |
+|**Throughput**       | 200 messages/min (can be increased upon request)| 6000 messages/ min (can be increased upon request) | 600 messages/ min (can be increased upon request)|
+|**Supported Destinations**| United States, Canada, Puerto Rico| United States   |  Germany, Netherlands, United Kingdom, Australia, France, Switzerland, Sweden, Italy, Spain, Denmark, Ireland, Portugal, Poland, Austria, Lithuania, Latvia, Estonia |
+|**Get started**|[Get a toll-free number](../../quickstarts/telephony/get-phone-number.md)|[Get a short code](../../quickstarts/sms/apply-for-short-code.md) | [Enable alphanumeric sender ID](../../quickstarts/sms/enable-alphanumeric-sender-id.md) |
+
+\* See [Alphanumeric sender ID FAQ](./sms-faq.md#alphanumeric-sender-id) for detailed formatting requirements.
 
 ## Next steps
 

articles/communication-services/concepts/sms/concepts.md

@@ -44,10 +44,9 @@ Consent can be obtained in a variety of ways, such as:
 
 Regardless of how consent is obtained, you and your customers must ensure that the consent is unambiguous. The scope of the consent should clear to the recipient.
 
-
 ### Consent requirements:
 
-- Provide a “Call to Action” before obtaining consent. You and your customers should provide potential message recipients with a “call to action” that invites them to opt-in to your messaging program. The call to action should include, at a minimum: (1) the identity of the message sender, (2) clear opt-in instructions, (3) opt-out instructions, and (4) any associated messaging fees.
+- Provide a “Call to Action” before obtaining consent. You and your customers should provide potential message recipients with a “call to action” that invites them to opt in to your messaging program. The call to action should include, at a minimum: (1) the identity of the message sender, (2) clear opt-in instructions, (3) opt-out instructions, and (4) any associated messaging fees.
 - Consent isn't transferable or assignable. Any consent that an individual provides to you cannot be transferred or sold to an unaffiliated third party. If you collect an individual’s consent for a third party, then you must clearly identify the third party to the individual. You must also state that the consent you obtained applies only to communications from the third party.
 - Consent is limited in purpose. An individual who provides their number or an email address for a particular purpose consents to receive communications only for that specific purpose and from that specific message sender. Before obtaining consent, you should clearly notify the intended message recipient if you'll send recurring messages or messages from an affiliate.
 
@@ -67,7 +66,6 @@ In addition to the messaging requirements discussed above, you may want to imple
   - The session ID or IP address of the consenting individual.
 - Privacy and security policies. Developers are encouraged to provide straightforward privacy policies that message recipients can review before their consent is obtained. We also recommend maintaining proactive security controls to safeguard individuals’ private information.
 
-
 ## Double opt-In consent:
 
 Azure Communication Services recommends that you use double opt-in consent for all messaging campaigns. Double opt-in consent is a two-step process where an individual first provides consent to receive certain types of messages from you. You then send a follow-up opt-in message to confirm their consent. You should send more messages only once the message recipient confirms their consent.
@@ -116,7 +114,7 @@ In addition to keywords, other common opt-out mechanisms include providing custo
 
 ### How we handle opt-out requests for SMS
 
-If an individual requests to opt-out of future messages on an Azure Communication Services toll-free number, then all further traffic from that number will be automatically stopped. However, you must still ensure that you do not send additional messages for that messaging campaign from new or different numbers. If you have separately obtained express consent for a different messaging campaign, then you may continue to send messages from a different number for that campaign. Check out our FAQ section to learn more on [Opt-out handling](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/communication-services/concepts/sms/sms-faq.md#how-can-i-receive-messages-using-azure-communication-services)
+If an individual requests to opt-out of future messages on an Azure Communication Services toll-free number or short code, then all further traffic from that number will be automatically stopped. However, you must still ensure that you do not send additional messages for that messaging campaign from new or different numbers. If you have separately obtained express consent for a different messaging campaign, then you must ask the customer to respond with a START message to resubscribe or may continue to send messages from a different number for that campaign. For alphanumeric sender ID, you are required to provide alternative mechanisms like email/call support or opt-out link for the customer to opt out. Check out our FAQ section to learn more on [Opt-out handling](./sms-faq.md#opt-out-handling).
 
 ### How we handle opt-out requests for email
 
@@ -128,7 +126,7 @@ If an individual requests to opt out of future messages on Azure Communication S
 
 Message content that includes elements of sex, hate, alcohol, firearms, tobacco, gambling, or sweepstakes and contests can trigger additional requirements. This content is expressly prohibited in some jurisdictions. If you send a message that includes this content, then it is your duty to abide by all applicable laws of the jurisdictions in which the communications are received. At the request of law enforcement or Azure Communication Services, you must be prepared to provide proof of consent with local laws that regulate adult content.
 
-Even where such content is not unlawful, you should include an age verification mechanism at opt-in to age-gate the intended message recipient from adult content. In the United States, additional legal requirements apply to marketing communications directed at children under the age of 13. 
+Even where such content is not unlawful, you should include an age verification mechanism at opt in to age-gate the intended message recipient from adult content. In the United States, additional legal requirements apply to marketing communications directed at children under the age of 13. 
 
 ### Prohibited practices: