Onboarding procedure
10DLC Registration
Register the verified political campaign for U.S. A2P 10DLC messaging, establish the appropriate political messaging use case, and provision the Twilio messaging service and phone number needed for launch.
What this step accomplishes
A2P 10DLC registration tells U.S. mobile carriers who is sending messages and what type of messaging program is being operated. Twilio submits the relevant Brand and Campaign information to The Campaign Registry (TCR) as part of this process.
In this registration context, “Brand” means the verified sender organization and “Campaign” means a registered messaging use case. The TCR Campaign is not the same thing as the candidate’s overall election campaign.
For an applicable 527 political organization, the valid Campaign Verify token from Step 2 is associated with the Brand registration. After the Brand is approved and the political use case is available, the messaging Campaign can be submitted for review and connected to a Twilio Messaging Service and U.S. 10DLC phone number.
The objective of Step 3 is to complete the registration layer needed for compliant A2P political messaging while the rest of onboarding—data, CRM, candidate knowledge, and messaging design—continues.
What your campaign provides
- 1
Verified campaign / committee identity
Legal or registered committee name, registration identifiers, EIN or other required identity information, address, website, and authorized representative information as applicable.
- 2
Current Campaign Verify token
The 10DLC CV Token generated in Step 2 for the campaign and intended messaging provider/Brand.
- 3
Messaging-program description
A clear explanation of who will send messages, who the intended recipients are, and why the messages are being sent.
- 4
Consent / message-flow description
The campaign’s approved description of how phone numbers are obtained and how the applicable messaging workflow satisfies current registration and compliance requirements.
- 5
Representative sample messages
At least the sample content needed for registration, aligned with the intended political messaging program and showing the campaign/Brand identity.
- 6
Website and policy information
Campaign website and, where the registration flow requires them, publicly accessible privacy-policy and terms pages or other supporting URLs.
- 7
Program attributes and approvals
Whether messages contain links or phone numbers, requested HELP/STOP behavior, and campaign approval to submit the registration and incur required third-party registration fees.
What FreeMessaging.ai handles
- Select and manage the appropriate Twilio customer / ISV registration architecture for the campaign.
- Create or associate the required Twilio customer compliance profile for the campaign using the campaign’s own identity information.
- Register the A2P Brand and securely import the Campaign Verify token for an applicable 527 political organization.
- Confirm Brand review status and verify that the appropriate Political special use case is available before the messaging Campaign is submitted.
- Prepare the A2P Campaign registration using the approved campaign description, message flow, sample messages, embedded-link/phone-number attributes, and HELP/STOP settings as applicable.
- Create or associate the Twilio Messaging Service and provision the U.S. 10DLC phone number used for the campaign.
- Submit the registration, monitor Twilio/TCR review status, coordinate clarifications or corrections, and document the final verified state.
- Keep the campaign informed of external review timing and begin later onboarding steps in parallel where possible so registration review does not stop data and messaging preparation.
Information to have ready
- Official campaign / committee name and registration information exactly as used in Step 2
- Current 10DLC Campaign Verify token for the correct campaign / provider relationship
- Campaign website and official contact information
- sender, recipient audience, and purpose
- Description of the campaign’s number-acquisition / consent / message flow
- Two to five representative message samples, including campaign/Brand identification
- Indication whether messages can contain links or phone numbers
- Public privacy-policy and terms URLs where required by the registration flow
- Approved opt-out / HELP behavior and keywords where campaign-managed settings are used
- Approval for applicable Twilio/TCR registration charges and the campaign’s planned launch window
What you will see
Twilio customer / compliance profile: The campaign identity used for the A2P 10DLC registration.
A2P Brand: The TCR Brand representing the campaign/committee, including the Campaign Verify association where applicable.
Brand status: The current Brand registration and verification state.
A2P Campaign: The registered political messaging use case, including description, message flow, and sample messages.
Campaign review status: Pending, verified/approved, or a status requiring clarification or correction.
Messaging Service and sender number: The Twilio Messaging Service and U.S. 10DLC phone number associated with the campaign workflow.
Step 4 readiness: Registration identifiers are documented so FreeMessaging.ai can continue with campaign data and CRM setup while final external review is completed.
Watch for
- Campaign or committee identity information does not match Campaign Verify, tax, or official registration records.
- The Campaign Verify token is expired, already used for another Brand, created for the wrong channel/provider relationship, or not successfully imported.
- The campaign description is too vague or does not clearly identify sender, audience, and messaging purpose.
- The message-flow / consent description is incomplete or inconsistent with the campaign’s actual planned workflow.
- Sample messages do not identify the Brand, do not match the registered use case, or omit links/phone-number examples that will appear in production.
- Required website, privacy-policy, or terms information is unavailable or not publicly accessible when needed for the submitted flow.
- The campaign is submitted under the wrong A2P use case or before the Political special use case is available.
- Twilio/TCR manual campaign review remains pending because of external review volume or requires additional information.
What happens next
FreeMessaging.ai does not need to wait for every external review to finish before continuing the internal onboarding work. Once the Brand/Campaign registration has been submitted and the required identifiers are in place, Step 4 — Connect Campaign Contact Data can begin, followed by Voter CRM, Candidate Knowledge Base, and Messaging Design work in parallel where appropriate.
Actual A2P 10DLC sending should not begin until the applicable Twilio/TCR Campaign is approved/verified and the campaign phone number is correctly associated with the registered Messaging Service and sender pool.
Public Knowledge Base note: This procedure describes the FreeMessaging.ai onboarding workflow and is not legal advice. A2P 10DLC, Campaign Verify, TCR, carrier, and Twilio requirements and review times can change; compliance-sensitive details should be checked against current authoritative sources before use.
Source references (reviewed September 2026): Twilio Programmable Messaging and A2P 10DLC; Registration for Government and Nonprofit Agencies (527 political organizations); U.S. A2P 10DLC Registration Guide for Political ISVs; Gather the Required Business Information; A2P 10DLC Registration Application Quickstart.
Questions
What is Step 3 of FreeMessaging.ai onboarding?
Register the verified political campaign for U.S. A2P 10DLC messaging, establish the appropriate political messaging use case, and provision the Twilio messaging service and phone number needed for launch.
Does this step require Odyssey Campaign Services?
No. The nine-step onboarding is part of the standard FreeMessaging.ai service. OCS is optional paid execution support.