Skip to content

Commit 533ddfa

Browse files
committed
edit pass: azure-communication-services-10dlc-articles
1 parent cf8e6d6 commit 533ddfa

File tree

2 files changed

+18
-18
lines changed

2 files changed

+18
-18
lines changed

articles/communication-services/concepts/sms/ten-digit-long-code-guidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: references_regions
1616

1717
# 10DLC registration guidelines
1818

19-
To send application-to-person (A2P) SMS messages by using 10-digit long code (10DLC), businesses must complete *brand registration* and *campaign registration*. Registering ensures compliance with carrier and CTIA (formerly called Cellular Telecommunications Industry Association) guidelines while enabling high-quality message delivery.
19+
To send application-to-person (A2P) SMS messages by using a 10-digit long code (10DLC), businesses must complete *brand registration* and *campaign registration*. Registering ensures compliance with carrier and CTIA (formerly called Cellular Telecommunications Industry Association) guidelines while enabling high-quality message delivery.
2020

2121
This article describes how to complete the required fields for brand registration and campaign registration. You need to complete brand registration and receive approval first. Then you can continue with campaign registration.
2222

@@ -40,7 +40,7 @@ Approval for brand registration with TCR typically takes two to three business d
4040
| Field name | Description | Example |
4141
| --- | --- | --- |
4242
| **Brand Name** | Official name of your organization | **Contoso Inc.** |
43-
| **EIN/Tax ID** | Employer identification number or Tax ID (required for non-Sole Proprietor entities) | **12-3456789** |
43+
| **EIN/Tax ID** | Employer identification number or tax ID (required for non-Sole Proprietor entities) | **12-3456789** |
4444
| **Business Type** | Type of brand, such as sole proprietor, LLC, or corporation | **Corporation** |
4545
| **Website** | Website URL associated with your business (used for verification) | `https://www.contoso.com` |
4646
| **Vertical** | Industry in which your business operates | **E-commerce** |

articles/communication-services/quickstarts/sms/apply-for-ten-digit-long-code.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Begin your brand registration by filling in the details on the **Application Typ
5959
On the **Company Details** tab, provide details about your company:
6060

6161
- **Company Name**: Enter your registered business name.
62-
- **DBA or Brand Name, if different**: Enter your Doing Business As (DBA) or brand name, if it's different from your registered business name.
62+
- **DBA or Brand Name, if different**: Enter your *doing business as* (DBA) or brand name, if it's different from your registered business name.
6363
- **Website**: Enter a website URL that represents your business.
6464
- **Type of legal form**: Select the legal structure of your company (such as **Private Company**).
6565
- **EIN issuing country/region**: Select the country or region where your employer identification number (EIN) was issued.
@@ -71,7 +71,7 @@ On the **Company Details** tab, provide details about your company:
7171
- **City**: Enter the city of the business location.
7272
- **State or province**: Select the state or province of the business location.
7373
- **Zip code or postal code**: Enter the ZIP Code or postal code for the business location.
74-
- **Country/Region**: Select the country where the business is located.
74+
- **Country/Region**: Select the country or region where the business is located.
7575
- **Stock symbol**: Enter the stock symbol, if it's publicly listed.
7676
- **Stock exchange**: Select the name of the stock exchange where your business is listed, if applicable.
7777
- **Vertical Type**: Select the business category (such as **Education** or **Finance**).
@@ -124,8 +124,8 @@ On the **Campaign details** tab, enter these values:
124124

