Caller ID shows spam risk

Hello Staci,

Please have them checked their Caller ID Settings. You may click on this link https://support.ringcentral.com/article/3614.html

I have the same issue. Our user's caller ID is set to the company phone number and not "possible spam risk" or "likely spam". What else can be done to prevent our call recipients from receiving this message?

@Staci Heidenson @jeffrey-raymond-jr. We are getting this same feeback from our clients on our outbound calls. We currently use our direct lines as the Caller ID and would prefer to keep it that way but we do not want our calls to show as a possible spam risk. Has anyone gotten more information about what might be causing this issue?

I have the same problem from my extension. I changed it to my direct line and called my personal cell to see what happens. It now says the company name, but I'm not sure if that's because I have the name saved in my phone. However, before when I had the main phone number of the company, it showed up as Spam Risk when I called my cell.

I am having this issue as well. My caller ID is set to my direct line, but am receiving feedback from clients that my call shows up as "Spam Risk." Is there anythign to be done about this? @Mary-Community_Moderator

We are fighting with this same issue as well. We migrated to RC in January from multiple phone carriers at various locations, and it seems that RC doesn't send the caller id information properly, and we are losing customers and prospects because our calls are all labeled as "suspected spam," or at BEST it just displays the ANI with no company information. We have requested a de-listing with ATT Wireless and Verizon wireless, but this problem won't be resolved until RC starts passing full caller ID information to the called party. Has anyone found a way to resolve this?

This is an ongoing problem for us as well, and checking the Caller ID Settings didn't help. Do you have any other suggestions?

Nothing seemed to work. We do realize it may depend upon the client's cell carrier. However, we just started using Hiya to 'fix' the problem. Too early to tell if it has worked...but it is free. Worth a shot!

You can pay a lot of money to third party companies out there to "clear" your name across all of the carriers. Outside of that you're fighting algorithms outside of RC's control. Not much to do about that.

Have you had any success with Hiya? We are starting to run into this same problem and it was suggested by RC support to give this a try.