Case study : Registration method with an automatic missed-call feature

My personal project is developing a registration system with an automatic feature that does not require SMS and can shorten registration steps.

Registration Flow

Project Summary

Research

Recently, I noticed that some users have complained about the disadvantages of using the SMS OTP method as their registration method because it is considered inefficient and it requires a lot of steps, especially if the SMS OTP fails to enter a user phone because there are a number of services that only limit the sending of the OTP code once.

There are many reasons why an OTP code is delayed or not delivered. Starting from technical problems such as problems with servers, applications, transmission to operators, and networks at operators.

Several companies have expressed some concerns about the cost of OTP code.

Current Flow Registration with OTP Methods

Who are the users?

Customers: They use the My Blue Bird application to travel everywhere conveniently by ordering online taxis.

My role

• Conduct design research on applications
• Create ready to use designs
• Create easy to understand application flows

Goals and objectives

Design for registration uses an automated miscall method that takes fewer steps and maximizes the user experience when registering in-app.

Let’s start designing

1. The flow of the first step: verify using a phone number

• Register Page: Here I decided to verify using a phone number first to make it easier and safer in the verification process, after verifying the phone number the user can use an email as an alternative login.
• Number Verification: After the user registers his phone number, the user can wait for an automatic call without having to pick it up (miscall) because it is only for device verification.
• Incoming call: The phone will enter for fast (1–5 seconds) because it is only to verify the device (miscall), and after that the user only needs to continue the next step.

Verify number flow

2. The flow of the second step: complete the data by filling in the email and name

• Filling out user data: Similar to a typical sign-up proccess in an application, users need to include information related to his email and name.
• Verification process is being processed: Users will wait a few seconds while the data is being processed before they can use the application.
• Verification is complete: The user will immediately be directed to the homepage and the user can start using the application for their purposes.

Fill data flow

Conclusion

Using the miscall method has a number of significant impacts:

• Shorten user steps because they don’t need to use SMS, let alone type OTP code.
• Can validate the user’s mobile number automatically, if the mobile number used is inactive, unlisted, or landline, this method will immediately identify it without revealing other sensitive information about the customer.
• The missed call method has lower operational costs, it is also cheaper than OTP SMS Authentication and OTP Voice Authentication.
• Secure HTTPS API based integration with applications.

Closing

So, this is my innovation for the exploration project.

If you have any suggestions, please send your comments.

Thanks for watching! See you later 👋