Blink

Touch-free phone number verification

Blink is the most recent addition to our Conversion Rate Optimization Suite. This phone number verification technology eliminates the need for human interaction during verification, resulting in a great user experience while also removing the possibility of human error. Yes, some users do enter the one-time password (OTP) incorrectly!

Blink is an SDK that can be integrated into your mobile app. It works by placing a call to the phone, intercepting this call and verifying the phone number before the user has time to even answer the call. This results in a swift and smooth phone number verification process with the end user just seeing a missed call on their phone.

Blink is currently only available to Android users.

Enough reading, check out our demo video of Blink here! Should the end users phone not be able to be verified by Blink, RingCaptcha proceeds to verify the phone number by SMS and then voice OTP.

Why should I use Blink?

Completely eliminates possibility of incorrect OTP input by user
- It happens! Blink utilizes a touch-free technology for phone verification, eliminating the need for any user interaction
Seamless user experience
- No action required from user
Easy implementation
- Blink is already built into our Android SDK, which takes just 2 minutes to integrate into your app.

How do I add Blink to my verification process?

We recommend using our Android SDK as Blink is already built into the SDK. You can check out the other advantages of using our SDKs in the next section below.

If you wish to use Blink without using our SDK, just let write to our support team through our live chat.

Android SDK iOS SDK

Check out our video here to see how easy it is to integrate our SDKs. It takes just 2 minutes!

Advantages of using our SDKs

Our SDKs have all of our best features and best practices already built in!
Some of the pain points they address:

Incorrect OTP input
- Our touch-free verification (Android only) utilizes ‘missed call’ technology for phone verification eliminating the need for any user action
Poor OTP deliverability
- Our SDKs request OTP through RingCaptcha’s true single OTP API endpoint that routes OTP over different routes/medium during route disruptions
Users getting distracted while waiting for OTP
- Our SDKs are set up to send follow-up OTP for phone numbers that have not converted after 60 seconds
User not receiving OTP for other reasons. For example, phone number is blacklisted.
- A ‘Call for Help’ button that sends a request to support team
- Our SDKs can trigger our AI-assist feature which dials out to unconverted phone numbers to automatically determine why the user did no convert