Documentation Index
Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
Use this file to discover all available pages before exploring further.
Real-World Example
Jane changes her mobile number while setting up communication preferences. The portal should confirm the new number before using it for SMS notices, payment reminders, or account access.Visual Flow
How It Should Work
- It should treat email and mobile number changes as verification-sensitive actions.
- It should preserve the current verified contact until the new contact is confirmed.
- It should support communication controls, login, and OTP delivery without mixing old and new contact states.
How It Should Not Work
- It should not send account-sensitive messages to an unverified new contact.
- It should not remove the consumer from future communications only because verification is pending.
- It should not allow a contact update to affect another consumer record.
Developer Notes
- Contact verification is used across profile, communication controls, and OTP flows.
- When changing this behavior, test both email and mobile update paths.
Related App Areas
app/Livewire/Consumer/Profile/CommunicationControls.phpapp/Livewire/Consumer/Forms/Profile/CommunicationControlsForm.phpapp/Livewire/Consumer/ConsumerContactInput.phpapp/Livewire/Consumer/Traits/SendOtp.php