Skip to content

Commit 26cfd97

Browse files
authored
pencil edits
- Lines 49, 72, 75, 76, 84: opt in > opt-in - Line 105: opt out > opt-out
1 parent eb45acd commit 26cfd97

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Regardless of how consent is obtained, you and your customers must ensure that t
4646

4747
### 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 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.
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'll send recurring messages or messages from an affiliate.
5252

@@ -68,20 +68,20 @@ In addition to the messaging requirements discussed above, you may want to imple
6868

6969
## Double opt-In consent:
7070

71-
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.
71+
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.
7272

7373
The initial confirmation message that you send should include your identity, the option to opt-out of future messages (such as the use of a “STOP” command), a toll-free number or “HELP” command for additional information, notification that the individual is enrolled in a recurring message program, a brief description of the program, the frequency with which you intend to send recurring messages, and any associated fees.
7474

75-
### Does Azure Communication Services ever require double opt in consent?
76-
Yes, while double opt in consent is always recommended, Azure Communication Services requires that you use double opt in consent for some types of messaging campaigns due to their frequent use in phishing schemes or their tendency to result in consumer complaints. These campaigns include:
75+
### Does Azure Communication Services ever require double opt-in consent?
76+
Yes, while double opt-in consent is always recommended, Azure Communication Services requires that you use double opt-in consent for some types of messaging campaigns due to their frequent use in phishing schemes or their tendency to result in consumer complaints. These campaigns include:
7777
- Auto-warranty messages
7878
- Short-term health insurance plans
7979
- Debt refinancing or interest rate reduction messages if not made by a financial institution
8080
- Lead generation messages
8181
- Sweepstakes, contests, and giveaways
8282
- Work-from-home offers
8383

84-
The campaigns for which double opt in consent is required are subject to change at the discretion of Azure Communication Services.
84+
The campaigns for which double opt-in consent is required are subject to change at the discretion of Azure Communication Services.
8585

8686
### Exceptions to traditional consent rules:
8787
While prior express consent is normally required before sending a message, there are two situations in which consent to message an individual is implied.
@@ -102,7 +102,7 @@ Message recipients may revoke consent and opt-out of receiving future messages t
102102

103103
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, you should not send additional messages unless the individual provides renewed consent.
104104

105-
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.”
105+
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.”
106106

107107
For email, it is to embed a link to unsubscribe in every email sent to the customer. If the customer selects the unsubscribe link, you should be prepared to remove that customer email address(es) from your communication list.
108108

0 commit comments

Comments
 (0)