125125
- Brand name
126126
- Types of messages that the consumer can expect to receive
127-
- Message frequency disclosure (for example, "Msg frequency varies")
128-
- Message and data rates disclosure (for example, "Msg & data rates may apply")
127+
- Disclosure of message frequency (for example, "Msg frequency varies")
128+
- Disclosure of message and data rates (for example, "Msg & data rates may apply")
129129
- Opt-in information, as described in the following table
130130
- Help information (for example, "send HELP for help")
131131
- Opt-out information (for example, "send STOP to unsubscribe")
@@ -139,16 +139,16 @@ On the **Campaign details** tab, enter these values:
139139
| Text message keyword | Users opt in by texting a keyword (for example, **START**) to a specific number. | Explain how users learn about the keyword, such as a webpage link or a screenshot. | "By texting START to [phone number], you consent to receive text messages from [Brand Name]. Msg & data rates may apply. Msg frequency varies. Unsubscribe by replying STOP. Reply HELP for help. Phone numbers won't be shared with third parties. Privacy Policy [link] & Terms [link]." |
140140
| Verbal | Users opt in verbally at a physical location or over the phone. | Provide a copy of the script that informs users about the opt-in. | "[Brand name] collects opt-in verbally at their locations or over the phone. Customers provide their number and are informed that 'Message and data rates may apply', 'Message frequency varies', and they can 'text HELP for support or STOP to unsubscribe.' Phone numbers won't be shared with third parties. Privacy Policy [link] & Terms [link]." |
141141

142-
- **Privacy Policy URL**: Provide a link to your brand's privacy policy related to SMS. The URL can be a webpage or an online file that's publicly accessible.
142+
- **Privacy policy URL**: Provide a link to your brand's privacy policy related to SMS. The URL can be a webpage or an online file that's publicly accessible.
143143

144144
- **Terms and conditions URL**: Provide a link to your brand's terms and conditions related to SMS. The URL can be a webpage or an online file that's publicly accessible.
145145

146-
The terms and conditions must have an SMS disclosure that includes the types of messages that consumers can expect to receive, texting cadence, message and data rates notices, privacy policy links, help information, and opt-out instructions. The terms and conditions must include at least the following information:
146+
The terms and conditions must have an SMS disclosure that includes at least the following information:
147147

148148
- Brand name
149149
- Types of messages the consumer can expect to receive
150-
- Message frequency disclosure (for example, "Msg frequency varies")
151-
- Message and data rates disclosure (for example, "Msg & data rates may apply")
150+
- Disclosure of message frequency (for example, "Msg frequency varies")
151+
- Disclosure of message and data rates (for example, "Msg & data rates may apply")
152152
- Support contact information (for example, "send HELP for support," "contact `[email protected]` for support")
153153
- Opt-out information (for example, "Send STOP to unsubscribe")
154154

@@ -161,7 +161,7 @@ SMS senders in the United States are required to include a link to reference ter
161161
If your company doesn't have a privacy statement related to SMS messaging, you can use the following Microsoft-provided template and complete it with your company's information. This template includes relevant SMS terms and placeholders where you can insert links to your general terms and conditions, privacy policy, and help information.
162162

