Feature Requests - BLF Button Profiles and Park Keys

[Nick - SPN Co]

Hey guys, it would awesome if we could have button profiles to save having to manually configure BLF buttons across users, with v20 it's become even harder not being able to edit multiple extensions at once. This would be particularly helpful for Park keys as even on the 3CX web apps our users regularly want the option to see what calls are on park and easily pick them up. Eg you setup one set of BLF buttons and give it a name, you then assign that button profile type to the relevant extensions.

Another side note would be the ability to rename the Park keys, I know this can be done with custom templates for phones but I find most of our customers are confused by the SP1 SP2 naming convention and would much rather have a Park 1, Park 2 naming.

 

[TheodorosG_3CX]

It has been mentioned in other forum posts as well that the Multi Editing is coming however we cannot provide any ETA for the official release.

 

[Nick - SPN Co]

It has been mentioned in other forum posts as well that the Multi Editing is coming however we cannot provide any ETA for the official release.

Thanks, has there been any consideration to the button profile idea or renaming of park keys? I'm sure these questions have already been asked but these are basically the biggest two road blocks we get from customers.

 

[TheodorosG_3CX]

To be honest, in the PBX you can see this information as described, however this also depends on what you see as information on the device directly.
Meaning that a BLF key having a text "Shared Parking 1" or "Park 1" will not be very useful, some devices for example show 3,4 or 5 characters most. I believe that SP0,SP1 etc is the best option.

 

[Nick - SPN Co]

To be honest, in the PBX you can see this information as described, however this also depends on what you see as information on the device directly.
Meaning that a BLF key having a text "Shared Parking 1" or "Park 1" will not be very useful, some devices for example show 3,4 or 5 characters most. I believe that SP0,SP1 etc is the best option.

I beg to differ, I've been installing phone systems for 15 years and basically every other system or handset I've come across has at least 6 characters displayed which is why they almost always say "Park 1" - The ability to adjust the names ourselves in the PBX under System - Call Parking would definitely be a huge improvement and would cater for any devices that only have a 3 character spacing.

 

[Nick - SPN Co]

It has been mentioned in other forum posts as well that the Multi Editing is coming however we cannot provide any ETA for the official release.

On the topic of multi editing buttons, this is a useful feature and will be good once it's back but the button profiles adds a whole additional benefit. multi editing can cause issues when you just want to update one extension but accidentally overwrite some others where as a profile allows you to set some standard key configurations and easily apply these to new users, this would compliment the new department feature nicely.

 

[TheodorosG_3CX]

I beg to differ, I've been installing phone systems for 15 years and basically every other system or handset I've come across has at least 6 characters displayed which is why they almost always say "Park 1" - The ability to adjust the names ourselves in the PBX under System - Call Parking would definitely be a huge improvement and would cater for any devices that only have a 3 character spacing.

Understand about this inquiry however at the moment this will be continue this way.

On the topic of multi editing buttons, this is a useful feature and will be good once it's back but the button profiles adds a whole additional benefit. multi editing can cause issues when you just want to update one extension but accidentally overwrite some others where as a profile allows you to set some standard key configurations and easily apply these to new users, this would compliment the new department feature nicely.

Thank you for the heads up, as mentioned this is coming in next updates.