The voter file providers, the CRM, the fundraising platform, the spreadsheet. The texting plugs into the stack, not the other way around.
VAN and L2 lay party, district, precinct, support score, and vote history onto the contacts you already hold. Matched data enriches. Unmatched rows hold for the field.
Voter file →Import from the CRM or a CSV, export any Segment back out. Every imported row carries its consent source, and rows without one land as field contacts, never textable ones.
Contacts →Giving history lands on the contact record, so the third-time donor and the first-time subscriber get different asks from one send, and Reports close the loop.
Fundraising →Grouped by what they do. Each one is marked for what it does today and what is on the build path, because an honest integration list is the whole point.
The Democratic contribution rail. A source-tagged donation link drops into the composer, and the gift reads back onto the contact record.
The Republican contribution rail. Same source-tagged link and same write-back to the record for a GOP committee.
An any-party processor. Works for a committee of any affiliation, and a party switch repoints nothing on this rail.
A commercial voter file. Party, district, precinct, and vote history enrich the contacts you already hold. Enrichment never manufactures consent.
The Democratic data warehouse. A committee key connects it. Matched rows enrich, unmatched rows hold for the field.
Republican data cooperatives. These require a private contract with the provider, so a connection stands up per committee, not off a public API.
The two sending carriers behind every message, with failover so a send survives a bad night. This is the plumbing the platform runs on.
Political 10DLC registration through TCR. Verified sender identity and brand vetting so your numbers land instead of getting filtered.
Rich messaging with the name, logo, and checkmark on every thread. Blocked on carrier agent approval, which every provider waits on.
A volunteer connects their own circle for relational outreach, and the opt-ins that come back write a real consent receipt.
Import any list, export any segment. Every imported row carries its consent source, and rows without one land as field contacts, never textable.
Two-way sync with the campaign CRM so the record is the record everywhere. Import today by export, a live connector on the path.
Honesty is the product. Today the platform sends through its carriers, enriches from imported data, and captures consent at the source. The named rails and data warehouses above are being built in priority order, and this page says exactly where each one stands rather than implying they are all live.
Bring your stack. Keep your records.
Pick your plan