Political Campaign and GOTV Messaging: A Buyer Guide for the 2026 US Cycle

Every US election cycle, the same search spike lands on the same unanswerable forum threads: "political texting rules." The rules are answerable. They are just scattered across TCR vetting, the SHAFT content standard, FEC disclaimer practice, and per-carrier throughput tiers. With the 2026 midterm general election on November 3, this guide collects the buyer-side answer in one place: how each political sender type gets vetted, what each content class must say, how GOTV and non-commercial advocacy sit inside SHAFT, how to plan election-night throughput against your registered tier, and which controls you own on the platform. Every control named here is a tenant-owned setting in Devotel Orbit. The final decision on any message still belongs to the carrier, aggregator, or review body looking at your traffic, and this guide is not legal advice.

Campaign brand, PAC, and party vetting on 10DLC

TCR does not review "political texting" as one bucket. It reviews a brand, a campaign use case, and the sample messages you file against that use case, and it treats the sender's legal identity as the first fact in the file. Campaign brands (a candidate's authorized committee), separate segregated funds and nonconnected PACs, and party committees carry different registration documents, and the mismatch between the legal name on the EIN and the name on the brand is still the most common rejection in the category, as our field notes on 10DLC campaign rejections and TCR vetting document.

What TCR asks for, in practice:

The entity's legal name and EIN, matching IRS records exactly. A committee's FEC registration name and its IRS name can drift; file the IRS version.
A stated use case that matches the traffic. Political traffic filed under a generic marketing or mixed-use class is a rejection when caught at filing and a de-registration when caught after. Route it under the political campaign use case from the first submission.
Sample messages that already carry the compliance furniture. Reviewers read your samples as a contract: the disclaimer, the opt-out language, the identification of the sender, and (for solicitation) the pay-to-play mechanics all need to appear in the samples, because the samples define what you are allowed to send.
Verification tokens where the ecosystem demands them. Campaign Verify authorization is the standing proof that the entity sending is the entity it claims to be; programs that arrive without it when their class expects it stall in manual review.

Rejection patterns in this vertical repeat: EIN/name mismatch, samples missing the "paid for by" line, samples missing opt-out language, and political traffic discovered on a non-political brand after approval. The appeal path is the same one commercial brands use, resubmission with corrected documents, and the per-carrier status split matters: a CSP-level approval does not mean every carrier family has cleared you, so watch the per-carrier statuses, not just the campaign-level one.

Party committees and PACs should register separate brands where their legal identities are separate. Sharing one brand across a candidate committee and its affiliated PAC compresses two registration postures into one file and inherits the strictest review of the two.

Participation vs. non-participation content classes, and the disclaimers each carries

Draw the line the way the regs draw it: participation content urges the election or defeat of a named candidate or clearly identified ballot measure; non-participation content (classic GOTV, poll information, civic reminders) does not. The content class decides the disclaimer stack.

Participation content carries the FEC-style "paid for by" disclaimer on the message itself, plus the committee's identity and opt-out language. A working shape:

> Sam, Adriana Ramirez for State Senate here. Early voting starts Oct 24 in your county. Volunteer shifts: adrianaramirez.example/volunteer. Paid for by Ramirez for State Senate. Reply STOP to unsubscribe, HELP for help.

And for contribution solicitation, where the send asks for money, the sample and the live traffic add the solicitation mechanics your counsel signs off on (the voluntary-against-federal-limits language applies to federal committees; state committees follow state disclosure law):

> Sam, Adriana Ramirez for State Senate here. Our field program runs on small gifts from neighbors: adrianaramirez.example/contribute. Paid for by Ramirez for State Senate. Reply STOP to unsubscribe, HELP for help.

The .example domain marks the placeholder: file and send with the campaign domain you actually own, because sample-to-live-message drift is itself a vetting rejection.

Non-participation GOTV and civic content carries no "paid for by" line, but it is not disclaimer-free. The sender identifies itself by name, states message frequency, and carries the same opt-out mechanics:

> Jordan, this is Civic Engagement Now. Polls in your county are open 7am to 8pm on Tue Nov 3. Find your polling place: vote.org. Msg freq varies. Reply STOP to opt out, HELP for info.

Three rules hold across both classes. Opt-out language is not optional on any application-to-person political traffic; "STOP" must work the moment it arrives. The sender name in the first words of the message is the identification the carriers' filters and the complaint desks actually look at. And the sample bodies you file with TCR are the ceiling of what you send: a live message that adds a claim, a link pattern, or a solicitation mechanic your samples never showed is a use-case mismatch discovered the expensive way.

SHAFT nuance for GOTV and non-commercial advocacy

SHAFT (sex, hate, alcohol, firearms, tobacco) is a content standard, and political speech is not a SHAFT category. The nuance our restricted industries and SHAFT buyer guide works through in its Political & advocacy section is that political programs still fail on the adjacent rails: a GOTV message that references a ballot measure about firearms or alcohol inherits that vertical's restrictions; advocacy content that promotes hate or election misinformation is prohibited outright, commercial or not; and nonpartisan does not mean unregistered, because the carriers vet the traffic class, not the intent behind it.

