Community Ideas

Welcome! We're glad you're here.

In the Ideas Portal, we encourage you to share your ideas and feature improvements for RingCentral products. Whether you're an admin supporting your whole team on the RingCentral app, an employee attending meetings with RingCentral Video, or a developer using integrations, we want to hear from you!

You're invited to browse existing ideas, vote on features you would like to see, and leave comments sharing your use case.

We've put together a helpful guide for getting the most out of Submitting and Voting for Product Ideas.

We can't wait to hear your bright ideas!

Please remove disabled & deleted users from any call flows/ring groups

When an employee leaves our company, we disable and then delete their extension (per RC Admin training), effectively dropping the extension into the 'Unassigned Extensions' page/list. If the phone 'object' (GLIP, RC Phone, physical phone, etc) associated with that terminated user was added to any other extensions' call flow, the phone object is still listed in the call flows even after the associated user has been disabled & deleted. When we re-use that unassigned extension for a new employee, the associated phone object is still in all of the call flows that the terminated employee was in. RC support told us to try swapping out the phone number on the phone object (didn't work), swapping out the assigned phone object for a different phone object (didn't work), and to delete the unassigned extension, effectively adding a license back to our account, and then re-create the extension when we're ready to re-use the license (didn't work, phone object still remained in call flows). Since RC can't provide us a way to identify which call flows a phone is a member of (without opening each individual extension's call flow settings) and they keep telling me this is a 'feature' not a bug, I have little choice but to request this be fixed via this forum.

  • Guest
  • Apr 27 2021
  • Attach files
  • Admin
    Becky Hensley commented
    29 Apr 03:46pm

    Thanks for sharing this idea - makes sense. We'll share with the team!