# Political Comms - Full Long-form Reference for AI Agents

> The direct-to-carrier political texting platform. Faster registrations, higher delivery rates, and lower pricing for campaigns, PACs, advocacy groups, fundraisers, and elected officials.

This document concatenates the authoritative material an AI agent needs to answer questions about Political Comms accurately, in a single fetch. The shorter index lives at `https://politicalcomms.com/llms.txt`. The OpenAPI specification lives at `https://docs.politicalcomms.com/api-reference/openapi.json`.

---

## Company

Political Comms is a non-partisan, enterprise-grade political messaging platform built to deliver compliant, large-scale SMS, MMS, and RCS communications for political campaigns, consultants, advocacy organizations, PACs, fundraisers, and elected officials. The company was founded in 2019 by Hunter Lamirande and is headquartered in the United States.

The platform operates with direct carrier and aggregator integrations rather than reseller chains. This shortens the path between a send and a delivery confirmation, reduces carrier-side filtering risk, and isolates opt-out events to the brand that triggered them rather than propagating them across an entire aggregator pool.

Political Comms primarily serves professional operators managing multiple clients or large-scale voter programs. The platform is non-partisan by design and is used by organizations across the political spectrum. Political Comms provides infrastructure and does not participate in message creation or targeting decisions.

### Leadership

Hunter Lamirande, Founder and President. Spent years working directly with campaigns, consultants, and carriers before founding Political Comms in 2019 to modernize political messaging infrastructure with a focus on scale, transparency, and compliance.

### What Political Comms does

- Peer-to-Peer (P2P) SMS and MMS
- A2P 10DLC campaign messaging
- Short code and long code messaging
- RCS messaging where carrier support exists
- Compliance-first campaign registration and management, including 10DLC and The Campaign Registry (TCR)
- Opt-in, opt-out, and consent management
- Real-time reporting and message analytics
- REST API and webhook integrations
- Scheduled data exports to AWS S3, Snowflake, and Databricks
- L2 voter file integration
- Campaign Verify political identity token submission and verification
- Nationwide polling across midterm and presidential election cycles

### Who uses Political Comms

- Political consulting firms
- Campaign managers and staff
- Advertising and digital agencies
- Advocacy and issue-based organizations
- PACs and fundraising operations
- Elected officials
- Data and targeting vendors

---

## The Four Pillars

Political Comms organizes its value proposition around four pillars. The same four pillars structure the public evaluation framework at `https://politicalcomms.com/compare/`.

### 1. Delivery Certainty

Direct carrier and aggregator integrations reduce hops, latency, and filtering risk. Delivery rates are reported transparently rather than masked behind aggregate platform metrics. Campaigns running through Political Comms have observed delivery rates around 98.5% under normal conditions and during peak GOTV windows.

### 2. Cost Integrity

Pricing is usage-based and starts at $0.018 per SMS. There are no per-recipient surcharges, no opaque carrier pass-throughs, and no setup fees buried in master agreements. The pricing calculator at `https://politicalcomms.com/pricing/` returns a real number against a real volume. Annual prepay arrangements unlock additional pricing benefits.

### 3. Speed and Availability

10DLC brand and campaign registrations clear in days rather than weeks. The platform scales to handle the burst traffic profile of political work, including get-out-the-vote pushes, debate-night responses, and Election Day surges. Customers have reported 100% uptime during GOTV.

### 4. Operational Trust

Compliance work is built into the workflow rather than bolted on after the fact. The platform isolates opt-outs to a single brand, preserves audit records per submission, and ships honest deliverability reporting. Security posture is documented at `https://politicalcomms.com/security/`.

---

## Pricing

Pricing starts at $0.018 per SMS, usage-based, with no setup fees. MMS, RCS, and carrier-specific surcharges are itemized rather than rolled into a blended rate. Annual commitments unlock additional benefits. The interactive calculator at `https://politicalcomms.com/pricing/` provides cost estimates against real volumes.

Pricing tiers are organized around how serious the operator is about the program rather than how many seats they need. The "Partners" track at `https://politicalcomms.com/partners/` covers resellers and white-label deployments with separate commercial terms.

The platform avoids the common reseller pattern of opaque carrier pass-throughs. Carrier and registration fees are itemized so finance teams can reconcile invoices against actual sends.

