# The phone\_number Captured During Registration Should Automatically Be Used for MFA

**URL:** <https://community.auth0.com/t/the-phone-number-captured-during-registration-should-automatically-be-used-for-mfa/167029>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [January 1, 2025, 12:51pm UTC](https://community.auth0.com/t/the-phone-number-captured-during-registration-should-automatically-be-used-for-mfa/167029 "2025-01-01T12:51:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashitosh.dessai](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ashitosh.dessai/32/69647_2.png) [@ashitosh.dessai](https://community.auth0.com/u/ashitosh.dessai)\
**Post date:** [January 1, 2025, 12:51pm UTC](https://community.auth0.com/t/the-phone-number-captured-during-registration-should-automatically-be-used-for-mfa/167029/1 "2025-01-01T12:51:49Z")

</div>

Hi everyone,

I’m working on a user registration flow where I capture the user’s phone number and verify it during the signup process. I want to use the same verified phone number for Multi-Factor Authentication (MFA). Additionally, when users configure MFA in the Auth0 UI, the phone\_number field should be pre-populated and set as read-only to avoid changes.

Questions:

- How can I ensure the verified phone number is automatically used for MFA during setup?
- Can the phone\_number field be read-only in the MFA configuration UI?
- Are there any specific hooks or custom actions I need to implement to achieve this?

Thank you.

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [January 2, 2025, 8:10pm UTC](https://community.auth0.com/t/the-phone-number-captured-during-registration-should-automatically-be-used-for-mfa/167029/3 "2025-01-02T20:10:12Z")

</div>

Hi @a■■■■osh.dessai,

Welcome to the Auth0 Community!

> [@ashitosh.dessai](#):
>
> How can I ensure the verified phone number is automatically used for MFA during setup?

Whenever a user has configured MFA SMS, the phone number field will always be pre-filled with the user’s verified phone number. The user will be prompted to submit a code to proceed. This phone number cannot be changed unless there is an MFA reset.

> [@ashitosh.dessai](#):
>
> Can the phone\_number field be read-only in the MFA configuration UI?

Yes, it is a read-only field on the MFA SMS page. You can see in our [Configure SMS and Voice Notifications for MFA](https://auth0.com/docs/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-sms-voice-notifications-mfa#message-delivery-provider-and-method) documentation of screenshots justifying this behavior.

> [@ashitosh.dessai](#):
>
> Are there any specific hooks or custom actions I need to implement to achieve this?

You can implement Passwordless SMS to capture the user’s phone number and verify it during the signup/login process.

If you decide to use a regular Database connection, you can capture the phone number by [configuring additional signup fields on the Universal Login page](https://community.auth0.com/t/configure-additional-signup-fields-on-the-universal-login-page/82448). However, this does not provide any option to verify the phone number or preemptively prefill it on the MFA page. The user’s phone number will only be verified and prefilled after the user configures MFA SMS.

Let me know if you have any questions.

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 16, 2025, 8:10pm UTC](https://community.auth0.com/t/the-phone-number-captured-during-registration-should-automatically-be-used-for-mfa/167029/4 "2025-01-16T20:10:39Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
