What's New?
Different organizations follow different ways of storing the employee mobile numbers in the employee database such as AD, HR Management systems etc. Moreover, different countries have different mobile number formats. If the mobile number formats are incorrect, then the end users may not receive the SMS from SummitAI application thereby leading to operational issues.
To overcome this problem, SummitAI is introducing a Mobile Number parser that would help to convert unstructured number formats to structured number formats, given that the parsing logic is accurately defined.
To further understand how the mobile number parser works, let us consider the following example:
Let us take mobile numbers of various countries with different formats:
Types | |
Type 1 (India) | The Mobile Number is present along with country code. Ex: 919845xxxxx0 |
Type 2 (India) | The Mobile Number is present without country code. Ex: 9845xxxxx0 |
Type 3 (Singapore) | The Mobile Number is present with hyphen. 135-5xx7 |
Type 4c(America) | The Mobile Number is present with country code in braces. Ex: (555) 555-xxxx |
We can see that the mobile numbers are of different format. You can specify the conditions for the Mobile Number to parse the numbers, this converts the unstructured format of the mobile number to a structured format.
Case 1: Mobile Number Format = +91-9845xxxxx0
How to define the parsing logic for this format?
- Condition:
- Mobile Number Starts with “+” character
- Mobile Number Equals to “12” Characters
- Parsing Rules:
- Between Preceding & Succeeding: The preceding value is "+" and succeeding is "-". The value between these are identified as Country Code.
- After Focus Character: The Focus Character value is "-" and the of character after focus Character is “10”. The last 10 values are identified as mobile number.
- Field Mapping: Map the User-Defined Key value to Standard Field to identify the Country Code, State Code and Mobile Number stored in the User Master.
Note:
- By specifying the conditions, parsing and mapping requirements, the Mobile Number +91-9845xxxxx0 is parsed and categorizes "91" as Country Code and "9845xxxxx0" as Mobile Number.
- Based on your mobile number format you can specify the parsing parameters and use them to send SMS notification.
- The Parser will convert the mobile number in a structured format and send the SMS during the runtime.
Case 2: Mobile Number Format = 919845xxxxx0
How to define the parsing logic for this format?
- Condition:
- Mobile Number Does not contain “+” character
- Mobile Number Does not contain “&” character
- Parsing Rules:
- First Few Characters: The First value is "2". The first two values are identified as Country Code.
- Last Few Characters: The Last value is "10". The last 10 values are identified as mobile number.
- Field Mapping: Map the User-Defined Key value to Standard Field to identify the Country Code, State Code and Mobile Number stored in the User Master.
Case 3: Mobile Number Format = (91)9845xxxxx0
How to define the parsing logic for this format?
- Condition:
- Mobile Number Greater Than “10” characters
- Mobile Number Starts with “(“
- Mobile Number Equals to “12” Characters
- Parsing Rules:
- Before Focus Character: The Focus Character value is ")" and the of character before focus Character is 2. The first two values before “)” are identified as Country Code.
- Last Few Characters: The Last value is "10". The last 10 values are identified as mobile number.
- Field Mapping: Map the User-Defined Key value to Standard Field to identify the Country Code, State Code and Mobile Number stored in the User Master.
Benefits
Following are the benefits of using the Mobile Number Parser feature:
Eliminates the troubleshooting time.
- On time notification due to accurately defined parser logic.
UI Change
The Mobile Number Parser Configuration screen is available in the Admin module (Admin > Advanced > Notification > Mobile Number Parser Configuration). For more information see, Mobile Number Parser Configuration.
Figure: MOBILE NUMBER PARSER CONFIGURATION page