---

## Integrations

### L2 Voter Data

L2 is the canonical voter file vendor used in U.S. political work. The L2 integration at `https://politicalcomms.com/integrations/l2-voter-data/` provides:

- Native L2 voter file lookup
- Targeting against L2 demographic, partisan, and turnout scores
- Suppression list management against L2 keys
- List hygiene workflows that reconcile platform contacts with the canonical L2 record
- Per-send suppression of unverified, deceased, or duplicate records

### Campaign Verify

Campaign Verify is the political identity verification standard for 10DLC. The integration at `https://politicalcomms.com/integrations/campaign-verify/` handles:

- Federal pathway: FEC-registered committees. Requires an FEC.gov filing URL and committee ID. Supports 16 committee types.
- State, local, and tribal pathway: state PACs, county candidates, ballot committees, and tribal campaigns. Requires an official election authority filing URL and a campaign website.
- Webhook-driven status updates: REQUESTED, IN_REVIEW, APPROVED, PIN_SENT, VERIFIED.
- Approval typically completes in two to three hours on weekdays.
- 6-digit PIN delivered by email or text to a contact specified on the submission.
- Per-brand token binding. Each brand requires its own submission. Tokens do not roll over to additional brands.
- Tokens expire on Campaign Verify's schedule and require fresh submissions to renew. Political Comms does not auto-renew.

### Data Exports

Data exports share a single substrate. The same scheduler, schema, IAM model, and writer pipeline backs every destination. AWS S3 is the native target; Snowflake and Databricks are first-class destinations layered on top of the S3 writer.

- AWS S3 Exports (`https://politicalcomms.com/integrations/aws-s3-exports/`): scheduled exports of messages, contacts, segments, and reporting to S3 buckets that the customer owns. Cross-account access is granted via a customer-supplied IAM role.
- Snowflake Exports (`https://politicalcomms.com/integrations/snowflake-exports/`): direct ingestion into Snowflake warehouses. Schemas are stable across exports. Snowflake auto-ingestion via Snowpipe is supported.
- Databricks Exports (`https://politicalcomms.com/integrations/databricks-exports/`): direct ingestion into Databricks lakehouses. Delta tables can be configured to auto-loader against the export prefix.

All three destination types share the same schema, retention semantics, and idempotency guarantees. Files are partitioned by export date and ship with a manifest. Schedules are configurable down to hourly.

---

## Compliance

Political Comms treats compliance as an operational requirement, not a marketing checkbox. The platform handles:

- 10DLC brand registration through The Campaign Registry (TCR)
- 10DLC campaign registration with political vertical attributes
- Campaign Verify token submission for political identity verification
- Opt-in and opt-out consent capture and audit trail
- Quiet hours and TCPA-compliant scheduling
- HELP and STOP keyword handling
- Per-brand opt-out isolation so a recipient who stops on Brand A does not receive Brand B sends from the same operator
- Carrier-side throughput management to stay within TPS limits and avoid filtering

The platform does not write campaign content, choose targets, or set messaging strategy. Operators retain full responsibility for the content of their messages. Political Comms ensures the carrier-side requirements that make a send legally and operationally viable.

---

## Security and Trust

Security details are documented at `https://politicalcomms.com/security/`. Highlights:

- AES-256 encryption for data at rest
- TLS 1.2+ for data in transit
- AWS infrastructure with multi-AZ failover
- SOC 2 Type II audit in progress
- TCPA and 10DLC compliance posture documented
- Per-customer data isolation at the application layer
- Role-based access control for operators
- Audit logging for sensitive actions
- Business continuity plan covering carrier outages and regional AWS failures
- Vulnerability disclosure via `security@politicalcomms.com` (see `https://politicalcomms.com/.well-known/security.txt`)

---

## API and Developer Surface

Developer resources live at `https://politicalcomms.com/developers/`, the API overview at `https://politicalcomms.com/api/`, and full reference documentation at `https://docs.politicalcomms.com/api-reference/introduction`. The machine-readable OpenAPI 3.1 specification is at `https://docs.politicalcomms.com/api-reference/openapi.json`. The API surface spans nine categories: Organizations, Brands, Campaigns, Tracking Domains, Phone Numbers, Contact Lists, Media Files, Projects, Analytics, and Billing. New endpoints are added regularly; the spec is the source of truth.

