Phone number captured in Incorrect format (Zapier)

Phone number captured in Incorrect format (Zapier)

Issue - Phone numbers from Zapier have an incorrect format (+91 without a hyphen), causing the system to read them incorrectly.. This is causing the system to treat the 10-digit phone number as a 12-digit number, resulting in Junk Leads.

Solution- 
  1. Zappier's Formatter Tool can fix this automatically. It allows to change the way data looks without needing extra apps.
  1. How to use it:        
    1. Modify the number format: Formatter can insert the missing hyphen after "+91" to make sure the system reads the phone number correctly.
    2. Prepare data for other steps: The correct phone number format will be used smoothly in the rest of the Zap actions.

Please find the article to transform data using Zapier Formatter: https://www.bannerbear.com/blog/5-ways-to-transform-your-automation-data-with-zapier-formatter/

    • Related Articles

    • Date format is showing as yyyy-mm-dd where mail merge is used

      Issue reported: The Company profile employs a distinct date format, yet the mail merge displays dates in the yyyy-mm-dd format. Solution: This is the default behavior of the system since the values are stored in the backend database in the format ...

    • Incorrect First Name Sent in the Email

      Issue Summary: 1. Customer has created one template, in that template he mail merged first name field. 2. Customer has sent emails in bulk. 3. After sending the email, we observed that all the leads system has updated the same " first name " dynamic ...

    • Dynamic form submission captured twice against the lead from portal

      Issue Description: Student submitted the form twice resulting in lead stage going back to the previous stage. Reason: This occurs when the student open up the form in multiple tabs and filling the same form from different tab. To avoid this, we can ...

    • Unable to update the distributed owner's name in the automation

      Issue: Customer was using an automation to update the assigned lead owner to the specific field. RCA: Customer was using incorrect mail merge for the owner (@{Owner:EmailAddress ,} @{Owner:FirstName ,}), because of which was values are getting ...

    • Import Failing with Unique Constraint Error

      Issue: Lead import is failing for specific leads at the time of import and the Message comes as a Unique constraint error from the Prospect Base table. Resolution: If an account has 2 unique fields, Email and Phone. And while importing both fields ...