Skip to content

Commit b8ba482

Browse files
committed
Fix blocking issues
Fixed Acrolinx problems and other small text edits.
1 parent 884f9df commit b8ba482

File tree

5 files changed

+37
-35
lines changed

5 files changed

+37
-35
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ SMS operational logs contain information to help identify trends and patterns, r
4242
* Messages sent.
4343
* Message received.
4444
* Messages delivered.
45-
* Messages opt-in & opt-out.
45+
* Messages opt in & opt out.
4646

4747
## Resource log categories
4848

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ SMS offers pay-as-you-go pricing. The price is a per-message segment* charge bas
6262

6363
### Carrier surcharges
6464

65-
A carrier surcharge applies to messages exchanged using 10DLC numbers. This surcharge is a per-message segment fee that might vary over time. For outbound messages, the carrier of the recipient's number determines the surcharge. For inbound messages, it's determined by the carrier of the sender's number. See the SMS FAQ [Carrier fees](../sms/sms-faq.md#carrier-fees).
65+
A carrier surcharge applies to messages exchanged using 10DLC numbers. This surcharge is a per-message segment fee that might vary over time. For outbound messages, the carrier of the recipient's number determines the surcharge. For inbound messages, the surcharge is determined by the carrier of the sender's number. See the SMS FAQ [Carrier fees](../sms/sms-faq.md#carrier-fees).
6666

6767
| Carrier | Frequency | Fee |
6868
|--------------------|---------------------------------------|--------|
@@ -75,4 +75,6 @@ A carrier surcharge applies to messages exchanged using 10DLC numbers. This surc
7575
| C-Spire (Outbound) | per message segment | $0 |
7676
| Commnet (Outbound) | per message segment | $0 |
7777

78-
*See our guide on [SMS character limits](../sms/sms-faq.md#what-is-the-sms-character-limit) to learn more about message segments.
78+
## Related articles
79+
80+
- For more information about message segments, see [SMS character limits](../sms/sms-faq.md#what-is-the-sms-character-limit).

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

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,13 @@ Consent can be obtained in various ways, such as:
4444

4545
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.
4646

47-
### Consent requirements:
47+
### Consent requirements
4848

49-
- 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.
49+
- 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.
5050
- Consent isn't transferable or assignable. Any consent that an individual provides to you can't 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.
5151
- 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 send recurring messages or messages from an affiliate.
5252

53-
### Consent best practices:
53+
### Consent best practices
5454

5555
In addition to the messaging requirements previously discussed, you may want to implement several common best practices, including:
5656

@@ -107,39 +107,39 @@ None of these messages may include solicitations or advertisements.
107107

108108
Message recipients may revoke consent and opt-out of receiving future messages through any reasonable means. You may not designate an exclusive means for message recipients to revoke consent.
109109

110-
### Opt-out requirements:
110+
### Opt-out requirements
111111

112-
Ensure that message recipients can opt-out of future messages at any time. You must also offer multiple opt-out options. After a message recipient opts out, don't send any new messages unless the individual provides renewed consent.
112+
Ensure that message recipients can opt out of future messages at any time. You must also offer multiple opt-out options. After a message recipient opts out, don't send any new messages unless the individual provides renewed consent.
113113

114114
One of the most common opt-out mechanisms in SMS applications is to include a “STOP” keyword in the initial message of every new conversation. Be prepared to remove customers that reply with a lowercase “stop” or other common keywords, such as “unsubscribe” or “cancel.”
115115

116116
For email, embed a link to unsubscribe in every email sent to the customer. If the customer selects the unsubscribe link, remove that customer email addresses from your communication list.
117117

118118
After an individual revokes consent, you should remove them from all recurring messaging campaigns unless they expressly elect to continue receiving messages from a particular program.
119119

120-
### Opt-out best practices:
120+
### Opt-out best practices
121121

122122
In addition to keywords, other common opt-out mechanisms include providing customers with a designated opt-out e-mail address, the phone number of customer support staff, or a link to unsubscribe embedded in an email message you sent or available on your webpage.
123123

124124
### How we handle opt-out requests for SMS
125125

126126
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 is automatically stopped. However, you must still ensure that you don't send any new messages for that messaging campaign from new or different numbers.
127127

128-
If you 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're 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).
128+
If you 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're 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).
129129

130130
### How we handle opt-out requests for email
131131

132132
If an individual requests to opt-out of future messages on Azure Communication Services using the unsubscribe UI page to process the unsubscribe requests, you need to add the requested recipient's email address to the suppression list used to filter recipients during the send-mail process.
133133

134134
## Message content
135135

136-
### Adult content:
136+
### Adult content
137137

138138
Message content that includes elements of sex, hate, alcohol, firearms, tobacco, gambling, or sweepstakes and contests can trigger more 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.
139139

140140
Even where such content legal, you should include an age verification mechanism at opt-in to age-gate the intended message recipient from adult content. In the United States, more legal requirements apply to marketing communications directed at children under the age of 13.
141141

142-
### Prohibited practices:
142+
### Prohibited practices
143143

144144
Both you and your customers are prohibited from using Azure Communication Services to evade reasonable opt-out requests. Additionally, you and your customers may not evade any measures implemented by Azure Communication Services or a communications service provider to ensure your compliance with messaging requirements and industry standards.
145145

@@ -162,12 +162,12 @@ Spoofing is the act of causing a misleading or inaccurate originating number or
162162

163163
## Final thoughts
164164

165-
### Legal Responsibility:
165+
### Legal Responsibility
166166

167167
This Messaging Policy doesn't constitute legal advice, and we reserve the right to modify the policy at any time. Azure Communication Services isn't responsible for ensuring that the content, timing, or recipients of our customers’ messages meet all applicable legal requirements.
168168

169169
Our customers are responsible for all messaging requirements. If you're a platform or software provider that uses Azure Communication Services for messaging purposes, then you should require that your customers also abide by all of the requirements discussed in this Messaging Policy. For further guidance, the CTIA's [Messaging Principles and Best Practices](https://api.ctia.org/wp-content/uploads/2019/07/190719-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf) provides a helpful overview of the relevant industry standards.
170170

171-
### Penalties:
171+
### Penalties
172172

173173
We encourage our customers to develop and implement policies and procedures designed to ensure compliance with all messaging requirements. Violations of messaging requirements may lead to substantial fines that can balloon quickly. It's in your best interest to learn and abide by all applicable messaging requirements and develop effective mitigation safeguards to contain and eliminate violations before they spread. If you do breach our Messaging Policy or other legal requirements, then we'll work with you to ensure future compliance. However, we reserve the right to remove any customer from the Azure Communication Services platform who demonstrates a pattern of noncompliance with our Messaging Policy or legal requirements.

articles/communication-services/concepts/sms/program-brief-guidelines.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Example: 234567, 234578, 234589.
6060
6161
### Directionality
6262

63-
This field captures the directionality of the SMS program – 1-way or 2-way SMS. In the United States, 2-way SMS is mandated to honor opt-out requests from customers.
63+
This field captures the directionality of the SMS program – 1-way or 2-way SMS. In the United States, two-way SMS is mandated to honor opt-out requests from customers.
6464

6565
### Recurrence
6666

@@ -86,8 +86,8 @@ Your terms of service must include terms specific to the short code program brie
8686
- Program Name and Description.
8787
- Message Frequency can either be listed as Message Frequency Varies or the accurate frequency. Message Frequency also needs to match the value listed in the call-to-action.
8888
- The disclaimer: "Message and data rates may apply" written verbatim.
89-
- Customer care information, for example: "For help call \[phone number\] or send an email to \[email\]".
90-
- Opt-Out message: "Text STOP to cancel".
89+
- Customer care information, for example: "For help call \[phone number\] or send an email to \[email\]."
90+
- Opt-Out message: "Text STOP to cancel."
9191
- A link to the Privacy Policy or the whole Privacy policy.
9292

9393
##### Example:
@@ -100,12 +100,12 @@ Your terms of service must contain ALL of the following information:
100100
- Program Name and Description.
101101
- Message Frequency can be either listed as Message Frequency Varies or the accurate frequency. Message Frequency also needs to match the value listed in the CTA (Call-To-Action).
102102
- The disclaimer: "Message and data rates may apply" written verbatim.
103-
- Customer care information, for example: "For help call \[phone number\] or send an email to \[email\]".
104-
- Opt-Out message: "Text STOP to cancel".
103+
- Customer care information, for example: "For help call \[phone number\] or send an email to \[email\]."
104+
- Opt-Out message: "Text STOP to cancel."
105105
- A link to the Privacy Policy or the whole Privacy policy.
106106

107107
> [!Note]
108-
> If you don’t have a URL of the website, mockups, or design, please send an email with the screenshots to [[email protected]](mailto:[email protected]) with "\[CompanyName - ProgramName\] Short Code Request".
108+
> If you don’t have a URL of the website, mockups, or design, please send an email with the screenshots to [[email protected]](mailto:[email protected]) with "\[CompanyName - ProgramName\] Short Code Request."
109109
110110
### Program Sign-up type and URL
111111

@@ -135,11 +135,11 @@ In these fields, you must provide a URL of the website where customers discover
135135

136136
**SMS**
137137

138-
Contoso.com: Announcing our Holiday Sale. Reply YES to save 5% on your next Contoso purchase. Msg&Data Rates May Apply. Txt HELP or terms&conditions. Txt STOP to opt-out.
138+
Contoso.com: Announcing our Holiday Sale. Reply YES to save 5% on your next Contoso purchase. Msg&Data Rates May Apply. Txt HELP or terms&conditions. Txt STOP to opt out.
139139

140140
**Web opt-in**
141141

142-
:::image type="content" source= "../media/short-code-web-optin.png" alt-text="Screen capture of the the web opt-in mock up.":::
142+
:::image type="content" source= "../media/short-code-web-optin.png" alt-text="Screen capture of the web opt-in mock up.":::
143143

144144
**Point of sale (hardcopy leaflet) with SMS keyword call-to-action**
145145

@@ -149,7 +149,7 @@ Contoso.com: Announcing our Holiday Sale. Reply YES to save 5% on your next Cont
149149

150150
*Example 1:*
151151

152-
**Agent** - To sign up for our last-minute travel deals, Press 1. Message and data rates may apply. Visit margiestravel.com for privacy and terms and conditions.
152+
**Agent** - To sign up for our last-minute travel deals, Press 1. Message and data rates may apply. Visit margiestravel.com for privacy and terms and conditions.
153153

154154
*Example 2:*
155155

@@ -166,7 +166,7 @@ You need to provide information about your company and point of contact. Status
166166

167167
Customer care contact information must be clear and readily available to help customers understand program details and their status with the program. Customer care information should result in customers receiving help.
168168

169-
In these fields, you're required to provide the customer care email address and a customer care phone number where customers can reach out to receive help.
169+
In these fields, you must provide the customer care email address and a customer care phone number where customers can reach out to receive help.
170170

171171
## Volume
172172

@@ -176,15 +176,15 @@ In this field, you need to provide an approximate number of messages sent out pe
176176

177177
### Replies per user
178178

179-
In this field, you must to provide an approximate number of replies you expect to get per customer.
179+
In this field, you must provide an approximate number of replies you expect to get per customer.
180180

181181
### Expected total messages sent
182182

183-
In this field, you're required to provide an estimate of total messages sent per month.
183+
In this field, you must provide an estimate of total messages sent per month.
184184

185185
### Traffic spikes
186186

187-
In this field, you're required to provide information on traffic spikes and their expected timing.
187+
In this field, you need to provide information on traffic spikes and their expected timing.
188188
Example: Traffic spikes are expected for delivery notifications program around holidays like Christmas.
189189

190190
## Templates
@@ -195,33 +195,33 @@ Azure communication service offers an opt-out management service for short codes
195195

196196
CTIA requires that the customer must actively opt into short code programs by sending a keyword from their mobile device to the short code, providing consent on website, IVR, and so on.
197197

198-
In this field, you're required to provide a sample of the confirmation message that is sent to the customer upon receiving their consent.
198+
In this field, you must provide a sample of the confirmation message that is sent to the customer upon receiving their consent.
199199

200200
**Example:** Contoso Promo Alerts: Three msgs/week. Msg&Data Rates May Apply. Reply HELP for help. Reply STOP to opt out.
201201

202202
### Help message response
203203

204204
Message senders are required to respond to messages containing the HELP keyword with the program name and further information about how to contact the message sender.
205205

206-
In this field, you're required to provide a sample of the response message that is sent to the customer upon receiving the HELP keyword.
206+
In this field, you must provide a sample of the response message that is sent to the customer upon receiving the HELP keyword.
207207

208208
**Example:** Contoso Appointment reminders: Get help at [email protected] or 1-800 123 4567.Msg&Data Rates May Apply. Txt HELP for help. Txt STOP to opt out.
209209

210210
### Opt-out message
211211

212212
Message senders are required to have mechanisms for customers to opt out of the program. You need to respond to customer messages containing the STOP keyword with the program name and confirmation that they won't receive any more messages.
213213

214-
In this field, you're required to provide a sample of the response message that is sent to the customer upon receiving the STOP keyword.
214+
In this field, you must provide a sample of the response message that is sent to the customer upon receiving the STOP keyword.
215215

216216
**Example:** Contoso Appointment reminders: You’re opted out and won't receive any more messages.
217217

218218
See our [guide on opt-outs](./sms-faq.md#opt-out-handling) to learn about how Azure Communication Services handles opt-outs.
219219

220220
### Example messages
221221

222-
Message senders are required to disclose all the types/categories of messages with samples that will be sent over the short code.
222+
Message senders are required to disclose all the types/categories of messages with samples that they plan to send over the short code.
223223

224-
In this field, you're required to provide a sample message for each content type you intend on using the short code for.
224+
In this field, you must provide a sample message for each content type you intend on using the short code for.
225225

226226
#### Example flow:
227227
- **Contoso**: Contoso: Your reservation is confirmed for 30th February 2022. Txt R to reschedule. Txt HELP or STOP. Msg&Data rates may apply.

0 commit comments

Comments
 (0)