Settings and activity
24 results found
-
20 votes
Baranee
supported this idea
·
-
1 voteBaranee
supported this idea
·
Baranee
shared this idea
·
-
14 votesBaranee
supported this idea
·
-
9 votesBaranee
supported this idea
·
-
41 votesBaranee
supported this idea
·
-
50 votesPlanned ·
AdminJessica Hernandez
(Community and Social Media Engagement Manager, RingCentral)
responded
We appreciate your feedback everyone. This is actively being looked into by our Fraud, Risk and Security team, along with our Account Management Teams. You'll start to see improvements over the next couple of months!
An error occurred while saving the comment -
49 votes
-
29 votes
-
17 votes
-
2 votes
-
7 votes
-
19 votes
-
32 votes
-
15 votes
-
169 votesImplemented ·AdminJessica Hernandez
(Community and Social Media Engagement Manager, RingCentral)
responded
Now live as of 1/23/24! Please ensure you are on the latest version of the app. Extended Emoji Library coming January 2024!
-
15 votes
-
55 votes
-
10 votes
-
38 votes
-
14 votes
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