Skip to content

Commit 41e7a28

Browse files
authored
Update ten-digit-long-code-guidelines.md
1 parent 0e17393 commit 41e7a28

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/communication-services/concepts/sms/ten-digit-long-code-guidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,12 +65,12 @@ Campaign registration enables you to specify the purpose of your messaging (such
6565

6666
Campaign details must accurately reflect the content and intent of your messages. Providing false or misleading information could lead to rejections or delays in the approval of your campaign.
6767

68-
### Campaigns Types supported
68+
### Campaign Types supported
6969

7070
Currently, Azure Communication Services supports:
7171
- **Standard campaigns:** The most common campaign type for general A2P messaging, such as 2FA, alerts, marketing, or customer care.
7272
- **Low Volume:** For limited or test messaging with low daily traffic. Ideal for small businesses or developers.
73-
- **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).
73+
- **UCaaS (Low Volume):** A sub-type of Low Volume used by approved Unified Communications as a Service applications. Used when each phone number is tied to a human (e.g., employee texting).
7474
- **Enhanced:** A higher-throughput campaign type for larger brands or automated communications. May require vetting.
7575
- **Emergency:** For public safety alerts from government agencies, schools, or utilities. Strictly regulated.
7676
- **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)