Hi @Damien welcome to the community! We don’t currently have this ability within our forms since the forms don’t save information until the respondent has clicked the submit button. Though, the developers are working on adding blocks to the builder to allow for integrations like this in the future.
Adding @kabir.mathur in here for visibility!
Hi @Damien
As @Liz mentioned, the flow of a form can’t be interrupted to make an external API call between questions.
So the only moment you can do this verification would be when the form is submitted.
As a workaround for now, I would suggest to break your flow into two forms.
One first form just asking for form number. This form redirects to an OTP validation UI of your own. When this forms is submitted it triggers a webhook to call Twilio OTP API.
If the OTP validation works, you can redirect the user to the second part of the form, passing the phone number as a hidden field.
Hope it makes sense :)
This would be HUGE for our marketing campaigns. We get a lot of fake phones and emails. PLEASE, PLEASE create this!
Agreed, @zima ! We’ve shared this with the product team, so any updates we have, we’ll post here!
The tool LeadsHook is able to do phone number/email/address verification with a Twilio integration, so it must be possible!
This feature would be a huge value add for you guys… I’m hoping I can use Typeform instead of Leadshook soon as your UI/UX is so much better. Thank you :)
Is this feature implemented to verify using an OTP? I have no coding experience and don’t intend to get one, so if this is an inbuilt feature it would really help. I’d want to just use it like a drag-drop.
I love the UI, so i’m not going to look for another site/software. I’d request you to immediately implement this even if it is at a cost. (based on each OTP that is sent, we can buy a package & use a pre-paid service for the same)
If its not implemented, it will be of no use to me & I’ll have to move on.
Thanks,
Hi @stock129 This isn’t an option we have available in our forms, so you would need to use a solution once the form is submitted.
Hi @Franky This isn’t currently in our roadmap, but if anything changes, we’ll post that update here.
Hi @Franky This isn’t currently in our roadmap, but if anything changes, we’ll post that update here.
Hi Liz, what is the progress of this project? Is it possible to test a beta?
Hi @leadworkshop I’m afraid we don’t have plans to build this feature at this time, but if that changes, we’ll post so here.
Hi @Liz ist there maybe a update on this? A phone numer verification will be a great benefit.
Hi @Sebastian TPTE Thanks for stopping by the community! This isn’t on the roadmap, but if that changes, we’ll post about it here.
Is there a way we can validate the number of digits in the number though?
Hi @Nawaz Xello While our phone field doesn’t validate if the phone number itself is real, it will ensure that it is a full number based on the country code the respondent clicks.
HI Liz,
Thank you for your reply.
All phone numbers we’re collecting are of Indian origin and all numbers usually have 10 digits. However, the typeform is accepting 9 digits as well and this may lead to a lot of missed opportunities for us.
Hi @Nawaz Xello Oh, I see. Let me ask the product team about this. I’m not totally sure if this is expected behavior or not. I’ll get back to you on this!
Hi again, @Nawaz Xello ! I asked the product team, and they let me know they use a plugin to validate the phone. That plugin provides a little bit of leeway for the phone numbers to prevent any user friction in that area. In this case, they’re most likely allowing 9 numbers to be correct since there is a use case where that number would be valid in India.
Hopefully this helps explain a bit!
Hey just nudging this. Would be a huge feature for our platform. We get many fake submissions, so it waste’s tons of time processing these orders. This feature could help us qualify our customer better and become more efficient, thank you!
We did find a way around this. Since we feel the experience of typeform is quite premium as compared to other forms we did not want to change the form which aligns with the mobile verification issue.
So what we did was that we created a pre-step of mobile number verification which then redirects to our typeform with the verified number and saves it as a hidden field. Since this solution was found in the midst of our marketing activities, we also wrote code to extract the UTM parameters to find the right attribution for our marketing techniques.
In summary, we reduced our junks to almost 0%, got the right data intel for our marketing campaigns as well as leveraged the power of typeform.
If anybody needs help, you can write to us at paarth@unweirdagency.com with the Subject: “Verification Typeform”. Since the code is already in place and just needs to be tweaked based on your tech infrstructure, we will do it at a nominal cost.
We will also share the summary of steps taken once we get any new issues on this board. Happy to help the typeform community. :)
Thanks so much for sharing this, @Paarthchadha20 !
To implement OTP phone number validation in your Typeform, you can integrate Twilio's API. While Typeform doesn't support this natively, you can use tools like Zapier or a custom script to trigger the OTP process after form submission. Twilio will send the OTP, and you can validate the input using webhooks or custom logic in your workflow. Let me know if you need more detailed guidance!
Thanks,
i switched to makeforms for my workflows. They have OTP for Mail and Phone.
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?