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!

Single Sign-On for Support Site

Signing onto the Support.ringcentral.com site to get anything done is a true hassle. You go to the site, click the link to log in, then when you click on the My Cases link, you are told "It looks like you're not logged in" and you have to log in again. Then, once you are viewing your case list, when you click on a case to view that case, you are again told "It looks like you're not logged in" and you have to log in FOR A THIRD TIME! If my users had to log in that many times just to view an open ticket they'd be furious at my IT department. Guess what? The multiple log ins on your site just to get case work done just may drive me elsewhere. The tech at the help desk told me that's normal because they're different systems. Well, no, it's not normal. You should only have to log into the support site one time. Can you please arrange for single sign-on for your support site?

  • Kent Haines
  • Jun 21 2021
  • Implemented
  • Attach files
  • Kent Haines commented
    19 Jul 06:02pm

    Just an FYI���this is not fixed yet. I was at a conference last week so wasn���t able to test it, but when I just did I was asked to login when trying to get into an existing ticket.

    Kent

  • Admin
    Rylie Perrault commented
    12 Jul 03:33pm

    Hello! This is a known issue that our team has been working on solving. Great news - users no longer have to log in twice to create a web case! Please let us know if this update doesn't solve your problem!