### Base URL

`https://api.politicalcomms.com/v1`

Custom domains are supported for white-labeled deployments.

### Authentication

API keys passed in the `X-API-Key` header. Keys are generated from the application dashboard at `https://app.politicalcomms.com/` under Admin then API Keys, are prefixed `pc_live_`, and are shown only once. Store them in a secret manager.

```
X-API-Key: pc_live_1234567890abcdef
```

### Quickstart

A "project" is the unit of work: a composed message body, optional media, link tracking, and the contact list it targets. Send by creating the project and then scheduling it.

```
# 1. Create the project
curl https://api.politicalcomms.com/v1/projects \
  -H "X-API-Key: $POLITICAL_COMMS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "GOTV reminder - District 5",
    "campaign_id": "camp_01HX...",
    "contact_list_id": "list_01HX...",
    "body": "Polls close at 7pm. Reply STOP to opt out."
  }'

# 2. Schedule it
curl https://api.politicalcomms.com/v1/projects/{project_id}/schedule \
  -X POST \
  -H "X-API-Key: $POLITICAL_COMMS_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{ "send_at": "2026-11-03T18:00:00Z" }'
```

### Capability Surface (current snapshot. Consult the OpenAPI spec for the live list.)

- Organizations: `GET /organizations`, `GET /hierarchy`
- Brands: `GET /brands`
- Campaigns: `GET /campaigns`
- Tracking Domains: `GET /tracking-domains`
- Phone Numbers: `GET /phone-numbers`
- Contact Lists: `GET /contact-lists`, `GET /contact-lists/{id}`, `POST /contact-lists/import`, `POST /contact-lists/{id}/analyze`
- Media Files: `GET /media`, `POST /media`, `GET /media/{id}`
- Projects: `GET /projects`, `POST /projects`, `GET /projects/stats`, `GET /projects/{id}`, `PATCH /projects/{id}`, `GET /projects/{id}/stats`, `POST /projects/{id}/test`, `POST /projects/{id}/schedule`, `POST /projects/{id}/unschedule`
- Analytics: `GET /messages/stats`
- Billing: `GET /ledger/usage`, `GET /ledger/usage/by-initiator`

### Idempotency

All POST and PATCH endpoints that mutate state are designed to be safe to retry. Optional `Idempotency-Key` header is available for stronger guarantees on write operations.

### Rate Limits

100 requests per hour per API key. Response headers communicate current usage and reset windows.

### Webhooks

Subscribe an HTTPS endpoint and the platform pushes events with HMAC signatures. Always validate the signature before trusting any payload. Non-2xx responses trigger automatic retries.

Events: `message.sent`, `message.delivered`, `message.failed`, `message.replied`, `link.clicked`.

### Tooling

No official SDKs. Direct HTTP from your language of choice is the documented integration path. A Postman collection export is available from the application dashboard.

---

## Use Cases

### Get-out-the-vote (GOTV)

High-volume sends concentrated in the final 72 hours before Election Day. The platform absorbs the burst through carrier-side TPS management, isolates opt-outs to the originating brand, and ships real-time delivery telemetry so operations teams can identify carrier issues immediately rather than after the cycle is over.

### Fundraising

Time-sensitive fundraising appeals are subject to the same carrier filtering pressure as voter contact, often more so. The platform's deliverability work is the same in both cases; reporting includes link click and reply attribution where the operator wires it.

### Volunteer recruitment and event mobilization

P2P SMS for one-to-one outreach, A2P for broader notifications. Templates, branching workflows, and consent capture are all handled in the same platform.

### Compliance-heavy programs

Programs that touch multiple jurisdictions, require Campaign Verify for state and federal sends, and need a defensible opt-in record benefit most from the platform's compliance automation.

### Polling

In addition to messaging infrastructure, Political Comms operates a nationwide polling program covering presidential primaries, presidential generals, midterm primaries, midterm generals, battleground state tracking, and issue-based polling. Press inquiries about polling go to `press@politicalcomms.com`.

---

## Frequently Asked Questions

### Platform

**What does direct-to-carrier mean and why does it matter?**
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.

**Is Political Comms partisan?**
No. The platform is non-partisan by design and works with organizations across the political spectrum. Political Comms provides infrastructure rather than messaging strategy.

