Community Ideas

Welcome! We're glad you're here.

In the Ideas Portal, we encourage you to share your ideas and feature improvements for RingCentral products. Whether you're an admin supporting your whole team on the RingCentral app, an employee attending meetings with RingCentral Video, or a developer using integrations, we want to hear from you!

You're invited to browse existing ideas, vote on features you would like to see, and leave comments sharing your use case.

We've put together a helpful guide for getting the most out of Submitting and Voting for Product Ideas.

We can't wait to hear your bright ideas!

Create a SPAM WARNING when spoofed PSTN inbound calls match a number within the RC Tenant

We have had instances where inbound PSTN spam caller ids have matched numbers within our RC tenant. This has resulted in instances where individuals believed their supervisor has called them when they did not.

A call within a RC Tenant to another number within the same tenant should never originate from the PSTN, these are station to station calls. When a caller ID is presented that is within the same tenant, can the caller ID be flagged as 'SPAM Warning', or even blocked altogether, as the call has arrived from an apparently invalid direction?

This mimics SPAM Warnings done by cell carriers. In our case it is potentially consequential as the spammers are clearly leveraging trust relationships within our organizaton.

  • Guest
  • Oct 8 2021
  • Attach files
  • Guest commented
    14 Oct 10:47am

    What is RCs position relative to this regulation:

    I note RC is not listed in the database. Submissions were due Sept 28, 2021? Is this not relevant?