Skip to content

Commit ef8580f

Browse files
authored
Update telephony spam prevention guidelines
1 parent e326944 commit ef8580f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/communication-services/concepts/telephony/prevent-spam-flag.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,15 +19,15 @@ When phone numbers are flagged as spam, it can limit the ability of businesses t
1919
- **Reputation Damage:** Being flagged as a spammer can harm the business reputation and customer trust.
2020
- **Operational Disruptions:** Communication disruptions can lead to operational inefficiencies and lost opportunities.
2121

22-
## Requirements and Best Practices for Voice Communications
22+
## Requirements and best practices for voice communications
2323

2424
- **Monitor Call Patterns:** Regularly monitor call patterns to identify any unusual activity that may trigger spam filters. Avoid making a high volume of calls in a short period.
2525
- **Use Caller ID:** Ensure that the customer’s caller ID is correctly set up and displays accurate information. This practice helps recipients recognize the caller and reduces the likelihood of being reported as spam. You can apply the Azure Communication process for Caller Name Delivery (CNAM) set up in [Define your caller identity](../telephony/how-to-manage-your-calling-identity.md).
2626
- **Obtain Consent:** Always obtain consent from recipients before making calls. This goal can be achieved through opt-in mechanisms where customers explicitly agree to receive calls from the customer’s business.
2727
- **Provide Opt-Out Options:** Offer recipients an easy way to opt-out of receiving calls. This action can be done through automated systems or customer service representatives.
2828
- **Maintain a Clean Contact List:** Remove inactive or incorrect numbers by regular update of customer’s contact list. This practice reduces the chances of calling numbers that may report customer’s calls as spam. Customers can use the Azure Communication Services Number Lookup API to help customers with this process. For more information, see [Look up operator information for a phone number](../../quickstarts/telephony/number-lookup.md).
2929

30-
## Prohibited uses of Communications Services
30+
## Prohibited uses of communications services
3131

3232
The following activities are prohibited:
3333
- Using Communications Services in any manner that may expose Microsoft or any of its personnel to criminal or civil liability;

0 commit comments

Comments
 (0)