Close Menu
SalesforceCodex
    Facebook X (Twitter) Instagram
    Trending
    • The Ultimate Guide to Data Cleanup Techniques for Salesforce
    • How to Leverage Model Context Protocol (MCP) to Enhance Salesforce AI
    • Top Mistakes Developers Make in Salesforce Apex Triggers
    • Introducing Agentforce3 to Salesforce Developers
    • The Ultimate Guide to Apex Order of Execution for Developers
    • How to Handle Bulkification in Apex with Real-World Use Cases
    • How to Confidently Manage Transactions in Salesforce Apex
    • Building a Dynamic Tree Grid in Lightning Web Component
    Facebook X (Twitter) Instagram
    SalesforceCodex
    Subscribe
    Friday, August 1
    • Home
    • Salesforce Platform
      • Architecture
      • Apex
      • Lightning Web Components
      • Integration
      • Flows & Automation
      • Best Practices
      • Questions
      • News
      • Books Testimonial
    • Industries
      • Artificial Intelligence
    • Hire Me
    • Certification
      • How to Prepare for Salesforce Integration Architect Exam
      • Certification Coupons
    • Downloads
      • Salesforce Release Notes
      • Apex Coding Guidelines
    • About Us
      • Privacy Policy
    • Contact Us
    SalesforceCodex
    Home»Salesforce»Apex»Phone verification in Salesforce using VeriPhone API

    Phone verification in Salesforce using VeriPhone API

    Dhanik Lal SahniBy Dhanik Lal SahniMay 27, 2021Updated:December 25, 20244 Comments4 Mins Read
    Facebook Twitter Pinterest LinkedIn Tumblr Email
    Phone verification in Salesforce using VeriPhone API
    Share
    Facebook Twitter LinkedIn Pinterest Email

    Many clients require verified phones for their business use cases. Verified phone helps business to give their services to valid customers. Below are some reasons why Phone verification in Salesforce is required by businesses

    • Better Service : If phone (mobile) is verified then we can send service messages on mobile. Instead of sending message on fake mobile number it will reach to correct person.
    • Avoid Fake : Fake profile can be created by users. Phone verification will help us to take decision for deleting, deactivating or activating them.
    • Easy Use: SMS/Message are preferred way for notification of any service update. So phone verification is required.

    In Salesforce we can easily validate mobile/phone number using regular expression but system will not help in verification of phone number.

    There are many API/products available for phone verification. Here are some API which can do phone verification

    1. Twilio
    2. Veriphone
    3. Telesign
    4. Nexmo

    I am using Veriphone for verifying phone in this post but we can use any one based on license availability.

    Use Case:

    Account object is storing customer information. We need to verify object record’s phone number.

    Solution:

    We can verify all account records in one go with batch processing or we can go manually one by one for phone verification. I am going with manual verification.

    Step for this use case solution:

    1. Veriphone API integration
    2. Flow creation to call apex
    3. Add button on screen
    4. Testing solution

    1. Veriphone API integration:

    Before we use Veriphone API , we have to create a free account at here. Once you create and verify account. Go to setting page of your API dashboard and copy API key.

    As we have API key now to call veriphone api. Let us create a basic apex class to call this API. We can use this API using GET/POST call. I have used GET method of this API to verify it. This API required only phone number with country code and API key.

    API Url : https://api.veriphone.io/v2/verify?phone=mobile&key=apikey

    Replace mobile and API key based on your setting and record page.

    Apex Class:

    2. Flow Creation to call above Apex

    We have to call above class method from flow to get verification done. So for doing this we need InvocableMethod which can be called from flow.

    Let us create a controller class to call above phone service class.

    Now we need to create a flow to call this method.

    Verify Phone in Salesforce

    Flow Type : Screen Flow

    Element used : Get, Update, Decision, Screen, Action and Assignment

    Flow Steps:

    1. Create a variable recordId of text type to get current record id
    2. Use Get element to get account record based on above recordId. Return mobile/phone and PhoneVerified fields. Phone Verified field is custom boolean field to store status of verification.
    3. Add Action element and use above created action Verify Phone (PhoneVerificationController). Pass account record phone field to method. Add one variable to store boolean response from action call.
    4. Check response value using decision element. If returned value is true then assign true to Phone Verified field and update record using Update element.
    5. If response is false then simply show message that phone is not verified.

    If you are able to do this step properly then clap for your self, if not then use flow metadata from here.

    3. Add button on Page layout

    We need button on account page layout so that we can verify phone. For this let us create a new action button and call above flow from that button.

    Verify Phone in Salesforce | Phone verification in Salesforce6

    After button creation add that button to page layout in Salesforce Mobile and Lightning Experience Actions section.

    Test page:

    References:

    https://veriphone.io/docs/v2

    Related Posts

    1. Automating data synchronization between Salesforce and Amazon Seller
    2. AWS Signature 4 Signing in Salesforce
    3. Download the S3 File in Salesforce using AWS Signature Version 4.0
    4. Use Named Credential to Upload File in S3

    apex flow integration mobile verification phone verification salesforce veriphone
    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email
    Previous ArticleApex Code Coverage In Custom Object
    Next Article Stop Serialization and Deserialization of Object In Apex
    Dhanik Lal Sahni
    • Website
    • Facebook
    • X (Twitter)

    With over 18 years of experience in web-based application development, I specialize in Salesforce technology and its ecosystem. My journey has equipped me with expertise in a diverse range of technologies including .NET, .NET Core, MS Dynamics CRM, Azure, Oracle, and SQL Server. I am dedicated to staying at the forefront of technological advancements and continuously researching new developments in the Salesforce realm. My focus remains on leveraging technology to create innovative solutions that drive business success.

    Related Posts

    By Dhanik Lal Sahni6 Mins Read

    How to Leverage Model Context Protocol (MCP) to Enhance Salesforce AI

    July 28, 2025
    By Dhanik Lal Sahni7 Mins Read

    Top Mistakes Developers Make in Salesforce Apex Triggers

    July 25, 2025
    By Dhanik Lal Sahni14 Mins Read

    The Ultimate Guide to Apex Order of Execution for Developers

    July 20, 2025
    View 4 Comments

    4 Comments

    1. Ankita on June 5, 2021 11:09 pm

      Very useful….

      Reply
      • Dhanik Lal Sahni on June 6, 2021 1:11 am

        Thank You @Ankita

        Reply
    2. Asim Rahim on May 21, 2023 4:05 am

      Hi Dhanik, first, I would like to thank you for sharing this article, and it’s really helpful. i tried creating a flow and getting this error when debugging the flow. “Error Occurred: The flow tried to update these records: 001Hs00002nWJk9IAG. This error occurred: INVALID_TYPE_ON_FIELD_IN_RECORD: PhoneVerified: value not of required type:
      I used check box data type for PhoneVerified field.

      Reply
      • Dhanik Lal Sahni on May 22, 2023 8:13 pm

        Hello Asim,
        Looks like your are not getting API result in boolean. Please try to debug data and data type before assigning to PhoneVerified field.

        Thank Yoi,
        Dhanik

        Reply
    Leave A Reply Cancel Reply

    Ranked #1 Salesforce Developer Blog by SalesforceBen.com
    SFBenTopDeveloper
    Ranked #4 Salesforce Developer Blog by ApexHours.com
    ApexHoursTopDevelopers
    Categories
    Archives
    Tags
    apex (116) apex best practices (5) apex code best practice (10) apex code optimization (6) Apex logging (4) apex rest (11) apex trigger best practices (6) architecture (22) Asynchronous apex (9) AWS (5) batch apex (10) best code practice (4) code optimization (9) custom metadata types (5) design principle (9) flow (16) google (6) google api (4) integration (19) integration architecture (6) lighting (8) lightning (66) lightning-combobox (5) lightning-datatable (10) lightning component (32) Lightning web component (64) lwc (53) named credential (8) news (4) optimize apex (5) optimize apex code (6) optimize apex trigger (5) Permission set (4) Queueable (9) queueable apex (4) rest api (23) salesforce (150) salesforce apex (52) salesforce api integration (5) Salesforce Interview Question (5) salesforce news (5) salesforce question (5) solid (6) tooling api (5) Winter 20 (8)

    Get our newsletter

    Want the latest from our blog straight to your inbox? Chucks us your detail and get mail when new post is published.
    * indicates required

    MailChimp

    Expert Salesforce Developer and Architect
    Ranked #1 SALESFORCE DEVELOPER BLOG BY SALESFORCEBEN.COM
    Featured on Top Salesforce Developer Blog By ApexHours
    Recent Posts
    • The Ultimate Guide to Data Cleanup Techniques for Salesforce
    • How to Leverage Model Context Protocol (MCP) to Enhance Salesforce AI
    • Top Mistakes Developers Make in Salesforce Apex Triggers
    • Introducing Agentforce3 to Salesforce Developers
    • The Ultimate Guide to Apex Order of Execution for Developers
    Ranked in Top Salesforce Blog by feedspot.com
    RSS Recent Stories
    • Top 10 Salesforce CRM Trends to Watch in 2025 July 18, 2025
    • Discover the Top 10 Salesforce AppExchange Apps to Boost Productivity July 10, 2025
    • Top 20 Salesforce Data Cloud Interview Questions & Answers for Admins June 5, 2025
    • How to Connect Excel to Salesforce to Manage Your Data and Metadata February 9, 2025
    • Difference Between With Security and Without Security in Apex January 2, 2025
    Archives
    Categories
    Tags
    apex (116) apex best practices (5) apex code best practice (10) apex code optimization (6) Apex logging (4) apex rest (11) apex trigger best practices (6) architecture (22) Asynchronous apex (9) AWS (5) batch apex (10) best code practice (4) code optimization (9) custom metadata types (5) design principle (9) flow (16) google (6) google api (4) integration (19) integration architecture (6) lighting (8) lightning (66) lightning-combobox (5) lightning-datatable (10) lightning component (32) Lightning web component (64) lwc (53) named credential (8) news (4) optimize apex (5) optimize apex code (6) optimize apex trigger (5) Permission set (4) Queueable (9) queueable apex (4) rest api (23) salesforce (150) salesforce apex (52) salesforce api integration (5) Salesforce Interview Question (5) salesforce news (5) salesforce question (5) solid (6) tooling api (5) Winter 20 (8)

    Get our newsletter

    Want the latest from our blog straight to your inbox? Chucks us your detail and get mail when new post is published.
    * indicates required

    Facebook X (Twitter) Instagram Pinterest YouTube Tumblr LinkedIn Reddit Telegram
    © 2025 SalesforceCodex.com. Designed by Vagmine Cloud Solution.

    Type above and press Enter to search. Press Esc to cancel.

    Ad Blocker Enabled!
    Ad Blocker Enabled!
    Our website is made possible by displaying online advertisements to our visitors. Please support us by disabling your Ad Blocker.