163163
> [!NOTE]
164-
> This template is for informational purposes only. It isn't intended as, and should not be substituted for, consultation with appropriate legal counsel and/or your organization's regulatory compliance team. This template is applicable only to approved uses of SMS from Azure Communication Services. Appropriate terms might vary depending on how you use this service and the nature of your business. We recommend that you seek legal counsel to ensure compliance with all applicable regulatory and legal obligations.
164+
> This template is for informational purposes only. It isn't intended as, and shouldn't be a substitute for, consultation with appropriate legal counsel and/or your organization's regulatory compliance team. This template is applicable only to approved uses of SMS from Azure Communication Services. Appropriate terms might vary depending on how you use this service and the nature of your business. We recommend that you seek legal counsel to ensure compliance with all applicable regulatory and legal obligations.
165165
166166
```
167167
TEMPLATE: SMS Terms of use
@@ -214,7 +214,7 @@ If your company doesn't have a privacy statement related to SMS messaging, you c
214214
On the **Use case** tab, enter the following information:
215215

216216
- **Content Type**: Select the type of content that you intend to send (such as **Marketing** or **Customer Care**).
217-
- **Sub-content Type**: Choose a more specific content category if applicable.
217+
- **Sub-content Type**: Choose a more specific content category, if applicable.
218218
- **Sample messages**: Provide sample messages that align with the campaign's use case. You can add multiple sample messages, if necessary, by selecting **Add sample message**. Sample messages must include the following information:
219219

220220
- Brand name
@@ -231,14 +231,14 @@ On the upper part of the **Campaign and content attributes** tab, fill in the fo
231231
- **Subscriber opt-in message**: If you selected **Yes** for **Subscriber opt-in**, enter the message for subscribers to receive when they opt in to the campaign. This message must include the following information:
232232

233233
- Brand name
234-
- Message frequency disclosure (for example, "Msg frequency varies")
235-
- Message and data rates disclosure (for example, "Msg & data rates may apply")
234+
- Disclosure of message frequency (for example, "Msg frequency varies")
235+
- Disclosure of message and data rates (for example, "Msg & data rates may apply")
236236
- Help information (for example, "send HELP for help")
237237
- Opt-out information (for example, "send STOP to unsubscribe")
238238

239239
An example might look like this:
240240

241-
*Thank you for opting in to receive [type of messages] from [Brand Name]. Msg frequency varies. Msg & data rates may apply. Reply HELP for help. Reply STOP to opt out from receiving messages from this number. Send START to resume a conversation.*
241+
"Thank you for opting in to receive [type of messages] from [Brand Name]. Msg frequency varies. Msg & data rates may apply. Reply HELP for help. Reply STOP to opt out from receiving messages from this number. Send START to resume a conversation."
242242
- **Subscriber opt-out**: Select **Yes** or **No** to indicate if subscribers can opt out.
243243
- **Subscriber opt-out message**: If you selected **Yes** for **Subscriber opt-out**, enter the response message for subscribers to receive when they opt out. This message must include the following information:
244244

@@ -247,7 +247,7 @@ On the upper part of the **Campaign and content attributes** tab, fill in the fo
247247

248248
An example might look like this:
249249

250-
*You have successfully opted out of messages from this [Brand Name] number. You'll receive no further messages. Reply START to resume. Msg & data rates may apply.*
250+
"You have successfully opted out of messages from this [Brand Name] number. You'll receive no further messages. Reply START to resume. Msg & data rates may apply."
251251
- **Subscriber help**: Select **Yes** or **No** to indicate if subscriber help is available.
252252
- **Subscriber help answer**: If you selected **Yes** for **Subscriber help**, provide the message for subscribers who seek assistance. The help message must include the following information:
253253

@@ -256,7 +256,7 @@ On the upper part of the **Campaign and content attributes** tab, fill in the fo
256256

257257
An example might look like this:
258258

259-
*Thank you for contacting [Brand Name] support. Please email us at [email address] for support. Reply STOP to opt-out from receiving messages from this number. Msg & data rates may apply.*
259+
"Thank you for contacting [Brand Name] support. Please email us at [email address] for support. Reply STOP to opt-out from receiving messages from this number. Msg & data rates may apply."
260260

261261
> [!NOTE]
262262
> Make opt-in, opt-out, and help messages clear and compliant. Only the keywords **START**, **HELP**, and **STOP**, **QUIT**, **END**, **REVOKE**, **OPT OUT**, **CANCEL**, and **UNSUBSCRIBE** are monitored and enforced.
@@ -266,7 +266,7 @@ On the upper part of the **Campaign and content attributes** tab, fill in the fo
266266
On the lower part of the **Campaign and content attributes** tab, fill in these attributes:
267267

268268
- **Direct lending or Loan arrangement**: Select **Yes** or **No** to indicate if the campaign involves any lending or loan arrangements.
269-
- **Embedded link**: Select **Yes** or **No** to indicate if embedded links are sent in messages. Public URL shorteners (Bitly and TinyURL) aren't accepted. If you select **Yes**, at least one sample message must include an embedded link.
269+
- **Embedded link**: Select **Yes** or **No** to indicate if embedded links are sent in messages. Public URL shorteners (for example, Bitly and TinyURL) aren't accepted. If you select **Yes**, at least one sample message must include an embedded link.
270270
- **Embedded phone number**: Select **Yes** or **No** to indicate if embedded phone numbers are sent in messages, excluding the help contact. If you select **Yes**, at least one sample message must include an embedded phone number.
271271
- **Age-gated content**: Select **Yes** or **No** to indicate if the content is age-restricted.
272272
- **Terms and conditions**: Affiliate marketing isn't permitted on 10DLC numbers. Select the checkbox to confirm that you won't use the campaign for affiliate marketing.

0 commit comments

Comments
 (0)