Update Mobile Number

šŸŽÆ Purpose

Enables users to change the mobile phone number used for receiving SMS authentication codes. This functionality ensures continuous access to SMS-based authentication when users change phone numbers or carriers.


šŸ“ Access Requirements

  • Edit Mode Active: Re-authentication must be completed
  • SMS Factor Present: User must have SMS OTP authentication configured
  • Update Button Available: SMS factor must show update capability in "Others" section

šŸ”„ Mobile Number Update Process

šŸŽÆ Initiation

  • Location: SMS authenticator in "Others" section with Auth Type: SMS
  • Action Button: Click update/edit button (šŸ“) for SMS authentication
  • Availability: Button only functional after re-authentication
  • User Context: Clear indication this affects SMS OTP delivery

šŸ–„ļø Update Mobile Number Screen

  • Screen Title: "Update Mobile Number" prominently displayed
  • Current Number: May show masked current mobile number
  • New Number Field: Input field for new mobile phone number
  • Format Guidance: Instructions for proper number format
  • Generate OTP Button: Trigger for sending verification SMS

šŸ“Š Mobile Number Update Interface Elements

ElementPurposeUser Experience
Current Number DisplayContextShows masked current number (--1234)
New Number InputPrimary fieldMobile number format validation
Format InstructionsGuidanceClear requirements for number format
Generate OTP ButtonVerification triggerSends SMS to new number
OTP Input FieldVerificationEnter code received via SMS
Update ButtonAction triggerProcesses number change

šŸ” Mobile Number Verification Process

šŸ“± OTP Generation and SMS Delivery

  1. Number Entry: User enters new mobile phone number
  2. Format Validation: System validates number format and carrier compatibility
  3. Generate OTP: User clicks "Generate OTP" button
  4. Code Creation: System generates 6-digit verification code
  5. SMS Dispatch: Authentication code sent via SMS to new number
  6. User Notification: Confirmation that SMS has been sent

šŸ“² SMS Characteristics

  • Sender: REL-ID system SMS service
  • Content: 6-digit verification code with clear identification
  • Delivery: Usually delivered within seconds to minutes
  • Expiration: Code valid for limited time (typically 5-10 minutes)
  • Format: Clear, easy-to-read numeric code

šŸ”„ Mobile Number Validation Flow

šŸ“ Code Entry and Validation

  1. SMS Reception: User receives text message with 6-digit code
  2. Code Retrieval: User reads authentication code from SMS
  3. Code Entry: User enters code in "Validate Authentication Code (sent via SMS)" screen
  4. System Validation: Code verified against generated value
  5. Time Check: Validation ensures code used within expiration window
  6. Success Processing: Valid code triggers mobile number update

šŸŽÆ Validation Screen Elements

  • Screen Title: "Validate Authentication Code (sent via SMS)"
  • Instruction Text: Clear guidance about SMS code location
  • Code Input Field: 6-digit numeric input field
  • Resend Option: Link to request new SMS if needed
  • Validate Button: Processes the entered code

āœ… Success Flow

šŸŽ‰ Successful Mobile Number Update

  1. Code Validation: Entered code matches and is within time limit
  2. Number Update: New mobile number replaces old number in system
  3. Success Screen: "Update Mobile Number - success screen" displayed
  4. Confirmation: Clear message that mobile number has been changed
  5. Immediate Effect: New number active for future SMS OTP delivery

šŸ“± Success Screen Features

  • Success Icon: Visual confirmation of successful change
  • Success Message: "Your mobile number has been successfully updated"
  • New Number Display: Confirmation of updated mobile number (may be masked)
  • Return Option: Link back to Sign In Options screen

šŸ”„ Mobile Number Update Flow Diagram


🚨 Error Handling and Recovery

āŒ Common Error Scenarios

Error TypeCauseUser ExperienceResolution
Invalid Number FormatMalformed phone numberFormat error messageCorrect number format
SMS Not ReceivedCarrier issues, poor signalNo SMS receivedUse resend functionality
Invalid CodeWrong digits entered"Invalid code" errorRe-enter correct code
Expired CodeCode used too late"Code expired" errorGenerate new code
Carrier BlockingSMS service blockedDelivery failureContact carrier or try different number

šŸ”„ Recovery Options

  • Resend SMS: New verification code sent to same number
  • Number Correction: User can modify number and retry
  • Format Help: Guidance on proper number formatting
  • Carrier Support: Information about SMS delivery issues

šŸ“± Mobile Number Format Requirements

šŸŒ International Support

  • Country Codes: Support for international number formats
  • Carrier Compatibility: Works with major mobile carriers
  • Format Validation: Real-time validation of number format
  • Regional Support: Adaptation to local numbering conventions

šŸ“Š Format Guidelines

ElementRequirementExample
Country CodeMay be required+1 for USA
Area CodeUsually required(555) or 555
Number LengthCarrier-specific10 digits for USA
Special CharactersUsually ignoredDashes, spaces, parentheses

šŸŽÆ User Experience Considerations

šŸ“² SMS Delivery Guidance

  • Delivery Time: Expected SMS arrival time (usually under 1 minute)
  • Signal Strength: Importance of good cellular reception
  • Carrier Delays: Possible delays during high-traffic periods
  • International: Additional considerations for international numbers

šŸ”’ Security Features

  • Number Verification: Ensures user controls the new mobile number
  • Time-Limited Codes: Prevents code reuse and reduces security risk
  • Single-Use Codes: Each code can only be used once successfully
  • Carrier Security: Leverages carrier-level SMS security

āš ļø Important Considerations

šŸ”„ Immediate Effect

  • Instant Activation: New mobile number immediately active
  • SMS Delivery: Future authentication codes sent to new number
  • Old Number: Previous number no longer receives authentication SMS
  • No Delay: Change takes effect immediately upon validation

šŸ›”ļø Security Implications

  • Access Control: User must control both current session and new mobile device
  • Verification Required: Prevents unauthorized number changes
  • Audit Trail: Mobile number changes logged for security monitoring
  • Recovery Impact: Changes may affect account recovery processes
  • Cross-Platform: Number change affects all systems using SMS authentication