How to Evaluate a Dialer for a Political Cycle

Picking a dialer six weeks out from election day is the worst time to learn your platform can't scrub DNC properly, or that the multi-line feature your vendor sold you is illegal in three of your target states. The dialer market is loud, the demos look great, and most of the painful questions don't get asked until the list is already half-burned.

Here's how to evaluate a dialer the way a campaign manager should — focused on legality, deliverability, and whether your list will still be usable in week four.

Start with the legal floor, not the feature list

Every dialer demo leads with productivity: agents per hour, contacts per shift, AI screening. Skip past that for the first call. The questions that matter on day one are the ones that keep you out of a complaint file.

• DNC scrubbing. Does the platform scrub against the federal DNC list automatically, on every load? Does it scrub against state-level DNC lists (several states maintain their own, and they're not always synced to the federal file)? Does it scrub your internal opt-out list across campaigns, or only within a single list?
• Political exemption scope. Live political calls have a federal DNC exemption. Prerecorded messages and texts to wireless numbers do not. If your dialer blurs the line between live agent and ringless voicemail or AI agent, you need to know exactly which mode is running.
• Time-of-day enforcement. The platform should refuse to dial outside legal calling hours in the recipient's time zone, not the agent's. This is a config setting most vendors get wrong by default.
• Recording consent. One-party vs. two-party consent varies by state. The dialer needs to handle that per-record, not per-campaign.

If the sales rep can't answer these without checking with someone, you're not talking to the right vendor.

Multi-line dialing: legal in some states, not in others

This is the one that catches campaigns off guard. "Triple-line" or "predictive" dialers — where the system dials three or four numbers per agent and drops the calls that connect after the first — are restricted or effectively illegal in a handful of states because of abandoned-call rules. The dialer vendor will still happily sell it to you.

The FCC caps abandoned calls at 3% per campaign per 30-day period, and requires a recorded identification message play within two seconds when a call is abandoned. Several states layer stricter rules on top — Florida, Indiana, and others have their own statutes that can make aggressive multi-line dialing functionally unworkable.

What to ask:

1. Can the platform throttle abandon rate per-state, not just per-campaign?
2. Does it auto-play the required abandon message, and log it?
3. Can you cap line ratio by state — single-line in restricted jurisdictions, multi-line elsewhere — from one list?

If the answer to any of those is "sort of" or "we're working on it," you have a compliance problem waiting to happen.

Carrier deliverability is half the dialer decision

A dialer is only as good as the trunks behind it. You can have the cleanest list and the smartest pacing in the world, but if your outbound numbers are getting flagged as spam by Tuesday, your answer rate collapses.

Most campaign dialers either bundle their own termination or let you bring your own carrier. Bringing your own is almost always better for a high-volume cycle because you control the number pool, the rotation, and the reputation. A few things worth pinning down:

• Number pool size. How many DIDs (the actual phone numbers your calls show as) can you cycle through? For a serious GOTV push you need hundreds to thousands, not dozens. We wrote more about this in our political campaign connectivity guide.
• Rotation logic. Burning a number means it starts showing as "Spam Likely" on T-Mobile or "Scam Likely" on Verizon. Once that happens, retiring it is the only fix. Your dialer or your carrier needs to rotate before that point, not after.
• Attestation. Calls signed at the highest trust level (carriers call it "A-attestation" — basically, the carrier vouches that you actually own the number you're calling from) get flagged as spam far less often. If your provider can't sign at that level, your answer rate is going to suffer. There's a deeper breakdown here.

Disposition workflows decide whether your list survives the cycle

This is the part nobody demos and everyone regrets. A dialer without disciplined dispositions turns a 200,000-record list into noise by week three.

At minimum your dispositions should sort every dial into buckets you can actually act on:

• Live contact — supporter / undecided / opposed / refused
• Left voicemail (and how many times — cap it)
• No answer / busy (re-dial schedule should differ by bucket)
• Bad number (remove permanently, don't keep dialing)
• Do not call (internal suppression, applied across every future list)
• Wrong person / household member (re-survey opportunity, not a callback)

The dialer needs to push these back to your CRM or VAN in near-real-time. If dispositions sit in the dialer for a week before sync, two things happen: your callers redial people who already opted out, and your data team is reconciling spreadsheets at 2am instead of building turf.

Pricing: ask for the structure, not the sticker

Dialer pricing is rarely the line-item that wrecks a budget. Termination minutes and DID volume are. When you're comparing vendors, ask for a full rate sheet — per-minute termination, per-DID provisioning, any per-call surcharges, and what the commit looks like for the duration of your cycle.

Compare apples to apples. One vendor's "all-in" seat price might exclude termination entirely; another's might bundle it but cap your minutes. Get it in writing before you sign, and negotiate based on your projected dial volume for the full cycle, not a single week.

Plan the wind-down before you sign

The cycle ends. Your dialer contract probably doesn't, at least not on the day you want it to. Before you commit:

• Confirm month-to-month or cycle-specific terms in writing.
• Get number portability terms in writing too — if you want to keep your DID pool for the next cycle or move it to another carrier, know what porting looks like.
• Confirm data export. Your dispositions, recordings, and call logs are yours. Make sure you can pull them in a usable format on day one of the next cycle.

What to do next

Before you sign anything, run the vendor through this short list: DNC scrubbing on every load, multi-line caps that respect state law, A-level attestation, real-time disposition sync, and a DID pool sized for your dial volume. If any of those answers are soft, keep looking.

If you're still shopping for the trunk side of this — the actual numbers and termination — that's where we come in. The bulk DIDs page has the basics, and a quick conversation about your cycle size is faster than reading a spec sheet.