You’re trying to reach your customers, and instead your calls are getting ignored or blocked because they are being labeled as Spam Likely, Scam Risk, Robo or similar..… you’re not alone.
This is a very common industry-wide issue and we’re on your side in helping you work through it.
Why This Happens
Call labeling is handled by Wireless carriers (like AT&T, Verizon, T-Mobile) and Third-party analytics companies (like TNS, Hiya, First Orion, Neustar).
These systems are designed to stop spam and fraud, however sometimes legitimate businesses can get caught in the mix and end up getting mislabeled.
When the analytics companies determine if calls are related to spam, they look at the following:
What It Looks Like
Different carriers and analytics providers label calls differently.
|
Call Label |
Carrier / Provider |
|
Fraudulent Call |
Altice, Fidelity Communications, Telzio, Windstream |
|
Spam Risk, Fraud Risk |
AT&T |
|
Blocked – High Spam Risk |
Comcast (Xfinity) |
|
Potential Spam |
C-Spire, US Cellular, Verizon |
|
Robo Caller |
Frontier, Lumen |
|
Spam Likely |
Spectrum (Charter) |
|
Scam Likely |
T-Mobile |
|
Spam |
Truecaller |
|
Robo? Or Spam? (Prepend) |
Altice, Comcast (Xfinity), Fidelity Communications, Windstream |
How You Can Fix It
There isn’t a single instant fix, but the following steps will give you the best chance of improving the issue overall.
1. Configure Calling Name Value (CNAM)
2. Register your numbers (most important step)
|
Analytics Company |
Carrier / Provider |
Registration Link |
|
Free Caller Registry |
Multiple |
|
|
First Orion |
Tmobile |
|
|
HIYA |
ATT |
|
|
TNS |
Verizon |
|
|
Neustar |
Multiple |
Note - After registering, analytics systems will still evaluate your traffic based on behavior.
3. Follow Calling Best Practices
What If the Issue Persists?
If your calls are still being labeled as spam after updating CNAM and registering with the Free Caller Registry, the next step is to submit your number(s) directly to the provider responsible for labeling on the affected carrier’s network. Each provider has its own process and review timeline.
Note - If you are unsure which provider applies to a specific number, Voyant Support may be able to assist in identifying the correct carrier.
|
Provider and Carrier Labels |
|
|
Carrier / Provider |
Labeling |
|
Fraudulent Call or CNAM prepend of Spam? or Robo? |
|
|
Spam Risk or Fraud Risk |
|
|
Comcast (Xfinity) |
Blocked – High Spam Risk or CNAM prepend of Spam? |
|
Potential Spam |
|
|
Fraudulent Call or CNAM prepend of Spam? |
|
|
Robocaller |
|
|
Robocaller |
|
|
Spectrum (Charter) |
Spam Likely |
|
Fraudulent Call |
|
|
Scam Likely |
|
|
Spam |
|
|
Potential Spam |
|
|
Potential Spam |
|
|
Fraudulent Call or CNAM prepend of Spam? |
|
What if the Issue Persists After Working with Provider?
If you’ve engaged the problem provider and you’re still stuck, bring it to us.
We can help with the following:
At the same time, we want to be transparent:
But that doesn’t mean you’re on your own. We’ll work through it with you.
Calling Best Practices
Build Trust with Consistent, Legitimate Traffic
What Can Accidentally Make It Worse
Day-to-Day Calling Practices
Documentation for Voice Calling API: https://developers.sinch.com/docs/voice/api-reference/
Android : https://developers.sinch.com/docs/in-app-calling/android-cloud/
iOS : https://developers.sinch.com/docs/in-app-calling/ios-cloud/
Javascript: https://developers.sinch.com/docs/in-app-calling/js-cloud/
Latest Voice SDKs: https://developers.sinch.com/docs/in-app-calling/sdk-downloads/
Voice SDK
Reference Apps: JS, Android, iOS https://github.com/sinch/rtc-reference-applications
Calling API
webhook callback application: https://github.com/sinch/voice-api-webhook-nodejs
php client + samples : https://github.com/sinch/voice-api-php
How to: https://community.sinch.com/t5/Virtual-Numbers/Getting-a-number-from-Sinch/ta-p/8081
Login to https://dashboard.sinch.com/numbers/buy-numbers find the number you want.