Skip to content

Commit 1d31800

Browse files
authored
Acrolinx improvements
1 parent cf273df commit 1d31800

File tree

1 file changed

+26
-26
lines changed
  • articles/communication-services/concepts/sms

1 file changed

+26
-26
lines changed

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

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -24,27 +24,27 @@ Azure Communication Services customers can use Azure Event Grid to receive incom
2424

2525
### Can I receive messages from any country/region on toll-free numbers?
2626

27-
Toll-free numbers are not capable of sending or receiving messages to/from countries/regions outside of US, CA, and PR.
27+
Toll-free numbers aren't capable of sending or receiving messages to/from countries/regions outside of US, CA, and PR.
2828

2929
### Can I receive messages from any country/region on short codes?
30-
Short codes are domestic numbers and are not capable of sending or receiving messages to/from outside of the country/region it was registered for. *Example: US short code can only send and receive messages to/from US recipients.*
30+
Short codes are domestic numbers and aren't capable of sending or receiving messages to/from outside of the country/region it was registered for. *Example: US short code can only send and receive messages to/from US recipients.*
3131

3232
### How are messages sent to landline numbers treated?
3333

34-
In the United States, Azure Communication Services does not check for landline numbers and attempts to send it to carriers for delivery. Customers are charged for messages sent to landline numbers.
34+
In the United States, Azure Communication Services doesn't check for landline numbers and attempts to send it to carriers for delivery. Customers are charged for messages sent to landline numbers.
3535

3636
### Can I send messages to multiple recipients?
3737

3838
Yes, you can make one request with multiple recipients. Follow this [quickstart](../../quickstarts/sms/send.md?pivots=programming-language-csharp) to send messages to multiple recipients.
3939

4040
### I received an HTTP Status 202 from the Send SMS API but the SMS didn't reach my phone, what do I do now?
4141

42-
The 202 returned by the service means that your message has been queued to be sent and not delivered. Use this [quickstart](../../quickstarts/sms/handle-sms-events.md) to subscribe to delivery report events and troubleshoot. Once the events are configured, inspect the "deliveryStatus" field of your delivery report to verify delivery success/failure.
42+
The 202 returned by the service means that your message was queued to be sent and not delivered. Use this [quickstart](../../quickstarts/sms/handle-sms-events.md) to subscribe to delivery report events and troubleshoot. Once the events are configured, inspect the "deliveryStatus" field of your delivery report to verify delivery success/failure.
4343

4444
### How to send shortened URLs in messages?
45-
Shortened URLs are a good way to keep messages short and readable. However, US carriers prohibit the use of free publicly available URL shortener services. This is because the ‘free-public’ URL shorteners are used by bad-actors to evade detection and get their SPAM messages passed through text messaging platforms. When sending messages in US, we encourage using custom URL shorteners to create URLs with dedicated domain that belongs to your brand. Many US carriers block SMS traffic if they contain publicly available URL shorteners.
45+
Shortened URLs are a good way to keep messages short and readable. However, US carriers prohibit the use of free publicly available URL shortener services. This is because the ‘free-public’ URL shorteners are used by bad-actors to evade detection and get their SPAM messages passed through text messaging platforms. When sending messages in the US, we encourage using custom URL shorteners to create URLs with dedicated domain that belongs to your brand. Many US carriers block SMS traffic if they contain publicly available URL shorteners.
4646

47-
Below is a list with examples of common URL shorteners you should avoid to maximize deliverability:
47+
Following is a list with examples of common URL shorteners you should avoid to maximize deliverability:
4848
- bit.ly
4949
- goo.gl
5050
- tinyurl.com
@@ -60,14 +60,14 @@ Below is a list with examples of common URL shorteners you should avoid to maxim
6060
## Opt-out handling
6161
### How does Azure Communication Services handle opt-outs for toll-free numbers?
6262

