Guides · Political campaign software

Political Campaign Software: Choosing a Campaign CRM

Political campaign software is the set of tools a campaign uses to organize its work and reach people: a canvassing app for doors, a texting tool, email, a website, fundraising and compliance software, and a CRM (customer relationship management software). A CRM for political campaigns, often called a political CRM, keeps one record for every person your campaign or party organization works with: voters, volunteers, donors, committeepersons, and the local leaders whose support you want. Everything you learn about a person is added to that record in date order, from the petition they signed to what they said at the door, how they answered a text, and the form they filled out on your website, so anyone on the team can see the whole history before the next contact.

The best CRM for a political campaign is the one that keeps that record complete and lets the organization keep it from one race to the next. The section on what to look for below lists the questions to settle before you choose. The rest of this guide covers the decisions that matter more than any software: treat each person as one record, import every list the same way, have your door and texting tools add results to each person's record, write down consent with a date and a source, and make sure the organization, not one volunteer, owns the account. It is written for candidates, campaign managers, county and township party organizations, precinct committeepersons and referendum committees, whatever your party and whichever side of a ballot question you are on.

What a campaign CRM actually does

Many CRMs are designed for tracking business sales. A race is organized differently: it has a fixed end date and touches many people once or twice, but underneath it sits a smaller group the organization deals with for years, such as committeepersons, donors and volunteers. A campaign CRM has to support both the short race and the long-term relationships.

It keeps one record per person

A campaign CRM is organized around people rather than lists. A voter who signed your petition, answered a survey question at the door and replied to a text is one person with three events on their record. In a campaign without a CRM, that same voter is three rows in three files, often under slightly different names, and nobody can tell they are the same neighbor.

It keeps the history in order

Each record carries two kinds of information. Stable facts, such as name, address, precinct, phone and email, change rarely, and you want the current value. Events, such as a door result, a text reply or an opt-out (a request to stop messages), stay on the record in the order they happened. Keeping the two apart lets a volunteer see "not home twice, then contacted, said yes to a yard sign" rather than a bare label like "supporter" with nothing behind it.

It answers the questions that come up late in a race

In the last weeks of a race, the same questions come up. Who signed our petition? Who told us they are with us? Who asked us to stop contacting them? Which committeepersons promised to circulate sheets? A CRM can answer those quickly because the answers are on each person's record, not in someone's memory.

What it does not do

A CRM keeps records. It does not replace the paper petition: every Illinois candidate petition is signed in ink on the official form with a notarized circulator statement, and the CRM holds a note about the paper, never the paper itself. It does not decide who you may text, because consent rules still apply. It is not the treasurer's ledger, and it does not knock doors or send texts on its own. Your canvassing and texting tools do that, and their results go on the record. Our political campaigns page shows how CoreCNX handles this for campaigns that run the full CNX suite.

What to look for in political campaign software

Campaign tools are sold in different ways. Some platforms bundle voter data, a website, fundraising and outreach, and some of those are offered only to one party's candidates and organizations. Others, including CoreCNX, serve any campaign and import the voter list you get from your party, your election authority or a data vendor. Either way, settle these questions before you choose a CRM for a political campaign.

Our comparison of nine CRMs political campaigns use applies these questions to specific tools, from party-run platforms to tools open to any campaign.

Campaigns that rely on volunteers should also look at how the record supports organizing. A supporter's next step can be tracked as a stage, which is the idea behind a ladder of engagement. Volunteers who contact the people they already know, an approach called relational organizing, need a way to note who knows whom. Field directors will want to measure how canvassing is going, and our glossary entry on contact rate explains the most common measure and how to calculate it.

Where a campaign's contact data comes from

Contact data comes from several sources, and each identifies people differently: a petition sheet by name and address, a canvassing app by address, a texting tool by phone number. As a result, the same voter often ends up as several separate records.

Petition sheets

Petition season produces your first list of people who have actively done something for the campaign. Signers of an Illinois petition must be registered voters at the address shown next to their signature, and on a party primary petition they must be qualified primary electors of that party who live in the district (10 ILCS 5/7-10). That makes a signed sheet a useful record of engaged voters.

