I have used Extension Mobility for this in the past. Put the Hunt Group number in the User Device Profile. When the User Login using EM, the Hunt Group number appears oin the phone and calls will be delivered to this Hunt Group number. When they Logout, ie. go to lunch, the Hunt Group number will be removed from the phone, appear Busy to the system and it won't get any calls.
Not using Attenent Console-straight Hunt Group. I thought of EM but I was hoping to avoid giving users of Hunt Groups User logins (potentially facing thousands of logins-difficult to manage). Is there any other way?
The only other way would be Attendant Console, but that doesn't seem suited to your needs at all. Other than EM, there really is no other way...I thought of the Privacy feature, but that's only for shared lines...
You could try doing a Call Foward all back to the pilot point. So if they go to lunch get them to press CFwdALL and type in the pilot point number.
The TCD service will then pass it back to the next available agent. Alternatively if you dont want to rely on them doing it you can set this in thier line configuration to foward busy / no answer back to the pilot point.
Doing a Call Forward back to the initial Pilot Point that sent the Call to the phone is a good way to cause a potential loop that could crash the server. The reason the call came to that phone is it isn't showing busy to the Pilot Point. CFWDing the phone doesn't make it appear busy. Maybe you can set up a MeetMe conference bridge and have them all call into it when they go on break. Just kidding!! EM is the best solution. Been there, done that.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.