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/sms-faq.md
+49-21Lines changed: 49 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ This article answers commonly asked questions about the SMS serv
19
19
## Sending and receiving messages
20
20
### How can I receive messages using Azure Communication Services?
21
21
22
-
Azure Communication Services customers can use Azure Event Grid to receive incoming messages. Follow this [quickstart](../../quickstarts/sms/handle-sms-events.md) to setup your event-grid to receive messages.
22
+
Azure Communication Services customers can use Azure Event Grid to receive incoming messages. Follow this [quickstart](../../quickstarts/sms/handle-sms-events.md) to set up your event-grid to receive messages.
23
23
24
24
### How are messages sent to landline numbers treated?
25
25
@@ -29,7 +29,7 @@ In the United States, Azure Communication Services does not check for landline n
29
29
30
30
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.
31
31
32
-
### I received a HTTP Status 202 from the Send SMS API but the SMS didn't reach my phone, what do I do now?
32
+
### I received an HTTP Status 202 from the Send SMS API but the SMS didn't reach my phone, what do I do now?
33
33
34
34
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.
35
35
@@ -53,7 +53,7 @@ Below is a list with examples of common URL shorteners you should avoid to maxim
53
53
### How does Azure Communication Services handle opt-outs for toll-free numbers?
54
54
55
55
Opt-outs for US toll-free numbers are mandated and enforced by US carriers and cannot be overridden.
56
-
-**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."*
56
+
-**STOP** - If a text message recipient wishes to optout, 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."*
57
57
-**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.”*
58
58
- Azure Communication Services will detect the STOP message and block all further messages to the recipient. The delivery report will indicate a failed delivery with status message as “Sender blocked for given recipient.”
59
59
- 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.
@@ -62,7 +62,7 @@ Opt-outs for US toll-free numbers are mandated and enforced by US carriers and c
62
62
Azure communication service offers an opt-out management service for short codes that allows customers to configure responses to mandatory keywords STOP/START/HELP. Prior to provisioning your short code, you will be asked for your preference to manage opt-outs. If you opt-in to use it, the opt-out management service will automatically use your responses in the program brief for Opt-in/ Opt-out/ Help keywords in response to STOP/START/HELP keyword.
63
63
64
64
*Example:*
65
-
-**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."*
65
+
-**STOP** - If a text message recipient wishes to optout, 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."*
66
66
-**START** - If the recipient wishes to resubscribe to text messages from a short code, they can send ‘START’ to the short code. Azure Communication Service sends your configured response for START: *“Contoso Promo Alerts: 3 msgs/week. Msg&Data Rates May Apply. Reply HELP for help. Reply STOP to opt-out.”*
67
67
-**HELP** - If the recipient wishes to get help with your service, they can send 'HELP' to the short code. Azure Communication Service sends the response you configured in the program brief for HELP: *"Thanks for texting Contoso! Call 1-800-800-8000 for support."*
68
68
@@ -85,44 +85,72 @@ Once you have submitted the short code program brief application in the Azure po
85
85
### What is toll free verification?
86
86
The toll-free verification process ensures that your services running on toll-free numbers (TFNs) comply with carrier policies and [industry best practices](./messaging-policy.md). This also provides relevant service information to the downstream carriers, reduces the likelihood of false positive filtering and wrongful spam blocks.
87
87
88
-
This verification is **required** for TFNs sending messages to **Canada recipients** and is **not required** for TFNs sending [low throughput messages](#sms-to-us-phone-numbers) to **US recipients**. Verifying TFNs is free of cost.
88
+
This verification is **required** for best SMS delivery experience.
89
89
90
90
### What happens if I don't verify my toll-free numbers?
91
91
What happens to the unverified toll-free number depends on the destination of SMS traffic.
92
92
#### SMS to US phone numbers
93
-
Effective **October 1, 2022**, unverified toll-free numbers sending messages to US phone numbers will be subjected to stricter filtering and the following thresholds for messaging:
93
+
Effective **October 1, 2022**, unverified toll-free numbers sending messages to US phone numbers will be subjected to the following:
94
94
95
+
1.**Stricter filtering** - SMS messages are more likely to get blocked due to strict filtering, preventing messages to be delivered (i.e., SMS messages with URLs might be blocked).
96
+
2.**SMS volume thresholds**:
95
97
-**Daily Limit:** 2,000 messages
96
98
-**Weekly limit:** 12,000 messages
97
99
-**Monthly limit:** 25,000 messages
98
100
99
-
This does not apply to TFNs in a pending or verified status.
101
+
This would not apply to TFNs in a [pending or verified status](#what-do-the-different-application-statuses-verified-pending-and-unverified-mean).
102
+
> [!IMPORTANT]
103
+
> Unverified SMS traffic that exceeds the daily limit or is filtered for spam will have a [4010 error code](../troubleshooting-info.md#sms-error-codes) returned for both scenarios.
104
+
>
105
+
> The unverified volume daily cap is a daily maximum limit (not a guaranteed daily minimum), so unverified traffic can still experience message filtering even when it’s well below the daily limits.
100
106
101
107
#### SMS to Canadian phone numbers
102
-
Effective **October 1, 2022**, unverified toll-free numbers sending messages to Canadian destinations will have its traffic **blocked**. To be unblocked, TFNs have to be in pending or verified status.
108
+
Effective **October 1, 2022**, unverified toll-free numbers sending messages to Canadian destinations will have its traffic **blocked**. To unblock the traffic, a verification application needs to be submitted and be in [pending or verified status](#what-do-the-different-application-statuses-verified-pending-and-unverified-mean).
103
109
104
-
### What is a pending status? What can I do in a pending status?
105
-
After submission of the toll-free verification application, we will process your application and send it to the toll-free messaging aggregator. This process usually takes in 4-6 business days. Once the application reaches the toll-free messaging aggregator the application status changes to pending until verified or rejected.
106
-
107
-
Once in pending state, you can start sending SMS to US numbers without the thresholds mentioned above and be unblocked from sending SMS to Canadian destinations. TFNs in pending state are subject to reduced likelihood of filtering.
110
+
### What do the different application statuses (verified, pending and unverified) mean?
111
+
-**Verified:** Verified numbers have gone through the toll-free verification process and have been approved. Their traffic is subjected to limited filters. If traffic does trigger any filters, that specific content will be blocked but the number will not be automatically blocked.
112
+
-**Pending**: Numbers in pending state have an associated toll-free verification form being reviewed by the toll-free messaging aggregator. They can send at a lower throughput than verified numbers, but higher than unverified numbers. Blocking can be applied to individual content or there can be an automatic block of all traffic from the number. These numbers will remain in this pending state until a decision has been made on verification status.
113
+
-**Unverified:** Unverified numbers have either 1) not submitted a verification application or 2) have had their application denied. These numbers are subject to the highest amount of filtering, and numbers in this state will automatically get shut off if any spam or unwanted traffic is detected.
108
114
109
115
### What happens after I submit the toll-free verification form?
110
-
Updates for changes and the status of your applications will be communicated via the email you provide in the application. Results from the application can be: approved, denied or further clarification needed. For more questions about your submitted application, please email [email protected].
116
+
:::image type="content" source="./media/tf-status-blue.png" alt-text="A picture of the toll-free application timeline and the different application statuses.":::
117
+
118
+
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.
119
+
- From Application Submitted to Pending = **1-5 business days**
120
+
- From Pending to Verdict (Verfied/Rejected/More info needed) = **4-5 weeks**
121
+
122
+
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.
111
123
112
-
The whole toll-free verification process takes about **5-6 weeks** but is subject to change depending on the volume of applications to the toll-free messaging aggregator and how detailed the application is.
124
+
Updates for changes and the status of your applications will be communicated via the email you provide in the application. For more questions about your submitted application, please email [email protected].
113
125
114
126
### How do I submit a toll-free verification?
115
127
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. Click 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.
116
128
129
+
### What is considered a high quality toll-free verification application?
130
+
The higher the quality of the application the higher chances your application will enter [pending state](#what-do-the-different-application-statuses-verified-pending-and-unverified-mean) faster.
131
+
132
+
Pointers to ensure you are submitting a high quality application:
Toll-free verification (TFV) involves an integration between Microsoft and the Toll-Free messaging aggregator. The toll-free messaging aggregator is the final reviewer and approver of the TFV application. Microsoft must share the TFV application information with the toll-free messaging aggregator for them to confirm that the program details meet the CTIA guidelines and standards set by carriers. By submitting a TFV form, you agree that Microsoft may share the TFV application details as necessary for provisioning the toll-free number.
119
-
120
-
### What are common reasons for toll-free verification delays?
121
-
Your application wait time increases when your application has missing or unclear information.
122
-
123
-
-**Missing required information like Opt-in Image URL** - If there is no Opt-in option, provide a good justification.
124
-
-**Opt-in Image URL is not accessible to the public** - When you host your image on image hosting services (i.e. OneDrive, GoogleDrive, iCloud, Dropbox, etc.) make sure the public can view it. Test the URL by seeing if the URL can be viewed by a personal account.
125
-
-**Incorrect toll-free numbers** - Phone numbers have to be toll-free numbers, not local numbers, 10DLC, or short codes.
0 commit comments