Record who signed, on which sheet, who circulated it and roughly when. The paper stays the legal document, and once a petition is filed it cannot be modified or added to. There is no electronic option for an Illinois candidate petition, so the typed list is only ever a note about the sheets.

The most common mistake with petition data is treating a signature as permission to text, which it is not. A petition sheet counts as consent to receive texts only if the sheet says so plainly and the date is recorded. Our post on keeping one voter record across petitions, doors and texts walks through how a signer's record should look, consent included.

Door results

In Beacon, the CNX suite's canvassing app, a door result can be contacted, not home, refused, moved, deceased, inaccessible, come back later or left literature, along with a 1 to 5 rating, notes and survey answers. During petition season, a survey question can record "signed: yes/no" at the door, so the canvass records and the petition records match.

When moved or deceased is on the person's record, whoever plans the next canvass can leave that address off.

Text replies

A combined record matters most for texting, because the rules are strict and a mistake can put your number and reputation at risk. Every reply and every opt-out belongs on the same record as that person's door results. CampaignCNX+, the suite's texting tool, handles STOP replies automatically and keeps a shared two-way inbox for your team. Our sister product's guide to political texting covers the texting side in full.

Political texting also needs Campaign Verify, which confirms to the phone companies that a sender is a registered campaign or committee. It requires an EIN (a federal tax ID number) and a published election-authority filing, so a candidate with no committee is not eligible, though a county or township party committee with an EIN and a filing can be verified. Our explainer on when an Illinois candidate needs a campaign committee covers the $5,000 threshold and the D-1 deadlines.

Forms, sign-in sheets and your website

The last source is the broadest: volunteer sign-up forms, event sign-in sheets, emails people answer, and questions visitors ask on your website. A website chatbot such as Alma collects contact details from visitors, and in CoreCNX, chatbot leads are among the events added to a contact's timeline (the dated history on each record), and email events are too. Paper sign-in sheets follow the same consent rule as petitions.

How the streams become one voter record

Combining these sources mostly means doing a few things in the right order. If you skip steps, you end up with a CRM full of duplicates, which is the original problem in a new tool.

Start with your best list

Pick the most complete, most trusted list you have, often a voter list from your county party or your own cleaned-up supporter file, and import it first. Then add each other list one at a time, combining overlapping entries as you go, rather than importing everything at once.

Match on phone and email, never on a name alone

Two entries are the same person when they share a phone number or an email address. A phone number is usually the more reliable match, because families often share an email inbox and addresses such as info@ serve several people. Matching on name and street can combine two different people into one record. A missed merge leaves a duplicate you can fix later, while a wrong merge mixes two people's histories in a way that is hard to undo. When in doubt, keep them separate. Our companion guide to the unified contact timeline explains matching, merging and why this order matters.

Keep stable facts and events apart

Decide before the first import which columns are facts about the person (name, address, precinct, phone, email) and which are events (signed a petition, a door result, a text reply, attended an event). Facts are updated when they change. Events are added and never overwritten, because an event that can be changed later is no longer reliable evidence. This matters most for opt-outs, because the record that someone asked you to stop is the one you most need to keep.

Add door and text results to each person's record

Once the base list is in, have the tools that do the work add their results to each person's record, rather than combining a weekly spreadsheet from each tool by hand. In the CNX Suite, CoreCNX holds that record, and CampaignCNX+ for texts and Alma for website leads (on its Growth plan and up) send their activity to it. Beacon sends its door results.

Put consent on the record, with a date and a source

For every phone number, note where it came from and when consent was given: a sign-up form with clear texting language, a sign-in sheet that said so, or a reply in which the person asked to hear from you. Keep it on the person's record, not in a separate file someone forgets to check, and build your texting list only from people who agreed.

Keeping the record from one election to the next

The record is most valuable in its second and third cycles, when it already shows your reliable volunteers, your supportive households and who asked not to be contacted.

Plan for regular turnover

