Question 1

What is Political Comms?

Accepted Answer

Political Comms is a non-partisan, enterprise-grade political messaging platform built for compliant, large-scale SMS, MMS, and RCS delivery. It serves political campaigns, PACs, advocacy organizations, fundraisers, elected officials, and political consultants across the United States.

Question 2

What does direct-to-carrier mean and why does it matter?

Accepted Answer

Direct-to-carrier means Political Comms maintains its own carrier and aggregator relationships rather than reselling another vendor’s pool. The practical effect is shorter delivery paths, lower filtering risk, and per-brand opt-out isolation rather than aggregator-pool propagation.

Question 3

What geographies are supported?

Accepted Answer

The United States. The carrier compliance model is built around U.S. carrier and TCR requirements.

Question 4

How large can a single send be?

Accepted Answer

The platform is engineered for the burst traffic profile of political work, including GOTV pushes, debate-night responses, and Election Day surges. Customers regularly run multi-million-recipient sends and observe sustained delivery at peak. Specific throughput targets are documented in the developer reference.

Question 5

Who founded Political Comms?

Accepted Answer

Hunter Lamirande founded Political Comms in 2019 to modernize political messaging infrastructure with a focus on scale, transparency, and compliance.

Question 6

How does billing work?

Accepted Answer

Usage-based. SMS, MMS, RCS, and carrier-specific surcharges are itemized rather than blended. Pricing starts at $0.018 per SMS. Use the calculator at politicalcomms.com/pricing to model real volumes.

Question 7

Are there setup fees?

Accepted Answer

No setup fees on standard accounts. 10DLC and Campaign Verify carry their own carrier-side fees; these are passed through at cost and itemized.

Question 8

Are there volume discounts?

Accepted Answer

Yes. Volume discounts apply automatically in the calculator and are formalized in annual prepay arrangements.

Question 9

How are MMS messages priced?

Accepted Answer

MMS rates are itemized separately from SMS. Carrier surcharges where they exist are passed through at cost. The pricing calculator returns concrete numbers against actual message mix.

Question 10

Are carrier and registration fees passed through?

Accepted Answer

Yes, at cost and itemized on every invoice. 10DLC brand and campaign registration fees, Campaign Verify token fees, and any carrier-specific surcharges show up as separate line items so finance teams can reconcile against the actual cost basis.

Question 11

Does Political Comms register 10DLC brands and campaigns?

Accepted Answer

Yes. Brand registration goes through The Campaign Registry (TCR). Campaign registration carries political vertical attributes and is reviewed alongside Campaign Verify when applicable.

Question 12

How long does 10DLC registration take?

Accepted Answer

Typically 24 to 48 hours. The platform pre-populates required fields, validates inputs before submission, and surfaces TCR status in the operator dashboard the moment it changes.

Question 13

What is Campaign Verify and do you support it?

Accepted Answer

Campaign Verify is the political identity verification standard for 10DLC. Yes, we support it. Federal pathway and state, local, and tribal pathway are both available. Approval typically completes in two to three hours on weekdays.

Question 14

Does the platform handle TCPA compliance?

Accepted Answer

The platform captures opt-in records with audit metadata, enforces quiet hours, handles HELP and STOP keywords, and isolates opt-outs to the originating brand. Operators retain responsibility for the content and consent posture of their programs.

Question 15

How does opt-out isolation work?

Accepted Answer

Opt-outs are bound to the brand that triggered them rather than propagating across an aggregator pool. A recipient who replies STOP to Brand A does not stop receiving messages from Brand B run by the same operator. This preserves legitimate communication channels while honoring every individual opt-out.

Question 16

Can the same Campaign Verify token go on multiple brands?

Accepted Answer

No. Each Campaign Verify token is bound to a single brand. Operators running multiple brands need a submission per brand. The workflow is identical and pre-fills contact information across brands.

Question 17

What happens when a Campaign Verify token expires?

Accepted Answer

Tokens expire on Campaign Verify’s schedule. Renewal requires a fresh submission. The platform does not auto-renew. Submission detail pages show expiration timestamps so operators know when to refile.

Question 18

Which voter files are supported?

Accepted Answer

Any voter file. The platform accepts contact list imports from any source through the contacts API and the in-app uploader. L2 has a native integration on top of that for direct lookup, targeting, suppression, and list hygiene.

Question 19