63-
Opt-outs for US toll-free numbers are mandated and enforced by US carriers and cannot be overridden.
63+
Opt-outs for US toll-free numbers are mandated and enforced by US carriers and can't be overridden.
6464
- **STOP** - If a text message recipient wishes to opt out, they can send ‘STOP’ to the toll-free number. The carrier sends the following default response for STOP: *"NETWORK MSG: You replied with the word "stop", which blocks all texts sent from this number. Text back "unstop" to receive messages again."*
6565
- **START/UNSTOP** - If the recipient wishes to resubscribe to text messages from a toll-free number, they can send ‘START’ or ‘UNSTOP’ to the toll-free number. The carrier sends the following default response for START/UNSTOP: *“NETWORK MSG: You have replied “unstop” and will begin receiving messages again from this number.”*
66-
- Azure Communication Services detects STOP messages and blocks all further messages to the recipient. The delivery report will indicate a failed delivery with status message as “Sender blocked for given recipient.”
67-
- The STOP, UNSTOP and START messages will be relayed back to you. Azure Communication Services encourages you to monitor and implement these opt-outs to ensure that no further message send attempts are made to recipients who have opted out of your communications.
66+
- Azure Communication Services detects STOP messages and blocks all further messages to the recipient. The delivery report indicates a failed delivery with the status message as “Sender blocked for given recipient.”
67+
- The STOP, UNSTOP, and START messages are relayed back to you. Azure Communication Services encourages you to monitor and implement these opt-outs to ensure that no further message-send attempts are made to recipients who opted out of your communications.
6868

6969
### How does Azure Communication Services handle opt-outs for short codes in United States?
70-
Azure communication service offers an opt-out management service for short codes in US that allows customers to configure responses to mandatory keywords STOP/START/HELP. Prior to provisioning your short code, you are asked for your preference to manage opt-outs. If you opt-in, the opt-out management service automatically uses your responses in the program brief for Opt in/ Opt out/ Help keywords in response to STOP/START/HELP keyword.
70+
Azure communication service offers an opt-out management service for short codes in US that allows customers to configure responses to mandatory keywords STOP/START/HELP. Before you provision your short code, you're asked for your preference to manage opt-outs. If you opt in, the opt-out management service automatically uses your responses in the program brief for Opt in/ Opt out/ Help keywords in response to STOP/START/HELP keyword.
7171

7272
*Example:*
7373
- **STOP** - If a text message recipient wishes to opt out, they can send ‘STOP’ to the short code. Azure Communication Services sends your configured response for STOP: *"Contoso Alerts: You’re opted out and will receive no further messages."*
@@ -78,24 +78,24 @@ Azure Communication Services detects STOP messages and blocks all further messag
7878

7979
### How does Azure Communication Services handle opt outs for alphanumeric sender ID?
8080