In Illinois, the people in party roles change on a schedule. Outside Cook County, each party's primary voters elect one precinct committeeperson per precinct at the general primary every two years (10 ILCS 5/7-8(b)). In Cook County, ward and township committeepersons are elected every four years, and precinct captains are volunteers organized by those ward and township organizations. Staff and volunteers change even more often.

The organization owns the account

Set up the CRM, the canvassing tool and the texting tool under the campaign committee or the party organization, never under a volunteer's personal email or credit card. Give at least two people administrator access. Volunteers get access to the work they do, but they do not own the list. This decision keeps a precinct's history with the organization when its committeeperson leaves.

Plan the handoff before anyone moves

A precinct committeeperson who moves out of the precinct creates a vacancy right away. The statute says the person loses all rights and duties in the precinct even before a successor is named (10 ILCS 5/7-8(b)). The vacancy is filled under your party's rules, usually through the county chair. If the precinct's history is already stored in the organization's account, the successor starts with it. Our post on what happens when a committeeperson moves includes a handoff checklist that works on paper or in software.

Close out each election on purpose

After election day, decide whether the record carries forward to the next race, passes to a successor, or closes. Export a full copy so the data never depends on one tool, and keep opt-outs and "do not contact" notes with the records wherever they go. When you import an old list for the next cycle, give its entries their original dates. A history with invented dates misleads everyone who reads it.

Who keeps a campaign CRM, and what they use it for

The same record serves different jobs depending on who is working it.

Candidates and campaign managers

For a candidate in a partisan race, some of the most important records are not voters at all but committeepersons. On the county central committee, each precinct committeeperson has one vote for each ballot cast in the precinct by the party's primary voters at the primary where they were elected (10 ILCS 5/7-8(d)), so some carry far more weight than others. Our post on why candidates court committeepersons explains what they control, and our step-by-step plan for meeting the committeepersons in your district covers the first meeting through the primary.

Many county and township parties also slate candidates before a primary. Slating is a party practice rather than a procedure the Election Code sets out, and a slated candidate still has to file a valid petition and win the primary. Our explainer on how local parties slate candidates covers who decides and what to ask. Throughout this process, put every conversation, request and commitment on the committeeperson's record, so you follow up when you said you would.

Precinct committeepersons

The precinct is the unit everything else is built on, and our post on what a precinct is explains how Illinois draws precincts, how polling places are chosen and how to find yours. Most county parties ask committeepersons to recruit judges for their precinct, because the county chairs furnish the judge lists and are asked to list people who live in the precinct "insofar as possible" (10 ILCS 5/13-1). A record for each neighbor turns that knowledge into something a successor can use. Our post on how CoreCNX supports precinct committeepersons matches each part of the role to the record, and Beacon's precinct committeeperson handbook covers the role itself, from the statute to walking the precinct.

County and township party organizations

The county central committee is made up of the party's township, precinct and ward committeepersons in the county (10 ILCS 5/7-8(d)), so a county party's strength depends on how well its precincts are organized. With one account, the county party can see which precincts are organized, which are vacant and who said yes to serving as an election judge. Larger organizations often want a separate account area for each township or ward, and consultants managing several campaigns need the same. Our agency page explains how an Enterprise parent account holds client sub-accounts, and our guide to running the county party's data in one CRM shows how to set it up for every committeeperson.

Referendum committees and coalitions

A referendum coalition often brings several groups together, each with its own list, for a few months on one question, so the first job is turning those lists into one record per person. Two legal rules apply. Public funds may not be used to urge a vote for or against a public question, though factual information is allowed (10 ILCS 5/9-25.1). And a group that raises or spends more than $5,000 in any 12-month period for or against a question generally must file a Statement of Organization with the Illinois State Board of Elections (10 ILCS 5/9-3). Our post on CoreCNX for referendum coalitions and party organizations includes worked examples. Confirm your own obligations with ISBE or an election attorney. Coalition partners are often nonprofits with their own donor and volunteer lists, and our post on what a small nonprofit needs from a CRM covers keeping those records between elections.

Running the job in CoreCNX

