Fix TCR Code 2139: Form Missing Phone Input Field - MyTCRPlus
2139

Form Missing Phone Input Field

LOW PRIORITY
5% Rejection Rate
15 min Avg Fix Time
100% Success Rate
⚠️

Why This Rejection Happens

The URL or screenshot you provided for your opt-in form shows a form that collects data (like Name or Email) but does not have a field to enter a phone number. You cannot collect SMS consent without collecting the phone number itself.

Common Triggers: Submitting a link to an email newsletter signup form, a generic "Contact Us" message box, or a form where the phone field is hidden by conditional logic.

Root Cause Analysis

Regulatory Framework: 10DLC Consent Verification Mechanics

Primary Triggers

  • Wrong Link: You accidentally linked to your email subscription page instead of your SMS signup page.
  • Hidden Field: The phone field only appears if the user selects "Contact me by phone," but the default view hides it. Vetting agents review the default state.
  • Message Box Confusion: You assumed users would type their number in the "Message" body of a contact form. This is not a structured data field and is rejected.

Required Elements

Element Requirement Why?
Input Field Specific "Phone" or "Mobile" field Structured data collection is required for automated systems.
Visibility Visible on load Agents must see it without guessing how to trigger it.
Labeling Clear Label User must know what data goes there.

Step-by-Step Remediation

1

Check Your Form URL

Open the link you submitted. Look at the form. Is there a box specifically for "Phone Number"?

✓ Compliant Form

Fields: [Name] [Email] [Mobile Number] [Submit]

✗ Non-Compliant Form

Fields: [Name] [Email] [Subject] [Message] [Submit]

2

Add the Phone Field

If the field is missing, log in to your form builder (WordPress, HubSpot, etc.) and drag a "Phone" field onto the form. Make it Required if SMS is the primary purpose.

3

Update Your Submission

If you fixed the live site, just resubmit the same URL. If you provided a screenshot, take a new one showing the added field.

Carrier-Specific Requirements

T-Mobile

  • Requires the phone number field to be clearly labeled. A field just labeled "Contact" is often rejected if it looks like an email field.

AT&T

  • Will verify that the phone field is functional. If the form validates email format but not phone format, it may be flagged as a configuration error.

MyTCRPlus Tools That Can Help

Consent Form Builder

Create a compliant form that always includes a validated phone number input field.

Use This Tool →

Website Validator

Scan your URL to detect if the form is rendering correctly or if scripts are blocking the phone field.

Use This Tool →

Pre-Resubmission Checklist

  • The form has a dedicated input for "Phone" or "Mobile."
  • The field is visible immediately when the page loads.
  • The URL provided points to the corrected form.
  • I have not simply relied on the "Message" box for numbers.

Common Mistakes to Avoid

❌ Newsletter Signups

The most frequent error is submitting a footer "Newsletter Signup" that asks for Email only. You cannot use an email signup for SMS consent.

❌ "Optional" Phone Fields

If the phone field is marked "Optional" but there is no checkbox to specifically opt-in for SMS, it's ambiguous. If the primary goal is SMS consent, the phone field should be required or tied to a clear checkbox.

Expected Timeline

15 Min
Implementation Time
1-3 Days
Resubmission Review
100%
Success Rate After Fix