The posture that survives review is the documented-consent posture: every recipient on a political list traces to an opt-in that names the organization sending, the consent record is retained, and the message it authorizes is bound to it. File GOTV traffic under the campaign or advocacy class that matches it, keep the consent-required gate on so nothing sends without a consent record on file, and set quiet hours to the recipient's local time. Nonpartisan organizations should resist the temptation to borrow a party's or campaign's registered sender because the schedules collide; the registration is tied to the entity and its stated use case.

Peak-night throughput: segment sizes against your registered tier

Election-night failures are arithmetic failures. US 10DLC throughput is set per number per day by vetting tier (sole proprietors and low-volume standard campaigns sit at the bottom of the ladder; higher vetting scores open higher tiers), and a campaign that builds a 40,000-recipient GOTV segment on a sender registered for a few thousand messages a day will watch the queue pace, not the clock. Do the math before the calendar does it for you: recipient count divided by your registered per-day throughput is the number of days the blast takes, and peak night does not grant extra days. If the arithmetic fails, the fixes are the honest ones: register the throughput your plan needs during the vetting window, spread the send across the registered senders you legitimately operate, or cut the segment to the audience that actually decides the race. Our 10DLC rejections field notes carry the per-tier numbers, and the bulk broadcast checklist walks the queue-pacing side.

The second peak-night rule: keep one suppression list. Rapid-fire blasts across the final weekend are exactly where programs split their audience into ad-hoc segments and lose the opt-outs. A STOP collected at 9pm on the first blast must exclude that recipient from the 7am reminder, the poll-opening message, and the closing-time push. Orbit's suppression surface is shared across sends on the tenant, so the discipline is to keep every GOTV segment drawn from lists that inherit the same suppression scope, and to scrub imported lists against it before the first send, not after the first complaint.

State overlay laws add the third rule: some states run calling and texting windows on top of the federal baseline, and the calendar moves through H2 2026. The post-vacated TCPA state-overlay calendar is the date-anchored list; the operational consequence for peak night is that "send when the polls close" is not a rule you get to write yourself in every state.

The tenant-owned controls checklist

Before the first political send of the cycle, the posture lives in six tenant settings:

Consent basis per list. Each list carries its opt-in source, and the opt-in names the organization that sends. The consent-required gate blocks sends that have no consent record behind them.
Quiet hours on recipient local time, with a documented urgent-traffic policy. Urgent election-day traffic (a polling-place change, a schedule correction) runs as its own narrow list with its own documented send window and consent basis, not as an ad-hoc override bolted onto the whole program.
STOP propagation. Opt-outs apply tenant-wide across the program's senders on the tenant; verify the propagation before peak night, not during it.
Frequency caps. Caps are what keep a five-blast final week from reading as harassment to the recipient and as a complaint spike to the carriers.
The 10DLC campaign class filed per sender. Political traffic on political registrations, GOTV on its matching class, and no sender shared across entities that are legally distinct.
The content policy scanner on the political senders. A last-look pass that catches a drifted claim or a missing disclaimer at dispatch, before a carrier filter does.

Honest limits: the platform enforces posture, the sender owns legality

Draw the line clearly, because buyers ask. Orbit enforces the posture you configure: the quiet hours you set, the consent gate you turn on, the suppression scope you maintain, the frequency caps you choose, and the pacing your registered throughput allows. What Orbit does not do is decide that your campaign is legal. Disclaimer adequacy, contribution solicitation rules, blackout windows, state disclosure law, and whether a given message is participation or non-participation content are the sender's call, made with counsel, and the carrier and the regulator review that call after the fact. A platform that promises to make legality decisions for you is a platform telling you what it will not be checked on. The buyer-guide question worth asking every vendor in this cycle is the one this guide has answered all the way down: show me the controls I own, and show me exactly which decisions stay mine.

Frequently asked questions

Does a nonpartisan GOTV program need the political campaign registration?

It needs a registration whose use case matches the traffic. GOTV and civic-engagement traffic files under the advocacy or campaign class that describes it; the failure pattern is nonpartisan traffic squeezed through a generic marketing class, which reads as a use-case mismatch at vetting. The consent posture is the same as the participation posture: opt-ins that name the organization, retained, and bound to the messages.

Who exactly must the "paid for by" disclaimer name?

The committee or entity responsible for the message, by its registered legal name: "Paid for by Ramirez for State Senate," not the vendor, not the platform, and not a dba that differs from the filing. State disclosure law sets the exact wording for state races; the carriers' interest is that the sender is identifiable and that the disclaimer appeared in your filed samples.

Can we reuse one suppression list across a campaign, its PAC, and our GOTV nonprofit?

One suppression list per tenant is the floor, and the safer practice across legally distinct entities is to honor every opt-out everywhere the recipient could reasonably believe the same organization is sending. A STOP collected by the campaign that the affiliated PAC ignores is a complaint with your name on it, regardless of which entity's letterhead the message carries.

Our segment is bigger than our registered throughput. What are the honest options?

Register for the tier the plan needs while the vetting window is still open, spread the send across senders you legitimately operate and have registered, or cut the segment. Buying or borrowing throughput outside your registration is not an option the ecosystem offers; queues pace to the registered tier, and filter-evasion schemes are de-registrations waiting to happen.

Who is liable if a message violates campaign law?

The sender. The platform enforces the posture you configure and the carriers enforce their content standards; campaign-finance legality, disclaimer adequacy, and solicitation rules are the committee's responsibility with its counsel. This guide documents the controls, not the law.