CoreCNX is the CRM in the CNX suite: one contact record per person, with a timeline that text replies and chatbot leads write to, and door results and email events. The steps below cover setup and one election cycle.

  1. Open the account in the organization's name. Start the trial under the committee or party organization, not a personal account, and make at least two people admins. Give your campaign manager or county office the manager role, and volunteers and committeepersons the user role.
  2. Choose a plan by the number of contacts. Starter is $49 a month for up to 5,000 contacts, Growth is $99 for 15,000, Pro is $199 for 50,000, and Enterprise is $499 for about 150,000. An Enterprise parent can hold sub-accounts for townships, wards or clients at $49 a month each.
  3. Import your best list first. Clean it in a spreadsheet, one row per person, with name, address, precinct, phone and email in their own columns, then import it as a CSV file (a plain spreadsheet format). Combine duplicate entries before each later import.
  4. Bring in petition and sign-up lists the same way. Type up signers with sheet number and circulator, and sign-ups with their date. Fill a texting-consent column only where the sheet or form said so plainly and was dated.
  5. Walk with Beacon. Beacon puts walk lists (each volunteer's addresses) on a map, plans routes door to door, and works offline, uploading results when back online. The suite is designed so that Beacon's door results, appointments and contact status appear on the person's CoreCNX timeline.
  6. Text through CampaignCNX+. Send to supporters who agreed to receive texts. CoreCNX does not send texts itself. CampaignCNX+ sends them, and each text, reply and opt-out is added to the person's timeline beside the rest of their history. Our page on CoreCNX as a CRM with text messaging lists what is recorded.
  7. Add your website chatbot. Once Alma, the suite's website chatbot, is connected to your CoreCNX account (we connect it for you, or it happens automatically when you buy it as a suite through CoreCNX), the leads it collects on its Growth plan and up reach the timeline too, so a volunteer at that door can see that the person contacted you through your website.
  8. Open the record before every contact. Before a callback, a second knock or a committeeperson meeting, read the person's timeline.
  9. Export at the end of the cycle. CoreCNX exports to CSV, so the organization keeps a full copy and decides what carries forward.

Start with the list you already have

You do not need a perfect list to begin. Take the file you trust most, whether that is last cycle's supporters, a precinct list or a coalition partner's sign-ups, and put it in an account your organization owns. Start a 14-day CoreCNX trial, import that one list, and see how a single record per person changes the way your team plans its next canvass.

Frequently asked questions

What is the best CRM for political campaigns?

There is no single best choice for every race. The best CRM for a political campaign keeps one record per person, imports your voter and supporter lists, records results from your canvassing and texting tools, keeps consent with a date and a source, and belongs to your organization rather than to one volunteer. Compare published prices, check whether a tool serves your party, and test it with your own list before you commit.

What is the difference between a voter list and a campaign CRM?

A voter list tells you who is registered and where they live. A campaign CRM holds everything your campaign has learned about each of those people over time, including petition signatures, door results, text replies, sign-ups and emails, in date order on one record per person. Most campaigns import a voter list as the starting point and let each canvass, text conversation and event add to it.

Is a petition signature permission to send texts?

No. Signing a petition is not, by itself, permission to receive texts. A petition sheet or sign-in sheet counts as texting consent only if it says so plainly and the date is recorded. Build your texting list from people who clearly agreed, keep the date and source of each agreement on their record, and reach the other signers at the door instead.

What happens to our contact data after the election?

That depends on a decision your organization should make before the first import: whether the record carries forward to the next race, passes to a successor, or closes. Keep the account in the committee's or party's name, keep at least two administrators, and export a full copy at the end of each cycle. Opt-outs and do-not-contact notes should travel with the records wherever they go.

Does a precinct committeeperson need a CRM?

A committeeperson can do the job well without software, but the job is mostly about remembering people: reliable primary voters, volunteers, election judge prospects and neighbors who have moved. One record per person makes that knowledge easier to use and to pass on. Because a committeeperson who moves out of the precinct creates a vacancy right away, the record works best in an account the party organization owns.

Put your campaign's contacts on one record

CoreCNX keeps one record per person, with texts from CampaignCNX+ and form leads on the same timeline, and door results from Beacon, from one race to the next.

See CoreCNX for campaigns