Skip to content

Commit c3a1496

Browse files
authored
Update sms-faq.md
1 parent 8334a3a commit c3a1496

File tree

1 file changed

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

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ The vetting score is based on the information provided during brand registration
6464
Currently, Azure Communication Services supports:
6565
- **Standard campaigns:** The most common campaign type for general A2P messaging, such as 2FA, alerts, marketing, or customer care.
6666
- **Low Volume:** For limited or test messaging with low daily traffic. Ideal for small businesses or developers.
67-
- **UCaaS (Low Volume):** A sub-type of Low Volume used by approved Unified Communications as a Service providers. Used when each phone number is tied to a human (e.g., employee texting).
67+
- **UCaaS (Low Volume):** A sub-type of Low Volume used by approved Unified Communications as a Service apps. Used when each phone number is tied to a human (e.g., employee texting).
6868
- **Enhanced:** A higher-throughput campaign type for larger brands or automated communications. May require vetting.
6969
- **Emergency:** For public safety alerts from government agencies, schools, or utilities. Strictly regulated.
7070
- **Franchise:** For businesses with multiple locations or agents/franchisees sending similar but localized content. Requires disclosure of all sub-entities.

0 commit comments

Comments
 (0)