Settings and activity
25 results found
-
24 votes
AdminBill
(RingCX Subject Matter Expert, RingCentral)
shared this idea
·
-
80 votes
An error occurred while saving the comment An error occurred while saving the comment Current UC customer looking at Engage Voice (would raise ARR). There biggest headache is that when an EV agent logs in with their RCO endpoint, that destination is simply a 'dummy' telephony call leg. This idea would pass call details (call baggage) like ANI, DNIS, CNAM, Queue/campaign call connected on, etc and display this within the RCO endpoint (like RC Phone or Desktop app) should the user be taking a call on behalf of EV.
-
5 votesAdminBill
(RingCX Subject Matter Expert, RingCentral)
shared this idea
·
-
7 votesAdminBill
(RingCX Subject Matter Expert, RingCentral)
shared this idea
·
-
8 votesAdminBill
(RingCX Subject Matter Expert, RingCentral)
shared this idea
·
Instead of requiring a second app be used when a RingCX agent is pushing their audio path to a RingEX endpoint, there is value in embedding the RingEX phone where the current integrated RingCX phone is located. Training agents to use only the phone in the web browser page is easier for agent on-boarding. Allowing for the phone to be detached/float around the interface could offer both options for customers.