Settings and activity
45 results found
-
10 votes
Jerome
supported this idea
·
-
25 votesJerome
supported this idea
·
-
5 votesJerome
supported this idea
·
-
32 votesJerome
supported this idea
·
-
3 votesJerome
supported this idea
·
-
5 votesJerome
supported this idea
·
-
5 votesJerome
supported this idea
·
-
9 votesJerome
supported this idea
·
-
23 votesJerome
supported this idea
·
-
6 votesJerome
supported this idea
·
-
3 votesJerome
supported this idea
·
-
5 votesJerome
supported this idea
·
-
6 votesJerome
supported this idea
·
-
235 votesJerome
supported this idea
·
-
4 votesJerome
supported this idea
·
-
4 votesJerome
supported this idea
·
-
105 votes
An error occurred while saving the comment Jerome
supported this idea
·
-
9 votesJerome
supported this idea
·
-
9 votes
An error occurred while saving the comment Jerome
commented
We have found serious deficiencies in how RC handles faxing to workgroups. While it is a nice feature that each individual can send and receive faxes directly to their direct line and directly through the app, we converted into RC and ported in all of our old copper fax line numbers. This required us to stand up a call queue to replace the phone number connection to a physical MFD that generated faxes. The users in a workgroup that used to have local access to the physically generated faxed documents have to be set up as admin users for the fax queue that has been established, or else they do not receive the email containing the attached fax. On top of that they do not receive the faxes to these shared numbers in the RC app, but have to receive the fax via email. This is a tremendous flaw in the system. We should be able to stand up a dedicated fax "user" that links to our ported in fax number. We then should be able to assign to that fax "user" the actual individuals who are in the workgroup that would receive faxes from that number. These individuals should not have to be admins, but should just be end users with end user rights. From there those individuals should be able to access the received documents through their RC app, along with email receipt, if they chose or we allowed it administratively.
Jerome
supported this idea
·
-
4 votesJerome
supported this idea
·
We are a recent convert to RingCentral from a larger deployment of Shoretel. We sure do miss Shoretel, but knew that we had to jump off that system as Mitel didn't have anything that we wanted to move forward with. That said, our staff became very acostomed to a seamless movement between desktop software and desk phone. Whatever action they took in the software was reflected on the phone, and vice versa. When they went to check VM in the software, it would light up their phone and play audio through the phone. If they checked VM on the phone, the status and storage of that VM would immediately reflect the status they gave it during their session on the phone (heard, deleted, saved, forwarded, etc.). While desktop pairing of the telephone device on a user's desk is helpful, the fact that a user cannot get VM audio through their phone if they interact with the VM in the software is very odd. Additionally we used to do a lot of ad hoc assistance calls with staff and the inability to do a desktop screen share when deskphone pairing is on and audio is going through the phone is a tremendous step backward from Shoretel. In the Shoretel system we could do an ad hoc screen share in the software, to the connected user, with audio going through the desk phone.