Run an aggregate count
Counts show universe size, email readiness, phone readiness, and mail households. They do not expose voter-level records.
Use this guide when submitting a count package, approving an invoice, or tracking BYO voter-file workspace setup from the public order page.
Counts show universe size, email readiness, phone readiness, and mail households. They do not expose voter-level records.
Priced packages can become invoices after review. Custom services stay quote-required until the scope is confirmed.
Workspace activation requires a qualified campaign use case, source-path review, and confirmation that the customer is authorized to use the uploaded voter file.
The public order page shows the invoice link when it is ready. Payment moves the order into fulfillment once Stripe confirms it.
After payment, the order page can send the buyer an activation email. The voter-file setup page then requires the BYO agent designation before upload.
Pick the package that matches the next operational handoff.
Use this when the campaign already has an authorized voter file and wants a workspace for import, filters, turf, walk packets, and exports.
Use this when the campaign wants import help plus first turf, field, phone-bank, mail, or CSV export setup.
Use this when the campaign wants a setup call, column mapping support, import validation, and first target universes.
Use this for anything outside BYO launch scope, including append/enrichment, native messaging, supplied data, managed execution, or anything that needs a manual quote.
The request is queued for review. Package, count, and contact details are captured.
The team is checking scope, permitted use, source path, and any missing context.
The scope is ready for approval, but no payment link has been issued yet.
The invoice is available on the public order page.
Payment or approval is complete and workspace setup/import support is in progress.
The workspace or fulfillment artifact is ready and the public order page includes the access link.
The order needs more information or cannot proceed until the review issue is resolved.
If the workspace has not been activated and no voter-file import has started, support can refund and cancel the order.
If CA Voter cannot provision the purchased BYO workspace or make the self-serve import path work for a within-cap file, support can refund or move the customer to a scoped assisted path.
Once the customer activates the workspace or starts using imported voter data, refunds are reviewed by support for service failures, duplicate payments, or credible unauthorized charges.
Files over the self-serve upload cap are assisted/custom work. If the customer's only available file is above the cap, support can refund or quote an assisted-import path.