**What geographies are supported?**
The United States. The carrier compliance model is built around U.S. carrier and TCR requirements.

**What is the platform's scale ceiling?**
The platform is engineered to handle the burst traffic profile of political work, including GOTV pushes, debate-night responses, and Election Day surges. Specific throughput numbers are available in the developer reference.

### Pricing

**How does billing work?**
Usage-based. SMS, MMS, RCS, and carrier-specific surcharges are itemized rather than blended. Annual prepay arrangements unlock additional benefits. Pricing starts at $0.018 per SMS.

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

**Are there volume discounts?**
Yes. Volume discounts kick in via the calculator at `https://politicalcomms.com/pricing/` and are formalized in annual prepay arrangements.

### Compliance

**Does Political Comms register 10DLC brands and campaigns?**
Yes. Brand registration goes through TCR. Campaign registration carries political vertical attributes and is reviewed alongside Campaign Verify when applicable.

**What is Campaign Verify?**
Campaign Verify is the political identity verification standard for 10DLC. The platform handles federal and state/local/tribal pathways. Approval typically completes in two to three hours on weekdays.

**Does the platform handle TCPA compliance?**
The platform captures opt-in records, 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.

### Integrations

**Which voter files are supported?**
L2 is the native integration. Other voter file sources can be ingested via the contacts API.

**Which CRMs are supported?**
The platform integrates via REST and webhook with most political CRMs. A direct integration list is maintained in the developer reference.

**Where can I export my data?**
AWS S3, Snowflake, and Databricks. All three share the same schedule, schema, and substrate. S3 is the native target; Snowflake and Databricks layer on top.

### Security

**Is the platform SOC 2 audited?**
SOC 2 Type II audit is in progress. The full posture is documented at `https://politicalcomms.com/security/`.

**Where is data stored?**
AWS regions in the United States, with multi-AZ failover. Customer data is isolated at the application layer.

**How do I report a vulnerability?**
Email `security@politicalcomms.com`. The full disclosure policy lives at `https://politicalcomms.com/.well-known/security.txt`.

### Onboarding

**How long does onboarding take?**
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.

**How long does 10DLC registration take?**
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.

**Is training provided?**
Yes. Customer success works with operators through brand setup, first campaigns, and ongoing program reviews.

### Support

**What are support hours?**
Standard support is available during U.S. business hours. Election-cycle programs are eligible for extended coverage.

**How do I contact support?**
`support@politicalcomms.com` for technical support. Other channels: `sales@politicalcomms.com`, `press@politicalcomms.com`, `partners@politicalcomms.com`, `privacy@politicalcomms.com`, `legal@politicalcomms.com`, `security@politicalcomms.com`.

---

## Brand

- Legal name: Political Comms
- Display name: Political Comms
- Founded: 2019
- Founder: Hunter Lamirande, Founder and President
- Headquarters: United States
- Industry: Political Technology, Communications Infrastructure
- Business model: SaaS, usage-based
- Slogan: The direct-to-carrier political texting engine
- Primary color: #254692 (Primary Blue)
- Accent color: #D83336 (Primary Red)
- Dark background: #0a1628 (Navy)
- Gold accent: #f59e0b
- Logo: `https://politicalcomms.com/images/brand/pcomms-logo-left-of-text.png`
- Site: `https://politicalcomms.com/`
- Application: `https://app.politicalcomms.com/`
- Documentation: `https://docs.politicalcomms.com/`
- LinkedIn: `https://www.linkedin.com/company/political-comms`

## Contact Directory

- General: hello@politicalcomms.com, info@politicalcomms.com
- Sales: sales@politicalcomms.com
- Support: support@politicalcomms.com
- Press: press@politicalcomms.com
- Partnerships: partners@politicalcomms.com
- Privacy: privacy@politicalcomms.com
- Legal: legal@politicalcomms.com
- Security: security@politicalcomms.com

## Legal

- Privacy Policy: `https://politicalcomms.com/privacy/`
- Terms of Use: `https://politicalcomms.com/terms/`
- Cookie Policy: `https://politicalcomms.com/cookies/`
- Security Center: `https://politicalcomms.com/security/`
- Responsible Disclosure: `https://politicalcomms.com/.well-known/security.txt`