phone numbers stored incorrectly since latest update (country prefix)

New Contributor

We have been using Microsoft bookings quite a bit and really like it more and more.

Recently there was an update that changed how phone numbers are entered & stored in the related contact which now affects our text message reminder system.


Not sure when the last update reached us but it brought with it two major problems related to how phone numbers are handled now.

  1. the new "phone number prefix" field ALWAYS defaults to "United states (+1)". There is no way (at least that I could find) to change the default country meaning (since our business is operating out of Austria) clients always have to open the drop down box and select the correct country first. 

  2. The number itself is unfortunately "partly" butchered when saved which is a real problem for our SMS reminder system. The "+" in the prefix is for some reason ignored completely.


Example: a new client makes a booking and enters the phone number:  "United States +1 / 23456789"
This number is then stored as "123456789" instead of either "+123456789" or "00123456789" resulting in a wrong number.
We have a cloud based appointment reminder system that automatically sends out text messages after a booking to a clients phone number by searching for a valid number within each new appointment. However, because the leading zeros or the "+" is now ignored and not passed on by Microsoft Bookings, all the phone numbers are therefore invalid and text messages are only send out after we manually open each appointment in the calendar and add either a "+"  or a "00" in front of the number.

Furthermore if a client makes a mistake and adds a leading zero into the number field, bookings (instead of intelligently ignoring it) parses this on as well resulting again in an invalid number.

Example: A client enters "United States +1" 023456789
The resulting number should be "+123456789" or "00123456789" but is actually stored as "1023456789"

This is quite a big problem for us at the moment so a fix (or even a temporary workaround until a fix can be rolled out) would be greatly appreciated!

0 Replies