Who must register
Anyone sending application-to-person SMS or MMS through a US 10-digit local number must complete A2P 10DLC registration.
Twilio and carriers use registration to understand:
- Who is sending
- What messages are sent
- How recipients consent
- How recipients opt out or ask for help
- Whether the traffic matches a legitimate business use case
Registration improves deliverability and provides the carrier-approved throughput associated with the campaign.
Know when action is required
Fieldified displays a registration banner or status in two-way messaging settings.
An administrator should open Complete Registration when the number is not registered or when more information is required.
Registration statuses
Not started
The business information has not been submitted.
Next steps:
- Open Complete Registration.
- Prepare the official business and policy information.
- Review every field for consistency.
- Submit the application.
Processing
Twilio or an A2P registry is reviewing the brand or campaign.
Monitor Fieldified for requests for clarification. Current campaign review times can vary; Twilio may display an estimated processing window in the registration experience.
Do not submit duplicate applications while review is active.
More information required or failed
The application contains missing, inaccurate, inconsistent, or unverifiable information.
Next steps:
- Open the displayed rejection reason.
- Correct the cited business, website, policy, or opt-in issue.
- Verify related fields for the same inconsistency.
- Resubmit.
Contact verification expired
An identity-verification message was sent to the authorized contact but was not completed within its validity period.
Request another verification message and complete it using the same authorized mobile number. Contact Fieldified support if the number cannot receive the verification.
Approved
The brand and messaging campaign are approved and the dedicated number can be associated with the campaign.
After activation, authorized users can send and receive client messages from the registered number.
Prepare the application
Collect:
- Legal business name
- Business type
- EIN or applicable tax identifier
- Tax address
- Operating address
- Website
- Authorized contact
- Privacy-policy URL
- Terms URL
- Messaging use case
- Opt-in description and evidence
- Sample messages
- Expected traffic
Select the correct business type
Choose the structure reflected in official records, such as:
- Sole proprietor
- Partnership
- Limited liability company
- Cooperative
- Nonprofit organization
- Corporation
- Government organization when applicable
Do not choose sole proprietor simply to avoid entering an EIN. Twilio validates the business type against the identity and tax information supplied.
Enter the legal business identity
Use the exact legal name and identifier found in tax records.
The tax address must be a physical address associated with the business identity. Avoid:
- Trade names in place of the legal name
- Typographical differences in the EIN
- An unrelated mailing address
- An employee’s personal details as the registered business
Add an authorized contact
Enter the name, role, email, and mobile phone number of a person authorized to represent the business.
The mobile number must be able to receive verification texts. Do not enter the new dedicated Fieldified number as the contact number.
Prepare the website
The submitted URL must:
- Load without an error
- Clearly represent the registering business
- Show the business name and services
- Use contact information consistent with the application
- Link to the public privacy policy and terms
- Present the SMS opt-in disclosure where phone numbers are collected
A social profile used as business evidence should link to the main public profile, not an individual post or media page.
Build a compliant opt-in
The opt-in must be explicit and optional.
Show:
- Business name
- Message categories
- Expected frequency
- Message and data rate disclosure
STOPopt-out instructionHELPsupport instruction- Privacy-policy and terms links
Do not make text consent a required condition for receiving the underlying service when applicable law prohibits that practice. Promotional consent should use a separate unchecked choice.
Submit the registration
- Open the registration banner or two-way messaging settings.
- Enter the legal business details.
- Select the accurate business type.
- Enter tax and address information.
- Add the authorized contact.
- Add the website and public policy URLs.
- Describe the messaging use case.
- Describe how recipients opt in.
- Add representative sample messages.
- Review names, domains, addresses, and disclosures.
- Submit.
One administrator completes the application; the other administrators can monitor status.
Resolve common rejection reasons
Privacy policy is incomplete
Confirm that it:
- Explains collection and use of personal information
- Covers phone numbers and messaging data
- States the mobile-data sharing restriction
- Explains retention and protection
- Is publicly accessible
See Privacy Notice Requirements for Business Texting.
Terms page is incomplete
Add:
- Business and messaging-program name
- Message purpose
- Frequency
- Carrier-charge disclosure
- Help details
STOPinstructions- Privacy-policy link
See Terms Page Requirements for Business Texting.
Website URL is invalid
Correct typos, use the final public URL, and confirm that the page loads in a private browser window.
Website does not match the business
Align:
- Legal and brand name
- Services
- Address and contact information
- Email domain
- Policy ownership
Business type cannot be verified
Review the legal name, EIN, business type, and authorized contact. Select the structure supported by official records and resubmit.
Opt-in cannot be verified
Make the form public to reviewers and place the full SMS disclosure beside the unchecked consent control. The opt-in description in the application must match the live form.