Settings and activity
3 results found
-
191 votesSeptember 2023 UpdateThank you for your responses and feedback everyone! Product has completed their research into this possibility and have confirmed that at this time, the feature is not on any upcoming roadmaps. With this update, the status for the idea has been changed to Future Consideration. Hello everyone, Thank you for your interest in this idea. As our product managers are researching this feature, they'd like to know if you want this to be for Direct Messages and Teams, or just Direct Messages? Please leave your feedback and use case via comment. Thanks all!
Turnip
supported this idea
·
An error occurred while saving the comment -
41 votes
An error occurred while saving the comment Turnip
commented
We strongly support this feature request. Automatically resolving SMS conversations after 72 hours of inactivity can disrupt workflows, particularly when customer inquiries require extended follow-ups or remain pending.
We believe administrators should have the flexibility to disable automatic resolution or configure the inactivity period based on their organization's operational needs. Conversation history should also remain accessible regardless of resolution status.
Providing these options would improve conversation management, maintain visibility into pending customer requests, and allow businesses to establish their own follow-up processes without being restricted by a fixed 72-hour timeframe.
Turnip
supported this idea
·
-
30 votes
An error occurred while saving the comment Turnip
commented
We would really appreciate the ability to configure or disable the 72-hour auto-resolve timer for Shared SMS Inbox conversations. Different organizations have different workflows, and a fixed 72-hour limit does not always fit how teams manage customer or patient communication. In our case, conversations may remain active for several days due to scheduling, follow-ups, insurance coordination, or waiting for a response. It would be very helpful if administrators could define their own auto-resolve period, or choose to keep conversations open until they are manually resolved. This would allow each organization to build a process that better fits its operational needs.
Turnip
supported this idea
·
We strongly support this feature request. Having the ability to see whether a message has been read by the recipient would be a valuable enhancement to RingCentral's messaging functionality.
For teams that rely on RingCentral for internal communication and collaboration, read receipts would help improve accountability, reduce unnecessary follow-ups, and ensure important messages are acknowledged.
Ideally, we would like to see a **Read** status with a timestamp indicating when the recipient viewed the message, similar to what is available in other messaging platforms.
This would be a significant improvement to RingCentral's messaging experience and overall team communication efficiency.