I had changed in the past, there were some pros and cons.
Cons:
I used to have a DID associated to the device DN not the Agent ID as it would still ring if the agent was logged in.
Now with HDU the device DN goes out of service.
You need to program a single/multi line key for DID calls (or another way if not associated to the agent id)
Pro:
Group presence works, so no need to have different Agent IDs for different groups. You can just become present and absent in your groups.
You can now login into any device rather than having to have the device programmed as ACD, it just needs to allow HDU. Nice thing is all keys etc... move just like normal HDU.
I agree it is the way they are moving, not a bad thing IMO.
Thanks!
I guess my situation is maybe a bit different. Almost all of our phones are older, 5215 or 5220 phones, so no LCD buttons. So the buttons re-mapping upon login is frustrating. With the announcement that 5215 and 5220 will be EOL with MiVB 9, we are looking at replacing with 6930's. So at the moment I don't see much benefit to the button re-mappings.
Secondary issue I have is licensing. To make the switch, we'd have to purchase additional licenses to support the Hot Desk agents. So not thrilled with that.
And lastly is going to be a training issue or process re-thinking for our ACD groups.Right now our agents log out of the queue a lot throughout the day (vs. using DND or Make Busy), when they do non-ACD work. But people can still reach them on their extension/DID. So getting them to change that behavior will be tough.
To me I guess if you were a complete new install, it would be one thing. But getting users who are entrenched in doing things one way to suddenly change will be hard. <<Sorry for the rant>>