Feature Title: Enable Public Group Messaging for Unauthenticated External Senders

Feature Description:

Requesting a new RingCentral Team Messaging capability that allows external individuals to send messages to a shared group messaging destination without requiring a RingCentral account or authentication.

The proposed functionality should work similarly to an email distribution list, where external customers, vendors, or other contacts can send a message to a designated public messaging destination, and the message is automatically distributed to all designated group members.

Current Limitation:

RingCentral Team Messaging supports group conversations and external guest participation; however, it does not currently provide a public group messaging destination that allows unauthenticated external senders to submit messages for automatic distribution to designated members.

Requested Functionality:

Provide a unique public messaging address, link, or destination that external individuals can use to submit messages without creating a RingCentral account or signing in.

Automatically distribute incoming messages to all designated members of the associated group.

Allow administrators to manage group membership and control who receives messages submitted through the public destination.

Enable designated team members to view and respond to submitted messages, where supported.

Provide appropriate security controls, spam prevention, and administrative access restrictions to prevent abuse of the public messaging destination.

Business Justification:

This capability would streamline communication with external customers, vendors, partners, and other contacts who may not have RingCentral accounts. It would provide a centralized communication channel for teams to receive external inquiries without requiring senders to join a RingCentral conversation or create an account.

The functionality would also improve collaboration by ensuring that messages sent to a shared destination are automatically distributed to the appropriate team members, reducing the risk of missed inquiries and eliminating the need to forward messages manually.

Expected Benefit:

A public group messaging destination would extend RingCentral Team Messaging to support a distribution-list-style communication workflow for external senders, improving accessibility, team collaboration, and the handling of external inquiries.

Requested Outcome:

Evaluate the feasibility of introducing this capability as a native RingCentral Team Messaging feature.