Feature Title: Automated Caller ID Spoofing Detection and Call Blocking

Product: RingCentral RingEX

Request Type: Security Enhancement / Call Protection

1. Feature Description

We request the implementation of a feature that can automatically detect and block suspected spoofed calls before they reach the intended recipients. The system should analyze incoming call information and identify calls where the displayed Caller ID (CLID/ANI) may have been manipulated to impersonate a legitimate business number.

When a spoofed call is detected, RingCentral should be able to automatically reject the call, quarantine it, or route it to a designated destination based on administrator-defined policies.

1. Business Need

Customers are experiencing fraudulent calls in which external callers manipulate their Caller ID to make calls appear as though they originate from a legitimate corporate telephone number. These calls can deceive employees, create security risks, damage business reputation, and potentially expose organizations to social engineering attacks.

Currently, administrators may need to rely on manual blocking, IVR prompts, or other call-handling workarounds. These measures do not reliably prevent spoofed calls, particularly when the displayed number belongs to the customer's own organization.

An automated detection and blocking capability would help customers mitigate these risks and reduce the administrative effort required to manage fraudulent calls.

1. Requested Functionality

The proposed feature should include the following capabilities:

Automatic spoofing detection: Analyze incoming call signaling and available caller identity information to identify potentially spoofed Caller IDs.

Automatic call blocking: Allow administrators to configure rules to automatically reject calls identified as spoofed or high-risk.

Trusted number protection: Provide an option to flag or block external calls that present the organization's own telephone numbers as their Caller ID when the call cannot be validated as originating from an authorized source.

Configurable security policies: Allow administrators to choose whether suspected spoofed calls are blocked, sent to voicemail, routed to an IVR, or flagged for review.

Administrator notifications and reporting: Record detected and blocked calls, including timestamps, presented Caller ID, available originating carrier information, detection results, and the action taken.

Detection transparency: Provide a reason or risk indicator explaining why a call was flagged as potentially spoofed.

False-positive management: Allow authorized administrators to review flagged calls, configure trusted sources, and adjust blocking policies to avoid blocking legitimate calls.

1. Example Use Case

A customer reports receiving an external call that appears to originate from its corporate telephone number. The call was received at the company's store line, and the displayed Caller ID was inconsistent with the suspected caller's actual originating number.

The customer would like RingCentral to identify the discrepancy, determine whether the call is likely spoofed using available signaling and authentication data, and automatically block the call before it reaches the intended extension or call queue.

1. Expected Benefits

Reduce fraudulent and impersonation calls reaching employees.

Improve protection against social engineering and telephone-based fraud.

Protect corporate telephone numbers and business reputation.

Reduce reliance on manual number blocking and IVR workarounds.

Provide administrators with better visibility into suspected spoofing activity.

Improve overall customer confidence in RingCentral's call security capabilities.

1. Acceptance Criteria

The feature should allow administrators to:

Enable or disable automatic spoofed-call detection and blocking.

Define policies for calls that impersonate the organization's own numbers.

Configure the action taken when a call is classified as suspicious.

Review logs of detected, blocked, and permitted calls.

Investigate detection results using available call signaling, carrier, and caller authentication information.

Adjust policies and trusted sources to minimize false positives.

Important consideration: Caller ID discrepancies alone do not conclusively prove spoofing. The solution should use available authentication signals, such as STIR/SHAKEN attestation where applicable, carrier information, and other risk indicators to determine the appropriate action.

1. Business Impact and Priority

Suggested Priority: High

The lack of automated spoofing detection and blocking leaves customers vulnerable to fraudulent calls that impersonate their own corporate telephone numbers. Implementing this capability would strengthen RingCentral's security offering and provide customers with a proactive approach to mitigating caller ID spoofing.

Requested Outcome: Evaluate the feasibility of introducing an administrator-configurable feature that automatically detects, flags, and blocks suspected spoofed calls at the platform level.