Settings and activity
6 results found
-
21 votes
David
supported this idea
·
-
13 votes
An error occurred while saving the comment David
supported this idea
·
-
7 votesDavid
supported this idea
·
-
9 votes
An error occurred while saving the comment David
commented
Almost all PBX and VoIP systems have the ability to enable call forwarding for an extension via dialing a code from a desk phone. RingCentral lacking this feature prevents the users from controlling the call forwarding in the way they are used to from previous phone systems.
David
supported this idea
·
-
4 votes
An error occurred while saving the comment David
commented
Ringing a group of phones is basic PBX functionality. The fact that RingCentral doesn't have this at all, except by kludgy workarounds, is a serious and unacceptable deficiency. The workarounds are currently: making one extension simultaneously ring other extensions (which is not always desirable)... or using a Call Queue (which doesn't ring people who are already on the phone, and also has the unintended consequence of putting incoming callers on hold indefinitely, if not carefully controlled). A simple "Ring Group" feature as its own phone system target would be much more standard and fill this blatant hole in RingCentral's functionality.
David
supported this idea
·
-
60 votes
An error occurred while saving the comment David
commented
This would be one way to enable true "simultaneous ring", which is critical for small businesses consisting of sole proprietors with part-time assistants. The current Call Queue functionality does not allow multiple phones to ring simultaneously when an external line is call, yet have independent internal extension numbers which don't cause simultaneous ring... without an individual phone "never ringing" at someone's desk if they are the company owner and sole proprietor and in the office by themselves one day. They could find that their assistant phone is ringing, and put the caller on hold, then run over to the other desk to answer... but this is not ideal.
David
supported this idea
·
This is critical to allow any kind of control of how incoming faxes are processed. Without the caller ID being available across the company no matter what, the *only* option that does not remove the capability of publishing the company fax number in directory assistance, and does not remove the ability to use the company fax number as outgoing caller ID when faxing from the RingCentral app on any extension... is leaving the company faxes directed to the operator extension. This is a needless and frustrating limitation. The company fax number should be available as a fax caller ID no matter what settings are used, across the whole company, just as the company main number is.