Lift restrictions on phone number format for company phonebook to allow dialling Shared Parking

[Lincolns]

In order to work around the fact that the BLF (and thus shared parking) is awkward to access in the mobile apps, one of my predecessors set up company phonebook entries for "SP1" through "SP8". He apparently did this by using M365 shared contacts, which allowed the "Business" contact number to not be in a mobile phone format/to use letters.

Recently it looks like there was a bug at Microsoft which has renamed our shared contacts. I'm in the process of rebuilding this, but the whole thing seems ridiculous, and I want to just be able to edit the phone number fields in the Company Phone book so we don't have to jump through such hoops. Is there any way I can drop/alter the restrictions for how phone numbers are formatted when I try and import them from CSV or edit them directly?

I mean, I'd prefer if there was a way to make the BLF available on the mobile apps without having to choose/switch between showing "Team" and "BLF", but failing that, being able to edit the Company Phonebook administratively and not try and override/reject the formatting I know works just fine...

 

[Alphabetic]

You can edit the numbers from System > Phonebook

whats the problem? are you using 365 or the native phonebook?

 

[BrunoI_3CX]

Hello @Lincolns

Could you please confirm whether Microsoft 365 Phonebook synchronization is currently enabled?

If these contacts are being synchronized from M365, any changes to the synchronized contact information should be made on the M365 side. Otherwise, changes made directly in the system's Company Phonebook will be overwritten during the next synchronization.

When creating or importing contacts directly to the system, the phone number fields are validated and are expected to contain a valid dialable number. There is currently no option to disable or modify this validation.

Regarding the mobile apps, BLF entries are currently accessed through the BLF view rather than being displayed together with the Team view. There is currently no supported option to combine both views.