--- title: "Mobile Number Parser Configuration" slug: "mobile-number-parser-configuration" updated: 2026-03-04T08:35:26Z published: 2026-03-04T08:35:26Z canonical: "help.symphonysummitai.com/mobile-number-parser-configuration" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Mobile Number Parser Configuration ## Overview 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 application thereby leading to operational issues. To overcome this problem, Mobile Number parser is introduced, which would help to convert unstructured number formats to structured number formats, given that the parsing logic is accurately defined. ## What is Mobile Number Parser? **Mobile Number Parser** is a software component that takes input data (mobile numbers) and builds a data structure, this enables you to convert the unstructured mobile number to a structured mobile number by eliminating the difficulty involved in sending an **SMS** to a mobile number. Due to availability of various mobile number formats of the users across organizations create hassle when sending messages. To overcome this, you can use the **Mobile Number Parser**. To further understand how the mobile number parser works, let us consider the following example: Let us take mobile numbers of various countries with its country codes: | 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 4 (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. #### To configure **Mobile Number Parser Rule**, perform the following steps: 1. Select **Admin > Notifications > Mobile Number Parser Configuration.** 2. On the **Mobile Number Parser Configuration** page, click **Add New** on the right action panel. The following page is displayed. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-5HDA4Z9E.png) Figure: MOBILE NUMBER PARSER CONFIGURATION page 3. Specify the required details to configure a Mobile Number Parser Rule. The following table describes the fields on the **Mobile Number Parser Configuration** page: | **Fields** | **Description** | | --- | --- | | **Details** | | Rule Name | Specify the name of the Mobile Number Parser rule. **Note:** You can specify a parser name with maximum character limit of 75. | | Active | Activate or deactivate the rule by selecting the checkbox. - If the check box is selected, then the rule is activated. - If the check box is not selected, then the rule will be deactivated. - By default, the check box is selected. | | **Condition** | | This section is available to define multiple conditions based on which the parsing logic can be executed. The condition options available in the **Mobile Number** drop-down. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-KZ0GKSL6.png) Figure: MOBILE NUMBER PARSER CONFIGURATION Page: Condition Section | | Mobile Number | Define multiple conditions based on which the parsing logic can be executed. The conditions are as follows: - Starts With - Ends With - Contains - Does Not Contain - Greater Than - Lesser Than - Equals **Note:** In the **Value field**, you can specify either characters such as "*****", "**+**", "**(**", "**)**", "**–**" or numbers from **1 to 9** or alphabets from **a to z.** Also, you can define AND/ OR Conditions to the parser rule. | | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-a6h6hxy7.png) | Click ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-k1titfes.png) icon to define multiple conditions based on which the parsing logic can be executed. | | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-nvt10gei.png) | Click ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-8d9c6x76.png) icon to delete the parsing logic conditions defined. | | **Parsing** | | This section is available to define various parsing rules. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-JL7GQCWU.png) Figure: MOBILE NUMBER PARSER CONFIGURATION Page: Parsing Section | | Extract Characters | Define the criterion based on which the characters can be extracted from the mobile number. The criteria that can be defined are as follows: - Between Preceding & Succeeding - Before Focus Character - After Focus Character - First Few Characters (Left to Right) - Last Few Characters (Right to Left) | | Parsing Logic | Based on the criteria defined, the ‘parsing logic’ controls are reflected dynamically as displayed in the above screen. | | User-Defined Key | Define a key name to the extracted character. **Note: User-Defined Key** text box supports up to 100 alpha numeric characters. The defined parsing logics are displayed in the grid view. You can edit an already defined parsing condition by clicking on the hyperlink on the User-Defined Key column. The User-Define Key column has a hyperlink. When you click on the hyperlink, the corresponding parsing condition loads in edit mode. You can then make the required changes and update it by clicking ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-axn0rrqj.png) icon on the Add column. | | Preview | Preview the pattern based on the selected value in the ‘Extract Characters’ and ‘Parsing Logic’ column so that the Administrator is clear on the value that is extracted. | | Add | Add the parsing condition by clicking on the ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-cvb20eqx.png) icon | | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-hqmk4cfo.png) | When you click on the ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/mobile-number-parser-configuration-image-x5bfwfvb.png) icon in the grid view, a pop-up with “Are you sure you want to delete the user defined key: (Mobile No) ?” message is displayed with the following options: - **Yes**: The condition will be deleted - **Cancel**: The focus will shift back to the screen with no delete operation being performed | | **Mapping** | | This section is available to Map all the user defined keys to the standard attributes of the **Mobile Number** field. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-MO38EDYG.png)Figure: MOBILE NUMBER PARSER CONFIGURATION Page: Mapping Section | | User-Defined Key | All the user defined keys in the Condition section will reflect as dropdown in the User-Define Key field. The Standard fields attributes are as follows: - Country Code - State Code - Mobile Number | | Submit the parsing rule by clicking on the **SUBMIT** button. | ##### **List** Click Show list icon to display the **List** table showing all the configured Mobile Number Parser rule details. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-EGO6NCC2.png) Figure: MOBILE NUMBER PARSER CONFIGURATION page: List of Mobile Number Parser Rule Configured - To edit a Mobile Number Parser Rule detail, click the configured Rule Name. Make appropriate changes and click **Submit**. - To display inactive Mobile Number Parser Rules, click the **Include Inactive** checkbox. Note: When the Mobile Number Parser Rule details are displayed under the **List** table, the **Add New** icon is displayed on the right action panel. Click **Add New** to add a new Mobile Number Parser Rule. Active control is a type of switch that is represented as checkbox, where the user can select and clear as a Switch control action.