Skip to content

Commit d14ce45

Browse files
authored
Update concepts.md
1 parent 16947f5 commit d14ce45

File tree

1 file changed

+2
-0
lines changed
  • articles/communication-services/concepts/sms

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ Key features of Azure Communication Services SMS SDKs include:
3434
- **Analytics** to track your SMS usage patterns. See [SMS insights](../../concepts/analytics/insights/sms-insights.md) for details.
3535
- **Opt-Out** handling support to automatically detect and respect opt-outs for toll-free numbers and short codes. US carriers mandate and enforce opt-outs for US toll-free numbers. See [opt-out handling FAQ](./sms-faq.md#opt-out-handling) for details.
3636

37+
:::image type="content" source="./media/sms-concept.png" alt-text="Diagram showing sms dekkivery flow concept." lightbox="./media/sms-concept.png":::
38+
3739
## Sender types supported
3840

3941
To send SMS, you must have a sender ID—this can be a phone number or an alphanumeric sender ID where supported. Choosing the right sender ID is critical to the success of your messaging campaign. When selecting a number or sender ID type, consider the destination country, regulatory requirements, throughput needs, and your desired timeline for launch. Azure Communication Services enables you to send SMS using various sender types: toll-free number (1-8XX), short codes (12345), 10 digit long codes (1-234-123-1234), mobile numbers (+XX XXXXX XXXXX), and alphanumeric sender ID (CONTOSO). The following table walks you through the features of each sender type:

0 commit comments

Comments
 (0)