Skip to main content
Answered

Feature to verify phone number

  • September 8, 2021
  • 30 replies
  • 4104 views

Show first post

30 replies

  • Navigating the Land
  • October 2, 2024

Thanks,

i switched to makeforms for my workflows. They have OTP for Mail and Phone. 

Are they good? Hearing a lot about them lately. Is the UI / UX even as good as Typeform?

Overhyped product. bought it and refunded. Childish founder who like to trash other competitors. Red flag


Theformguy
  • Navigating the Land
  • April 10, 2025

Thanks,

i switched to makeforms for my workflows. They have OTP for Mail and Phone. 

Thanks for referring. I used them. They give 5k responses for $29. But, you need to purchase verification SMS credits separately and it’s costly compared to Twilio. For US, Twilio charges per sms are $0.007 for which they charge about $0.040. I had to reach out to support and they gave only 20% discount. But it’s okay for me as I don’t need to manage a separate Twilio account. 


  • Navigating the Land
  • July 31, 2025

Hey Damien,
You're right Typeform doesn’t support OTP verification natively, and setting it up with Twilio requires custom API work and infrastructure for sending and verifying codes.

If you're looking for a simpler solution to check if a phone number is real and valid, I recommend using Zapier + Numverify. I've used this setup successfully for form validation without needing to send OTPs.

Here’s how it works:

  1. A user submits a phone number via Typeform

  2. Zapier picks up the submission

  3. (Optional) Use OpenAI inside Zapier to clean and format the number

 

  1. Pass the formatted number to Numverify, which checks if it’s:

    • A real number

    • Properly formatted

    • From a valid carrier and country

Why use this approach:

  • No code required

  • Works for international numbers

  • Flags fake or mistyped entries

  • Integrates easily with Google Sheets, CRMs, and more

  • You can still trigger Twilio OTP after validation, if needed

Let me know if you’d like help setting up a sample Zap.

— Aanchal


James
Community Team
Forum|alt.badge.img+5
  • Community Team
  • July 31, 2025

Thanks so much for your suggestion ​@Aanchal 🙏 Seems like a robust solution!


Theformguy
  • Navigating the Land
  • August 28, 2025

Hey Damien,
You're right Typeform doesn’t support OTP verification natively, and setting it up with Twilio requires custom API work and infrastructure for sending and verifying codes.

If you're looking for a simpler solution to check if a phone number is real and valid, I recommend using Zapier + Numverify. I've used this setup successfully for form validation without needing to send OTPs.

Here’s how it works:

  1. A user submits a phone number via Typeform

  2. Zapier picks up the submission

  3. (Optional) Use OpenAI inside Zapier to clean and format the number

 

  1. Pass the formatted number to Numverify, which checks if it’s:

    • A real number

    • Properly formatted

    • From a valid carrier and country

Why use this approach:

  • No code required

  • Works for international numbers

  • Flags fake or mistyped entries

  • Integrates easily with Google Sheets, CRMs, and more

  • You can still trigger Twilio OTP after validation, if needed

Let me know if you’d like help setting up a sample Zap.

— Aanchal

How do you verify if the number belongs to the person filling up the form. And how will the OTP verification via Twilio work? I think this still doesn’t solve the basic problem of verifying user’s phone number using OTP.