Configure phone buttons for items other than Presence

Coming from past Mitel, ShoreTel (before they were owned by Mitel), and many other systems, why is button control a limited "feature"! I fully agree that this needs to change and allow other buttons to be programed from the web interface, either by the admin directly or letting the user setup their needed buttons. Not to mention supporting a default key layout template for the VVX 450.

So RC has added the ability to put speed dials on Mitel phones, but they limited it to 24 lines and are calling the limit a "feature". But now you can't add anything to the phone via the phone interface and it pushes any additional "presence" lines way down the screen. Come on RC if presence can be used for more than 24 lines, then so can any other keymap function. Please fix this "feature" to be fully functional.

Thanks for adding the extra features for the Speed Dial's in the portal. Can we ask to enable that ability for each user in the HUD? It would save me a lot of time if I could let the end user manage their own speed dials. Thanks.

Yes! We are coming from Mitel and could configure all sorts of things on the phone buttons. External speed dials, paging group extensions, etc. They have the KB on how to do it, just ask them for it.. PLEASE.

It seems to me that this is somewhat available now, but on a larger scope, considering your aquisition of Mitel/Shoretel, on those phones there were many button features available (logon, logout, dial voicemail direct, monitor extension, page, park, etc, etc). There were probably over 20 some features available, and even then at times it didn't seem like there were enough for a few needs. Having no ability to dial pauses seems to be a problem (also sort of an issue with Mitel/Shoretel). Why not open up the button use (if possible, maybe it is a VVX limitation?) and try and make it more powerful. Why can't I have a menu on a button, why can't I have a queue on a button, why can't I pick up with a button from another phone. These features all work with dial strings, why not allow them to work on buttons.

At the end of the day, the desk phone has a valuable purpose, and that is to help workflow. I could give you a computer with just a mouse for example... but that isn't as useful. You can give me an extension without a phone, but that ISN'T as useful. The phone has value over software alone. If anything we need more one touch buttons, not fewer. The only alternative I believe would be to implement those into the softphone/webphone interface (also done by Mitel/Shoretel in connect and communicator).

We swapped out some phones and had to manually set up all the paging quick buttons on all of the phones, which would have been a great option to have them under "presence" for the phone to automatically populate.

This would be very helpful. There are use cases where we want to have control over what buttons are on the phone, and going to each phone to program a speed dial is maddening.