Skip to content

feat(auth): SMS opt-in disclosure for phone-first form (#944, A2P campaign alignment) - #1007

Merged
developer-ainative merged 2 commits into
mainfrom
feature/944-phone-otp-consent-copy
Oct 7, 2026
Merged

developer-ainative merged 2 commits into
mainfrom
feature/944-phone-otp-consent-copy

Conversation

@developer-ainative

Copy link
Copy Markdown
Contributor

Adds the SMS opt-in disclosure line under the phone-first signup form's phone field: "We'll text you a one-time code to verify this number."

This was cited as already-live product copy in the A2P 10DLC 2FA campaign just resubmitted to Twilio (core#8533) — it needs to be real before the campaign's message-flow description is accurate. Also corrects a misleading doc comment in lib/build/otp.ts that called the +19377642838 number "the ZeroVoice number" (it's Builder's own; the carrier-rejection confusion traced back in part to this number/campaign being registered under ZeroVoice's branding instead of Builder's).

No test changes needed — pure copy addition, covered by existing Auth phone-form tests (36/36 pass). tsc clean.

AINative Admin added 2 commits October 6, 2026 22:59
…one field

Supports the Twilio A2P 10DLC campaign resubmission (core#8533) as a 2FA/
verification use case — carriers require the opt-in language shown to the
user at the point of consent to match what's documented in the campaign
registration. This is that language, placed directly under the phone
input it describes.
…r, not ZeroVoice's

Mislabeled during #938's implementation. Both Builder-owned OTP numbers
(937, 831) are currently carrier-blocked because their live A2P 10DLC
campaigns were registered under ZeroVoice's branding/use case
(CUSTOMER_CARE) instead of Builder's — tracked in core#8533.
@developer-ainative
developer-ainative merged commit 11ae4b2 into main Oct 7, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant