SMS Consent Demonstration for Twilio A2P Registration

Screenshots from the mobile app

During onboarding (Step 3 — Verify Your Mobile), users see explicit transactional SMS consent language, standard disclosure (rates, frequency, STOP/HELP), and links to our Privacy Policy and Terms & Conditions before a verification SMS can be sent.

Phone verification (OTP) flow

Phone verification uses a one-time passcode (OTP) delivered by SMS. The flow combines in-app consent, a duplicate-number check before messaging, delivery of the OTP to the user's phone, and secure verification on our backend so the confirmed number can be stored on the account.

1. The user enters a US mobile number (10 digits; the UI shows a +1 prefix).
2. They must check the box agreeing to transactional SMS, including the disclosures shown in the screenshots above. Without consent, the client does not send an SMS.
3. Optionally, the user may skip phone verification for now and continue onboarding; they can verify later from account settings.
4. Before triggering SMS, the app calls the backend to confirm the number is not already registered to another account (to avoid unnecessary messages).
5. When the user taps Send Verification Code, the user receives an OTP by SMS. A cooldown applies before a resend is allowed.
6. The user enters the 6-digit code in the app to prove control of the number.
7. The app submits the code for verification; the server validates it, confirms the phone is still eligible (including unique-to-account checks), and records the verified number on the user's profile.

Phone verification currently uses Firebase Authentication. We are migrating to Twilio Programmable SMS for OTP delivery.

SMS keywords (STOP, HELP, START)

These are the automated replies users receive when they text the following keywords to Find My Partner.