More interested in outbound capability

A US customer disagrees to submit a form that says International Whitelisting Agreement for a US-based number.
We should have a form that whitelists local numbers.

Objective: The purpose of this feature request is to streamline and automate the process of enabling whitelisting for international inbound calling on RingCentral. The proposed enhancement aims to reduce user inconvenience by automatically enabling inbound calling for a particular country if it is already enabled for international calling in the RingCentral Call Rates tab on the service web.Background: Currently, users often face inconvenience and delays when they need to enable inbound calling for a specific country. This process involves reaching out to support, which can be time-consuming. By automating the whitelisting process based on the existing configuration in the Call Rates tab, users can enjoy a seamless experience without the need for manual intervention.Proposed Functionality: Introduce an automated system that checks the international calling settings in the RingCentral Call Rates tab on the service web. If a particular country is already enabled for international calling, the system should automatically enable whitelisting for inbound calls from that country.

Currently, when a customer asks for a full-digit valid phone number to be whitelisted, we are opening up a base prefix of that number. The following reason was provided by Fraud Response to the customer:This is to confirm receipt of your signed Whitelist Agreement Form. New White Listed Destination(s): United Kingdom with phone part +44 7488... Please try your call again. We understand that you requested a specific phone number to be whitelisted. Please be advised that we do not whitelist entire phone numbers, we whitelist per destinations or phone part. Adding entire phone numbers restrict the message flow which will likely end with a failed connection. For example, the customer asked +44 7488 123 123. They filled out the whitelisting form and it has the following clause in it: "You Agree to Be Responsible for Fraud on Your Account As indicated above, RingCentral does not generally recommend whitelisting destinations because of the substantial fraud risk to the end user. If your request is granted, you assume the risk of fraud resulting from Whitelisted Destinations and shall be responsible for monitoring for fraud on your account." https://assets.ringcentral.com/us/guide/Whitelist-Customer-Agreement.pdfThe customer's concern is that they can be responsible for the full digit number that they asked for, but since we are opening a base prefix which opens an entire pool of numbers, it contradicts the clause. I would like to propose the following:At Service Web billing > calling rates, the customer can check the outbound rates and enable and disable the destination. Would it be possible to give access to individual calling rates where the customer superadmin can add the required full-digit number?Expected behaviour:With the above implementation, Even if we open the base rate prefix, the customer can choose to allow certain numbers. Benefits of the above implementation:The prevention of fraudulent activities can be improved. The customer does not have to take responsibility for the entire number pool which they didn't ask for. They will only be responsible for outbound calls for the number they have added to the calling rates.The customer will come to an agreement as per the whitelist clauses. Kind Regards, Baranee SelvendranTechnical Account Manager

Allow admins to whitelist blocked numbers from ServiceWeb. We often have to log Support tickets with Whitelist forms for numbers.It would be much easier, efficient and a better customer experience to allow admins to whitelist numbers from Service Web, signing waivers from there, rather than needing to log support tickets.

Customer should have the ability to whitelist country without sending CCAF, since not all were comfortable sharing this information