81-
Alphanumeric sender ID is not capable of receiving inbound messages or STOP messages. Azure Communication Services does not enforce or manage opt-out lists for alphanumeric sender ID. You must provide customers with instructions to opt out using other channels such as, calling support, providing an opt-out link in the message, or emailing support. See [messaging policy guidelines](./messaging-policy.md#how-we-handle-opt-out-requests-for-sms) for further details.
81+
Alphanumeric sender ID isn't capable of receiving inbound messages or STOP messages. Azure Communication Services doesn't enforce or manage opt-out lists for alphanumeric sender ID. You must provide customers with instructions to opt out using other channels such as, calling support, providing an opt-out link in the message, or emailing support. See [messaging policy guidelines](./messaging-policy.md#how-we-handle-opt-out-requests-for-sms) for further details.
8282

8383
### How does Azure Communication Services handle opt outs for short codes in Canada and United Kingdom?
8484

85-
Azure Communication Services does not control or implement opt-out mechanisms for short codes within Canada and the United Kingdom. Recipients of text messages have the option to text ‘STOP’ to unsubscribe or ‘START’ to subscribe to the short code. These requests are relayed as incoming messages to your event grid. It is your responsibility to act on these messages by resubscribing recipients or ceasing message delivery accordingly.
85+
Azure Communication Services doesn't control or implement opt-out mechanisms for short codes within Canada and the United Kingdom. Recipients of text messages have the option to text ‘STOP’ to unsubscribe or ‘START’ to subscribe to the short code. These requests are relayed as incoming messages to your event grid. It is your responsibility to act on these messages by resubscribing recipients or ceasing message delivery accordingly.
8686

8787
## Short codes
8888
### What is the eligibility to apply for a short code?
89-
Short Code availability is currently restricted to paid Azure subscriptions that have a billing address in the United States. Short Codes cannot be acquired on trial accounts or using Azure free credits. For more details, check out our [subscription eligibility page](../numbers/sub-eligibility-number-capability.md).
89+
Short Code availability is currently restricted to paid Azure subscriptions that have a billing address in the United States. Short Codes can't be acquired on trial accounts or using Azure free credits. For more details, check out our [subscription eligibility page](../numbers/sub-eligibility-number-capability.md).
9090

9191
### Can you text to a toll-free number from a short code?
92-
Azure Communication Services toll-free numbers are enabled to receive messages from short codes. However, short codes are not typically enabled to send messages to toll-free numbers. If your messages from short codes to Azure Communication Services toll-free numbers are failing, check with your short code provider if the short code is enabled to send messages to toll-free numbers.
92+
Azure Communication Services toll-free numbers are enabled to receive messages from short codes. However, short codes aren't typically enabled to send messages to toll-free numbers. If your messages from short codes to Azure Communication Services toll-free numbers are failing, check with your short code provider if the short code is enabled to send messages to toll-free numbers.
9393

9494
### How should a short code be formatted?
95-
Short codes do not fall under E.164 formatting guidelines and do not have a country code, or a "+" sign prefix. In the SMS API request, your short code should be passed as the 5-6 digit number you see in your short codes page without any prefix.
95+
Short codes don't fall under E.164 formatting guidelines and don't have a country code, or a "+" sign prefix. In the SMS API request, your short code should be passed as the 5-6 digit number you see in your short codes page without any prefix.
9696

9797
### How long does it take to get a short code? What happens after a short code program brief application is submitted?
98-
Once you have submitted the short code program brief application in the Azure portal, the service desk works with the aggregators to get your application approved by each wireless carrier. This process generally takes 8-12 weeks. All updates and the status changes for your applications are communicated via the email you provide in the application. For more questions about your submitted application, please email [email protected].
98+
After you submit the short code program brief application in the Azure portal, the service desk works with the aggregators to get your application approved by each wireless carrier. This process generally takes 8-12 weeks. All updates and the status changes for your applications are communicated via the email you provide in the application. For more questions about your submitted application, email [email protected].
9999

100100
## Alphanumeric sender ID
101101

@@ -113,13 +113,13 @@ Once you have submitted the short code program brief application in the Azure po
113113
- Spaces
114114

115115
### Is a number purchase required to use alphanumeric sender ID?
116-
The use of alphanumeric sender ID does not require purchase of any phone number. Alphanumeric sender ID can be enabled through the Azure portal. See [enable alphanumeric sender ID quickstart](../../quickstarts/sms/enable-alphanumeric-sender-id.md) for instructions.
116+
The use of alphanumeric sender ID doesn't require purchase of any phone number. Alphanumeric sender ID can be enabled through the Azure portal. See [enable alphanumeric sender ID quickstart](../../quickstarts/sms/enable-alphanumeric-sender-id.md) for instructions.
117117

118118
### Can I send SMS immediately after enabling alphanumeric sender ID?
119119
We recommend waiting for 10 minutes before you start sending messages for best results.
120120

121121
### Why is my alphanumeric sender ID getting replaced by a number?
122-
Alphanumeric sender ID replacement with a number may occur when a certain wireless carrier does not support alphanumeric sender ID. This is done to ensure high delivery rate.
122+
Alphanumeric sender ID replacement with a number may occur when a certain wireless carrier doesn't support alphanumeric sender ID. This is done to ensure high delivery rate.
123123

124124
## Toll-Free Verification
125125

@@ -156,24 +156,24 @@ New limits are as follows:
156156
157157
### What happens after I submit the toll-free verification form?
158158

159-
After submission of the form, we will coordinate with our downstream peer to get the application verified by the toll-free messaging aggregator. While we are reviewing your application, we may reach out to you for more information.
159+
After submission of the form, we'll coordinate with our downstream peer to get the application verified by the toll-free messaging aggregator. While we are reviewing your application, we may reach out to you for more information.
160160
- From Application Submitted to Pending = **1-5 business days**
161161
- From Pending to Verdict (Verfied/Rejected/More info needed) = **4-5 weeks**. The toll-free aggregator is currently facing a high volume of applications due to which applications can take around eight weeks to get approved.
162162

163163
The whole toll-free verification process takes about **5-6 weeks**. These timelines are subject to change depending on the volume of applications to the toll-free messaging aggregator and the [quality](#what-is-considered-a-high-quality-toll-free-verification-application) of your application. The toll-free aggregator is currently facing a high volume of applications due to which applications can take around eight weeks to get approved.
164164

165-
Updates for changes and the status of your applications will be communicated via the regulatory blade in Azure portal.
165+
Updates for changes and the status of your applications are communicated via the regulatory blade in Azure portal.
166166

167167
### How do I submit a toll-free verification?
168168
To submit a toll-free verification application, navigate to Azure Communication Service resource that your toll-free number is associated with in Azure portal and navigate to the Phone numbers blade. Select on the Toll-Free verification application link displayed as "Submit Application" in the infobox at the top of the phone numbers blade. Complete the form.
169169

170170
### What is considered a high quality toll-free verification application?
171171
The better the quality of your application, the greater the likelihood of it being approved.
172172

173-
Pointers to ensure you are submitting a high quality application:
173+
Pointers to ensure you're submitting a high-quality application:
174174
- Phone number(s) listed is/are Toll-free number(s)
175175
- All required fields completed
176-
- The use case is not listed on our [Ineligible Use Case](#what-are-the-ineligible-use-cases-for-toll-free-verification) list
176+
- The use case isn't listed on our [Ineligible Use Case](#what-are-the-ineligible-use-cases-for-toll-free-verification) list
177177
- Opt-in process is documented/detailed
178178
- Opt-in image URL is provided and publicly accessible
179179
- [CTIA guidelines](https://www.ctia.org/the-wireless-industry/industry-commitments/messaging-interoperability-sms-mms) are being followed
@@ -207,7 +207,7 @@ This table shows the maximum number of characters that can be sent per SMS segme
207207
|Hello world|Text|GSM Standard|GSM-7|160|
208208
|你好|Unicode|Unicode|UCS-2|70|
209209

210-
### Can I send/receive long messages (>2048 chars)?
210+
### Can I send/receive long messages (>2,048 chars)?
211211

212212
Azure Communication Services supports sending and receiving of long messages over SMS. However, some wireless carriers or devices may act differently when receiving long messages. We recommend keeping SMS messages to a length of 320 characters and reducing the use of accents to ensure maximum delivery.
213213

@@ -229,12 +229,12 @@ Rate Limits for SMS:
229229

230230
## Carrier Fees
231231
### What are the carrier fees for SMS?
232-
US and CA carriers charge an added fee for SMS messages sent and/or received from toll-free numbers and short codes. The carrier surcharge is calculated based on the destination of the message for sent messages and based on the sender of the message for received messages. Azure Communication Services charges a standard carrier fee per message segment. Carrier fees are subject to change by mobile carriers. Refer to [SMS pricing](../sms-pricing.md) for more details.
232+
US and CA carriers charge an added fee for SMS messages sent and/or received from toll-free numbers and short codes. The carrier surcharge is calculated based on the destination of the message for sent messages and based on the sender of the message for received messages. Azure Communication Services charges a standard carrier fee per message segment. Carrier fees are subject to change by mobile carriers. For more information, see [SMS pricing](../sms-pricing.md).
233233

234234
### When do we come to know of changes to these surcharges?
235-
As with similar Azure services, customers are notified at least 30 days prior to the implementation of any price changes. These charges are reflected on our SMS pricing page along with the effective dates.
235+
As with similar Azure services, customers are notified at least 30 days before the implementation of any price changes. These charges are reflected on our SMS pricing page along with the effective dates.
236236

237237
## Emergency support
238238
### Can a customer use Azure Communication Services for emergency purposes?
239239

240-
Azure Communication Services does not support text-to-911 functionality in the United States, but it’s possible that you may have an obligation to do so under the rules of the Federal Communications Commission (FCC). You should assess whether the FCC’s text-to-911 rules apply to your service or application. To the extent you're covered by these rules, you are responsible for routing 911 text messages to emergency call centers that request them. You're free to determine your own text-to-911 delivery model, but one approach accepted by the FCC involves automatically launching the native dialer on the user’s mobile device to deliver 911 texts through the underlying mobile carrier.
240+
Azure Communication Services doesn't support text-to-911 functionality in the United States, but it’s possible that you may have an obligation to do so under the rules of the Federal Communications Commission (FCC). You should assess whether the FCC’s text-to-911 rules apply to your service or application. To the extent you're covered by these rules, you're responsible for routing 911 text messages to emergency call centers that request them. You're free to determine your own text-to-911 delivery model, but one approach accepted by the FCC involves automatically launching the native dialer on the user’s mobile device to deliver 911 texts through the underlying mobile carrier.

0 commit comments

Comments
 (0)