Hello,
I find 3cx works very good in basically all areas, but one area that it seems to fall down is Call Parking. The Orbits and Shared Parking just seem very complicated for the average phone user to deal with.
It seems that 3cx almost has a very elegant solution but needs one more step.
How basically every other phone system we have worked with works (and I've found very easy to train and users to deal with) is the reception simply transfers a call to a dedicated park extension and then when you do the transfer the system tells you the number to pick it up.
Then Reception doesn't need to have to watch if slots are free or not. We don't have to configure dedicated buttons for every extension etc.
The most common way I see it setup is the parking extension is say 9000 and slots are from 9100 to 9199.
I transfer a call to 9000 (always 9000 I never have to look at what slots are used). The phone system then looks at the first free slot, parks the call there and tells me "Call parked on 9100" or "Call parked on 9101".
Then reception just simply tells the user to pickup 9101 or whatever was read back to them.
Works great for every situation.
The Orbits are simply confusing. I can't figure out a use case that doesn't make this complicated or hard. I've *never* been able to explain it to a user and had them use it effectively. They are always confused. That may be a failure on my training I admin since I can't figure out how it make it easy.
Shared Park is very close. We've used it with some success, but still requires a bunch of extra setup and configuring all reception phones with the slots and reception always has to watch which slots are free and manually pick one. It's close but doesn't work from every phone since every phone since we don't want to reserve basically all the buttons for SP slots. We also don't want to have to configure say an 80 user organization with 80 shared parks and then configure all users with their own shared park.
Would be great if we could just have a shared park extension (like 9000 in my example above) where you can always transfer to say *50 and it just moves the call to the first available slot and then tells you the slot "Call parked on Shared Park 51". Then reception can tell whoever "Parts pickup *51".
Thanks,
Serge.
I find 3cx works very good in basically all areas, but one area that it seems to fall down is Call Parking. The Orbits and Shared Parking just seem very complicated for the average phone user to deal with.
It seems that 3cx almost has a very elegant solution but needs one more step.
How basically every other phone system we have worked with works (and I've found very easy to train and users to deal with) is the reception simply transfers a call to a dedicated park extension and then when you do the transfer the system tells you the number to pick it up.
Then Reception doesn't need to have to watch if slots are free or not. We don't have to configure dedicated buttons for every extension etc.
The most common way I see it setup is the parking extension is say 9000 and slots are from 9100 to 9199.
I transfer a call to 9000 (always 9000 I never have to look at what slots are used). The phone system then looks at the first free slot, parks the call there and tells me "Call parked on 9100" or "Call parked on 9101".
Then reception just simply tells the user to pickup 9101 or whatever was read back to them.
Works great for every situation.
The Orbits are simply confusing. I can't figure out a use case that doesn't make this complicated or hard. I've *never* been able to explain it to a user and had them use it effectively. They are always confused. That may be a failure on my training I admin since I can't figure out how it make it easy.
Shared Park is very close. We've used it with some success, but still requires a bunch of extra setup and configuring all reception phones with the slots and reception always has to watch which slots are free and manually pick one. It's close but doesn't work from every phone since every phone since we don't want to reserve basically all the buttons for SP slots. We also don't want to have to configure say an 80 user organization with 80 shared parks and then configure all users with their own shared park.
Would be great if we could just have a shared park extension (like 9000 in my example above) where you can always transfer to say *50 and it just moves the call to the first available slot and then tells you the slot "Call parked on Shared Park 51". Then reception can tell whoever "Parts pickup *51".
Thanks,
Serge.
