You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/sms/ten-digit-long-code-guidelines.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Ten digit long code (10DLC) registration guidelines
3
-
titleSuffix: An Azure Communication Services concept document
3
+
titleSuffix: An Azure Communication Services article
4
4
description: This article describes how to prepare for 10 digit long code (10DLC) brand registration and campaign registration.
5
5
author: prakulka
6
6
manager: darmour
@@ -16,7 +16,7 @@ ms.custom: references_regions
16
16
17
17
# Ten digit long code (10DLC) registration guidelines
18
18
19
-
To send Application-to-Person (A2P) SMS messages using 10 digit long codes (10DLC), businesses must complete **brand registration** and **campaign registration**. This ensures compliance with carrier and CTIA guidelines while enabling high-quality message delivery.
19
+
To send Application-to-Person (A2P) SMS messages using 10 digit long codes (10DLC), businesses must complete **brand registration** and **campaign registration**. Registering ensures compliance with carrier and Cellular Telecommunications Industry Association (CTIA) guidelines while enabling high-quality message delivery.
20
20
21
21
This article describes how to complete the required fields for **brand registration** and **campaign registration**.
22
22
@@ -44,7 +44,7 @@ Brand registration typically takes 2 to 3 business days with TCR (The Campaign R
44
44
|**Brand Name**| Official name of your organization. | Contoso Inc. |
45
45
|**EIN / Tax ID**| Employer Identification Number or Tax ID (required for non-Sole Proprietor entities). | 12-3456789 |
46
46
|**Business Type**| Select the appropriate business type (Sole Proprietor, LLC, Corporation, and so on). | Corporation |
47
-
|**Website**| Website URL associated with your business (used for verification). |https://www.contoso.com|
47
+
|**Website**| Website URL associated with your business (used for verification). |`https://www.contoso.com`|
48
48
|**Vertical**| Industry in which your business operates. | E-commerce |
49
49
|**Email Address**| Contact email for registration-related updates. |[email protected]|
50
50
@@ -56,7 +56,7 @@ Brand registration typically takes 2 to 3 business days with TCR (The Campaign R
56
56
57
57
## Campaign registration
58
58
59
-
Campaign registration enables you to specify the purpose of your messaging (such as marketing, customer service, or two-factor authentication) and how you plan to use 10DLC numbers. This step ensures that your use case complies with regulations and that carriers can properly route and filter messages based on the campaign type.
59
+
Campaign registration enables you to specify the purpose of your messaging (such as marketing, customer service, or two-factor authentication) and how you plan to use 10DLC numbers. This step ensures that your use case complies with regulations so carriers can properly route and filter messages based on the campaign type.
60
60
61
61
Campaign details must accurately reflect the content and intent of your messages. Providing false or misleading information could lead to rejections or delays in the approval of your campaign.
62
62
@@ -72,10 +72,10 @@ Campaign registration with TCR typically takes 3 to 5 business days for approval
72
72
|**Campaign Name**| Name identifying your campaign. | Contoso Marketing Campaign |
73
73
|**Campaign Description**| A detailed description of the campaign’s purpose. | Send promotional offers and updates to customers who opt in to Contoso's SMS notifications. |
74
74
|**Use Case**| The primary purpose of the campaign (such as marketing or customer care). | Marketing |
75
-
|**Message Samples**| Provide examples of the messages your campaign will send. | “Hello! Thank you for subscribing to Contoso updates. Reply STOP to opt out.” |
76
-
|**Subscriber Opt-in**| Confirms that recipients have explicitly consented to receive messages. | “Thank you for subscribing to Contoso Alerts. Reply HELP for help, STOP to unsubscribe.” |
75
+
|**Message Samples**| Provide examples of the messages your campaign plans to send. | “Hello! Thank you for subscribing to Contoso updates. Reply STOP to opt out.” |
76
+
|**Subscriber Opt-in**| Confirms that recipients explicitly consent to receive messages. | “Thank you for subscribing to Contoso Alerts. Reply HELP for help, STOP to unsubscribe.” |
77
77
|**Subscriber Opt-out**| Allows recipients to stop receiving messages at any time. | “You have unsubscribed from Contoso Alerts. Reply START to resubscribe.” |
78
-
|**Subscriber Help**| Provides instructions or assistance to users. | “For assistance, visit [www.contoso.com](https://www.contoso.com) or call 1-800-CONTOSO.” |
78
+
|**Subscriber Help**| Provides instructions or assistance to users. | “For assistance, visit `https://www.contoso.com` or call 1-800-CONTOSO.” |
79
79
|**Embedded Links**| Indicates if messages include URLs. | Yes |
80
80
|**Embedded Phone Numbers**| Indicates if messages include phone numbers. | Yes |
81
81
|**Age-gated Content**| Indicates if messages are age-restricted. | No |
@@ -84,7 +84,7 @@ Campaign registration with TCR typically takes 3 to 5 business days for approval
84
84
85
85
1. When is brand vetting required?
86
86
87
-
Brand vetting for 10DLC messaging is typically required for companies outside the Russell 3000 list as these companies are considered as pre-vetted. Smaller businesses, companies without EIN, unverified brands may require brand vetting.
87
+
Brand vetting for 10DLC messaging is typically required for companies outside the Russell 3000 list as these companies are considered as prevetted. Smaller businesses, companies without EIN, unverified brands may require brand vetting.
88
88
89
89
2. What happens when a brand is rejected during the 10DLC registration process?
90
90
@@ -95,7 +95,7 @@ Brand vetting for 10DLC messaging is typically required for companies outside th
95
95
96
96
3. How are registration fees charged?
97
97
98
-
All fees for registration, including vetting fees, are charged at the time of submission and are non-refundable regardless of approval status.
98
+
All fees for registration, including vetting fees, are charged at the time of submission and are nonrefundable regardless of approval status.
# Sign an HTTP request using hash-based message authentication code (HMAC)
19
19
20
-
In this tutorial, you learn how to sign an HTTP request with a hash-based message authentication code (HMAC) signature.
20
+
This article describes how to sign an HTTP request with a hash-based message authentication code (HMAC) signature.
21
21
22
22
> [!NOTE]
23
-
> We strongly encourage you to use [Azure SDKs](https://github.com/Azure/azure-sdk). The approach described here is a fallback option for cases when Azure SDKs can't be used for any reason.
23
+
> We recommend using the [Azure SDKs](https://github.com/Azure/azure-sdk) to sign an HTTP request. The approach described in this article is a fallback option if Azure SDKs can't be used for any reason.
- Create an Azure account with an active subscription. If you don't have an Azure subscription, see [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
- Create an Azure Communication Services resource. If you don't have a resource, see [Create a Communication Services resource](../../quickstarts/create-communication-resource.md). You need to record your `resourceEndpoint` and `resourceAccessKey` parameters for this tutorial.
@@ -36,7 +34,7 @@ The `hmac-sha256-signature` consists of:
36
34
37
35
## Set up the authorization header
38
36
39
-
The following steps describe how to construct the authorization header.
37
+
Complete the following steps to construct the authorization header.
40
38
41
39
### Create a new C# application
42
40
@@ -46,7 +44,7 @@ In a console window, such as cmd, PowerShell, or Bash, use the `dotnet new` comm
46
44
dotnet new console -o SignHmacTutorial
47
45
```
48
46
49
-
Change your directory to the newly created app folder. Use the `dotnet build` command to compile your application.
47
+
Change your directory to the newly created app folder. To compile your application, use the `dotnet build` command.
- Create an Azure account with an active subscription. If you don't have an Azure subscription, see [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
18
16
- Download and install [Python](https://www.python.org/).
19
17
- Download and install [Visual Studio Code](https://code.visualstudio.com/) or another integrated development environment (IDE) that supports Python.
20
-
- Create an Azure Communication Services resource. If you don't have a resource, see [Create a Communication Services resource](../../quickstarts/create-communication-resource.md). You need your `resource_endpoint_name` and `resource_endpoint_secret` parameters for this tutorial.
18
+
- Create an Azure Communication Services resource. If you don't have a resource, see [Create a Communication Services resource](../../quickstarts/create-communication-resource.md). You need your `resource_endpoint_name` and `resource_endpoint_secret` parameters for this example.
21
19
22
20
## Sign an HTTP request with Python
23
21
@@ -37,7 +35,7 @@ The `hmac-sha256-signature` consists of:
37
35
38
36
## Set up the authorization header
39
37
40
-
The following steps describe how to construct the authorization header.
38
+
Complete following steps to construct the authorization header.
0 commit comments