Get your campaign ready for texting approval

1. Understand the approval stages

Campaign Verify checks the committee's identity. Its PIN verifies access to a filing contact, and its authorization token is used for political registration. A successful PIN does not approve your website or give you a sending number. Campaign Verify explains the identity and token process.

Telnyx registers the brand and messaging campaign, with carrier review downstream. Your submitted messaging purpose, examples, and opt-in evidence must agree. Sending also requires a registered number assigned to the approved campaign. Payment, a valid token, or a pending registration is not the same as being ready to send. Telnyx campaign registration documentation.

2. Gather your committee information

• Use the committee's legal name, EIN, address, and filing record. Do not substitute a vendor's identity or a candidate nickname for the legal committee.
• Have your FEC ID for a federal committee, or the relevant state, local, or tribal registration details and public filing URL. Follow the field hints in Compliance for your registration type.
• Confirm who can access the filing contact's email or phone before selecting a verification method. Keep the campaign support email monitored.
• Use a working campaign website that identifies the committee. Decide what texts you will actually send, including whether they solicit donations.

Save the profile in Texting & Calls → Compliance. Saving is not submission. Prepare the website and policy pages before completing the registration steps that send your campaign to Telnyx.

3. Prepare your website and opt-in form

The live form needs a labeled phone input and an optional, initially unchecked SMS checkbox. Keep SMS permission separate from email, calls, and acceptance of terms. A visitor must be able to submit without opting into texts. Show the message purpose, sender, frequency, charges, STOP/HELP instructions, and mobile-data sharing disclosure next to the checkbox. Link working policy pages and make the submission actually save consent. See Telnyx's form requirements and visual example.

Using the MyCampaign form

1. Review and publish both SMS policy documents in Compliance.
2. Open Opt-in Forms. Check the heading, campaign brand, and website origins. Publish the form; a draft is not public approval evidence.
3. Copy the embed snippet and give it to your website developer. Install it on the campaign website at the location reviewers will visit.
4. Inspect the actual live form. The built-in template is a starting point, not an approval certificate. Check it against this guide, especially explicit political message types, mobile-data sharing language, and any fundraising disclosure. Ask MyCampaign support for help if the editor cannot express your required disclosures.
5. Open the website in a signed-out/private window on desktop and mobile. Check the entire form is visible, its links work, and the embed is not clipped or blocked. Using a number you control, test both checked and unchecked submissions and verify that only the checked submission records SMS permission.

You can also use a form built by your website team. It needs the same disclosures and consent records. Publishing a new form does not retroactively give permission to text existing email subscribers or imported contacts.

4. SMS consent language example

For your website developer: place wording like this beside the optional SMS checkbox. Replace every bracketed placeholder, use actual message types, and turn both policy references into clickable links. Have your compliance lead review it against your program; this example does not change your live form.

If the program solicits donations, add “Donations may be solicited.” and describe that purpose consistently in the registration. Do not promise an informational-only program and then send fundraising texts. Telnyx's message-flow guide covers political and fundraising disclosures.

5. Publish your privacy policy and SMS terms

In Compliance, use the policy editor to review the drafts before publishing. Generated text needs your committee's review; a published badge alone does not mean Telnyx has accepted it.

• Privacy: identify your committee and actual data practices. Protect mobile information and SMS consent from sale or sharing for third-party marketing, including affiliates. Broad sharing clauses elsewhere must not contradict that protection.
• SMS terms: describe the named program, message types, frequency, applicable messaging/data charges, how to stop texts, and a working support contact.
• Access: link the committee's policies from the form, not just a vendor's generic privacy page. Open each link while signed out and check for placeholder text, broken links, or a login requirement.

Give support both policy URLs with your evidence; Telnyx requires those links in the registration as well as on the website. Telnyx's compliance guide explains policy and registration requirements.

6. Prepare the evidence reviewers need

Send support a small evidence package before requesting a correction to your submission:

• The exact public opt-in URL and where the form appears, including any navigation or pop-up steps.
• A screenshot of the real live form showing the phone field, unchecked checkbox, complete disclosure, policy links, and submit button. Use a publicly viewable link without exposing a supporter's personal information.
• The privacy and terms URLs, your intended message types, and whether fundraising is included.
• A plain-language account of how consent is recorded. Keep the submitted wording aligned with what visitors actually experience.

An evidence screenshot supplements the real workflow; it is not a substitute for implementing it. For paper, verbal, or keyword opt-in, ask support to document that actual method rather than describing a nonexistent web checkbox. Telnyx's review checklist and message-flow guidance explain the evidence expected.

7. Complete registration in MyCampaign

1. In Compliance, save the completed legal profile and review the registration fee shown. Use Pay & submit, or Resume payment if your checkout is already pending.
2. Follow the Campaign Verify status. When prompted, enter the received code using Verify PIN. Use Refresh status to check progress instead of starting another registration.
3. When offered, select Create and validate 10DLC token. If the committee is already verified elsewhere, use the existing-token option with a token issued for this provider and follow the payment instructions shown. A PIN is not an authorization token; do not put either in public screenshots.
4. Track the separate Telnyx status. If it needs review, read the reason before taking another action. Keep your form and policy pages accessible during and after review.

Buttons depend on your status and permissions; ask an organization manager if the required controls are unavailable. Provider review is asynchronous. Do not plan a launch around an assumed approval deadline.

8. Resolve rejections and retry safely

“Add a link/screenshot of the opt-in form” or email-only form

Fix the actual website form first using the website checklist. Then confirm the submission points to it. Merely publishing a draft in MyCampaign, adding a phone field without SMS consent, or retrying the unchanged homepage will not address this rejection.

Campaign Verify succeeded, but Telnyx needs platform review

These are separate stages. Copy the full Telnyx reason and send it to MyCampaign support with your organization URL and evidence links. Brand, token, number-assignment, and content problems need different corrections; do not redo the PIN or pay for another identity verification simply because Telnyx rejected the campaign.

After the underlying problem is corrected

Use Compliance → Resubmit to Telnyx when available. Read the confirmation: provider fees may apply. This uses the existing verified setup to request a replacement for a rejected messaging campaign; it is not a new registration checkout. Website updates alone do not edit an already-submitted campaign. Telnyx documents rejected-campaign resubmission.

“Could not confirm the Telnyx resubmission”

An uncertain response is not proof that submission failed. Wait the indicated 10 minutes, then use the same Resubmit to Telnyx action to recover the attempt. Do not create a second registration. If it stays unresolved, send support the exact message and approximate attempt time.

9. Final checks before sending

• Confirm MyCampaign reports active Telnyx registration and an assigned, registered sending number. Escalate missing-number errors to support.
• Check the opt-in form and both policy links again after any website deployment.
• Use only an audience with permission appropriate to your program. A voter file, phone-number match, or email subscription alone is not evidence of SMS opt-in.
• Run a small test with people who agreed to participate. Verify receipt, inbound replies, HELP, and STOP suppression before launching to the full audience.
• Keep consent records and send content consistent with the approved program. Resolve new registration or delivery failures before expanding the send.

This guide covers political SMS registration in Texting & Calls, not approval of a calling program or every legal obligation. Return to your original MyCampaign tab to continue setup or open your organization's Support page for help.