Settings and activity
185 results found
-
2 votes
Homert
shared this idea
·
-
44 votes
An error occurred while saving the comment -
5 votesHomert
supported this idea
·
-
3 votesHomert
shared this idea
·
-
11 votesHomert
supported this idea
·
-
1 vote
An error occurred while saving the comment Homert
commented
Work around is to delete the user and create a new agent profile
Homert
shared this idea
·
-
170 votesHomert
supported this idea
·
-
1 voteHomert
shared this idea
·
-
3 votesHomert
shared this idea
·
-
1 voteHomert
shared this idea
·
-
2 votesHomert
shared this idea
·
-
1 voteHomert
shared this idea
·
-
1 voteHomert
shared this idea
·
-
9 votesHomert
supported this idea
·
Homert
shared this idea
·
-
5 votesHomert
shared this idea
·
-
2 votesHomert
shared this idea
·
-
1 voteHomert
shared this idea
·
-
1 voteHomert
shared this idea
·
-
2 votesHomert
shared this idea
·
-
11 votes
An error occurred while saving the comment Homert
commented
Business Need:
Currently, RingCentral messaging allows users to send messages but does not provide visibility into whether recipients have read them. This creates challenges for teams that rely on messaging for urgent communications, task assignments, and operational updates.Requested Enhancement:
Introduce an optional Read Receipt feature that allows message senders to see when recipients have read their messages.Suggested Functionality:
Display a "Read" status below or beside the message.
Show the date and time the message was read.
For group chats, indicate which participants have read the message.
Allow administrators and/or users to enable or disable read receipts based on privacy preferences.
Maintain existing "Delivered" status functionality alongside the new "Read" status.Benefits:
Improves communication accountability.
Reduces the need for follow-up messages.
Enhances collaboration and response tracking.
Aligns RingCentral messaging capabilities with other leading collaboration platforms.
Increases user confidence that important communications have been received and reviewed.Use Cases:
Supervisors confirming employees have reviewed critical announcements.
Contact center managers ensuring urgent operational updates are acknowledged.
Project teams tracking visibility of time-sensitive requests.
Internal business communications requiring confirmation of receipt.Expected Outcome:
Users can easily determine whether a message has been viewed, leading to more effective communication and improved operational efficiency.
Feature Enhancement: Archive/Quarantine Deleted User Extensions Before Permanent Deletion
Deleted user extensions should not be immediately and permanently removed from the Admin Portal. Instead, RingCentral should provide an Archive or Quarantine state for deleted extensions.
When an administrator deletes a user extension, the extension and its associated data should be retained in an archived/quarantined state for a configurable retention period, such as 7, 14, or 30 days, before being permanently deleted.
During this retention period, administrators should be able to:
View the deleted user's extension and basic account information.
Retrieve or access associated call records, logs, recordings, and other relevant data where applicable.
Restore the deleted extension if it was removed unintentionally.
Identify when the extension is scheduled for permanent deletion.
Permanently delete the extension immediately if the administrator does not want to wait for the retention period.
This would provide administrators with a safety window to recover important information or correct accidental deletions while still allowing RingCentral to permanently remove the data after the defined retention period.
This enhancement would also address situations where important call data, recordings, logs, or other historical information is needed after an extension has already been deleted.
The existing idea, "Retrieved data for a deleted user extension," already highlights the need to retrieve data from recently deleted extensions. This proposal extends that concept by introducing an archive/quarantine mechanism before permanent deletion.