When a call is forwarded to a smart phone after the desk phone did not pick up, then in order to accept the call you have to enter the phone password, then press 1 to accept the call.
Needless to say that if you are on the road driving, and you want to take the call, it's really not safe to go through these steps.
Is there any way to receive such calls as regular phone calls, so you can accept the call by just answering it ?
When answering my phone; why do I need to press answer on the touch screen, instead of picking up my handset?
We need an option to remove the press 1 from a call queue. Need this ASAP!!!
The definition of a call queue is "a line."
If this prompt was disabled, there would be no "line"...it would just fwd to the users cell phone and not roll to the next agent. You can setup a Virtual User Extension for that situation if you'd like it to flow that way.
PLEASE GIVE US THIS FEATURE. Stop making us pull out our phones while driving just to swipe and press a stupid number.
When driving and working HANDS FREE it is impossible to answer a queue call without pulling out my phone and pressing 1 - at which time I have crashed my car or received a ticket for texting while driving.
IF I could speak to RC by saying "ONE" or "Answer" that would solve this problem completely. I guess this is a new feature request....
I choose any user/extension that is part of the queue, add cell phone numbers to the section "Forward calls to".
I then choose "Create Ring Group" and select the numbers you want in the group.
When the group is created you can decide if you want calls sequential or simultaneously.
Go to the Incoming Call Information section and set up announcements when you get those forwarded calls so you know if the call is coming from work or it's just a personal call.
When this is all set up the way you like it you'll notice you don't have to press 1 to answer.
This is especially needed since we've been having issues where the call queue message won't recognize that we're pressing 1 to accept calls, causing a majority of our callers to be on hold while the system tries extensions until someone is successful at accepting the call. We've worked around the issue by using the extensions directly instead of the call queues, but this severely limits our ability to balance calls based on availability of different extensions.
Please, please, please add this feature. It makes no sense that it can be set for 'Never' on direct extensions calls if the reasoning is mobile voicemail and the like. The Call Handling settings are the same whether the call is sent to an extension directly or through the queue.
'Never' option under extension's Call Handling -> Incoming Call Information -> Play announcement before connecting -> Call Queue Calls
I would like the ability to disable this announcement on extensions that go to landline phones that do not have voicemail or any other automatic call handling features. I completely understand the need for it on mobile phones, but this should be an option that can be set on a per-extension basis by the system administrator. It would be useful to have the landlines ring until call queue timeout or pickup, but still require "press 1 to accept" message on extensions going to mobile phones to prevent voicemail answer from interrupting queue sequence.
This is especially needed since we've been having issues where the call queue message won't recognize that we're pressing 1 to accept calls. We pickup when queue call comes in, hear message and press 1, message repeats until queue call timeout and hangs up. Meanwhile caller is still on hold wondering why we don't answer the phone. We've worked around the issue by using the extensions directly instead of the call queues, but this severely limits our ability to balance calls based on availability of different extensions.
Reference support case number 05121547 for details of issues described above.
It makes no sense that there is a 'Never' option on direct extension calls but not queue calls if the reasoning is mobile voicemail. Call Handling settings apply in both cases (ie. direct extension calls can still end up at mobile carrier voicemail instead of RingCentral voicemail).
POOR DESIGN considering the people that are most likely to use your product are mobile work force and virtual office customers.
My guess is that a good attorney could make a court case pinning the liability on Ring Central when there is a fatal accident caused by this restriction.