10DLC Requirements
Form Requirements
At minimum: Name field and Phone Number field.
A checkbox at the bottom of the form that is not pre-checked.
Ensure only ONE of the following fields are required, if any:
Checkbox
Phone Number Field
Consent Language (CTA)
Place the following statement next to the checkbox:
"By checking this box and submitting this form, I agree to receiving [USE CASE] SMS messages from [BUSINESS NAME]. Message frequency varies. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help. I agree with the privacy policy [hyperlink] and terms of use [hyperlink]."
Legal Pages
Terms of Use page.
Privacy Policy page — must include the following sentence:
"No mobile information will be shared or sold to third parties for marketing or promotional purposes."
Toll-Free Number (TFN) Requirements
Form Requirements
At minimum: Name field and Phone Number field.
A minimum of two checkboxes at the bottom of the form that are not pre-checked.
Ensure only ONE of the following fields are required, if any:
Checkbox
Phone Number Field
Consent Language (next to checkboxes)
Checkbox 1: "By checking this box and submitting this form, I agree to receiving [USE CASE] SMS messages from [BUSINESS NAME]. Message frequency varies. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help."
Checkbox 2: "I agree with the privacy policy [hyperlink] and terms of use [hyperlink]."
Legal Pages
Terms of Use page.
Privacy Policy page — must include the following sentence:
"No mobile information will be shared or sold to third parties for marketing or promotional purposes."
*A new checkbox and CTA is required for each unique Use Case for TFNs
Short Code (SC) Requirements
Form Requirements
At minimum: Name field and Phone Number field.
A minimum of two checkboxes at the bottom of the form that are not pre-checked.
Ensure only ONE of the following fields are required, if any:
Checkbox
Phone Number Field
Consent Language (next to checkboxes)
Checkbox 1: "By checking this box and submitting this form, I agree to receiving [USE CASE] SMS messages from [BUSINESS NAME]. Message frequency varies. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help."
Checkbox 2: "I agree with the privacy policy [hyperlink] and terms of use [hyperlink]."
Legal Pages
Terms of Use page.
Privacy Policy page — must include the following sentence:
"No mobile information will be shared or sold to third parties for marketing or promotional purposes."
Additional SC-Specific Requirements when completing the Registration Form
A new checkbox and CTA is required for each unique Use Case
The contact email address must match the domain of the legal organization (the name associated with the EIN).
The address listed in the application must match:
The address associated with the EIN.
The address displayed on the website.
The company name associated with the EIN should match the domain name. If different:
Provide a registered DBA showing the relationship between the two names, along with a Business License or Articles of Incorporation.
OR obtain a new EIN associated with the domain name.
Short Code Best Practices
Do not purchase domains from NameCheap or free domain providers.
Providers review domain age — older domains are preferred.
Fully build out the website with detailed, authentic business information.
Carriers check for website traffic — ensure your site has activity before applying.
After approval, opt-out rates must remain below 2% to avoid audits
Reasons for Short Code Denials (Examples)
Website traffic is near zero
Limited information on the website
Address mismatch between website, EIN, and application (can trigger spam flags)
Domain purchased from NameCheap
Overall Notes for All Number Types
Once the Volt team reviews your completed site and registration, additional minor changes may be recommended.
The USE CASE in your CTA must match one of the approved options from The Campaign Registry (TCR). Here are a few common examples:
Marketing – Promotional or sales-focused messages aimed at driving revenue or customer engagement. (e.g., sales, offers, marketing content)
Customer Care – Service-related responses or outreach for existing customers. (e.g., appointment reminders, order follow-ups, support, feedback, service updates)
Account Notification – Informational updates about an account. (e.g., balance updates, changes in service, account alerts)
Transactional Messages – Non-promotional messages that complete a process or confirm an action. (e.g., account alerts, OTPs, confirmation messages)
Promotional Messages – Content intended to market products or services. (e.g., sales, offers, marketing campaigns)
2FA (Two-Factor Authentication) – Messages that deliver one-time passcodes or authentication links for secure account login or verification. (e.g., OTP codes, login links)
Polling and Voting – Requests for participation in surveys, polls, or official voting. (e.g., feedback surveys, political or non-political voting requests)
The information in this document is provided for general guidance only and does not constitute legal advice. Compliance requirements for phone number approval, messaging campaigns, and website content are subject to change based on carrier policies, regulatory updates, and The Campaign Registry (TCR) guidelines. It is the customer’s responsibility to verify that all campaign details and website content meet current requirements before submission. Our company assumes no liability for delays, rejections, or penalties resulting from non-compliance.