Settings and activity
17 results found
-
106 votes
Jorell
supported this idea
·
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment
Jorell
commented
Multiple requests for this issue.
This is critical. Agents have to hang up completely with the caller and call them back. So inefficient when they should be able to just cancel the requeue.
Jorell
supported this idea
·
-
2 votes
An error occurred while saving the comment
Jorell
commented
Why was this marked as "needs more information"?
If agent A is making a call to agent B, it should not matter if Agent A was on a call from a queue or anyone else
Agent B should see Agent A is calling. Instead it just looks like they're getting a call from the queue. They see the ANI of the inbound caller.
Jorell
supported this idea
·
-
4 votes
An error occurred while saving the comment
Jorell
commented
Critical. Multiple requests about requeue cancellation on this website, this is so inefficient.
Jorell
supported this idea
·
-
2 votes
-
2 votes
An error occurred while saving the comment
Jorell
commented
Please add this feature it seems so obvious.
Now I have to communicate any changes to the custom roles I create with all of my technicians.
Everyone has their own copy of the same role which is inefficient and surely will eventually lead to some misconfiguration issues.
When I search for roles, I should be able to see Global/Account-level roles which all admins can choose and assign and then my own custom roles separately, if needed.
Jorell
supported this idea
·
-
1 vote
Jorell
shared this idea
·
-
1 vote
Jorell
shared this idea
·
-
2 votes
An error occurred while saving the comment
Jorell
commented
Critical for us, there is no reason a person at our company would need to transfer a call center call to an employee who is not in the call center.
If someone is on a call which came from an CX Voice queue, they should lose the ability to transfer a call to a corporate extension.
Simultaneously, that person should still be able to call the corporate extension directly if they are not on a CX call.
Jorell
supported this idea
·
-
19 votes
An error occurred while saving the comment
Jorell
commented
Yes
Jorell
supported this idea
·
-
13 votes
An error occurred while saving the comment
Jorell
commented
We've experienced this as well
Jorell
supported this idea
·
-
290 votes
An error occurred while saving the comment
Jorell
commented
No-brainer
Jorell
supported this idea
·
-
11 votes
An error occurred while saving the comment
Jorell
commented
This nested hierarchy makes it so that our administrators cannot all share Analytics dashboards with each other
If I add a user as CX administrator, they will only see the other admins I added in the dropdown for who to "Send Current Dashboard"
If our Help Desk technician adds someone as administrator, that user will not see ANY of the admins I added in that dropdown.
As a result, everyone is editing the dashboards themselves, which defeats the purpose of the dashboard sharing function
That would all be solved if we could simply move child admins to whichever parent we want
Jorell
supported this idea
·
-
34 votes
Jorell
supported this idea
·
An error occurred while saving the comment
Jorell
commented
Please add this
-
38 votes
An error occurred while saving the comment
Jorell
commented
This is pretty important from an admin pov
In Analytics, all we can see is "outbound intercept" for the reason a call drops, I can't do anything with that information than to tell my end users "oh well it is what it is"
I understand RingCentral engineers have access to see the SIP status of each of those calls. Even just those simple error codes could make it so I can help my end users more accurately.
Jorell
supported this idea
·
-
130 votes
An error occurred while saving the comment
Jorell
commented
Upvote
Jorell
supported this idea
·
-
5 votes
An error occurred while saving the comment
Jorell
commented
This would be huge
The RingEX corporate extensions cannot be hidden when CX agents are looking for someone to transfer to. They see both the CX Agent and their RingEX extension
Our users are sending the calls to RingEX instead of keeping it in RingCXThe problem is RingEX doesn't care if an agent is already on a call from a CX Voice queue, so an agent's EX extensions starts ringing while already on a CX call, causing a missed call.
Jorell
supported this idea
·
Upvote