Which CRMs are supported?

Accepted Answer

The platform integrates with most political CRMs via REST and webhooks. A maintained list of direct integrations lives in the developer reference.

Question 20

Where can I export my data?

Accepted Answer

In two ways. Reports are downloadable directly from the application for on-demand pulls. For continuous delivery, scheduled exports run to AWS S3, Snowflake, or Databricks. All three destinations share the same schedule, schema, and writer substrate. S3 is the native target; Snowflake and Databricks layer on top.

Question 21

How are exports authenticated?

Accepted Answer

AWS S3 exports use a customer-supplied IAM role with cross-account access scoped to the export bucket. Snowflake and Databricks exports inherit that pattern through the S3 substrate or use direct ingestion credentials provided by the warehouse.

Question 22

Is there an OpenAPI specification?

Accepted Answer

Yes. The OpenAPI 3.1 specification is published at docs.politicalcomms.com/api-reference/openapi.json. The base URL is https://api.politicalcomms.com/v1.

Question 23

Are webhooks signed?

Accepted Answer

Yes. Every webhook delivery includes an HMAC signature with a per-endpoint secret. Retries follow exponential backoff up to 72 hours. Each event includes a unique ID so replays are safe.

Question 24

Is the platform SOC 2 audited?

Accepted Answer

SOC 2 Type II audit is in progress. The full security posture is documented at politicalcomms.com/security.

Question 25

How is data encrypted?

Accepted Answer

AES-256 encryption for data at rest. TLS 1.2+ for data in transit. Per-customer data isolation at the application layer.

Question 26

Where is data stored?

Accepted Answer

AWS regions in the United States with multi-AZ failover. Customer data is isolated at the application layer with role-based access control for operators.

Question 27

How do I report a security vulnerability?

Accepted Answer

Email security@politicalcomms.com. The responsible disclosure policy and Acknowledged Researcher list are at politicalcomms.com/.well-known/security.txt and politicalcomms.com/security.

Question 28

How long is message data retained?

Accepted Answer

Message and event retention windows depend on contract tier and compliance requirements for the operator’s program. Default retention covers the operational and audit needs of a full election cycle. Custom retention is negotiable for enterprise accounts.

Question 29

Does Political Comms read customer messages?

Accepted Answer

No. Message content is treated as customer data. Access is limited to authorized operations and support functions and audit-logged when used to resolve a specific support request.

Question 30

How long does onboarding take?

Accepted Answer

Usually 48 hours. 10DLC brand and campaign registration run in parallel with platform configuration. Most teams send their first production message inside the first few days.

Question 31

Is training provided?

Accepted Answer

Yes. Customer success works with operators through brand setup, first campaigns, and ongoing program reviews. Office hours are available for technical integrations.

Question 32

Can I migrate from another platform?

Accepted Answer

Yes. The platform supports brand and campaign re-registration where required, bulk contact and consent imports, and webhook re-subscription. Migrations typically complete inside two weeks once 10DLC re-registration clears.

Question 33

Do you support white-label and reseller arrangements?

Accepted Answer

Yes. The partners track at politicalcomms.com/partners covers resell and white-label deployments. Qualification criteria, onboarding timeline, and commercial terms are documented on that page.

Question 34

What are your support hours?

Accepted Answer

Standard support is available during U.S. business hours. Programs running into peak election windows are eligible for extended coverage including overnight and weekend support during the final 72 hours before Election Day.

Question 35

How do I get technical support?

Accepted Answer

Email support@politicalcomms.com or use the in-app support channel from app.politicalcomms.com. The team typically responds within the hour during U.S. business hours, and dedicated Slack channels are available for high-volume programs running into peak election windows.

Question 36

What other contact channels are available?

Accepted Answer

sales@politicalcomms.com for new business, press@politicalcomms.com for media, partners@politicalcomms.com for partnership inquiries, privacy@politicalcomms.com for privacy requests, legal@politicalcomms.com for legal, and security@politicalcomms.com for responsible disclosure.

Question 37

How fast does support respond?

Accepted Answer

The team typically replies within the hour during U.S. business hours. Election-cycle programs are covered overnight and on weekends through the final 72 hours before Election Day. Platform availability targets are documented in the security center.

Answered before you have to ask.

About the platform

Pricing

Compliance

Integrations

Security and data

Onboarding

Support

Question we did not answer?