Your office answers to a district, not a list. Every message arrives already verified — in district, registered, which precinct — on one constituent record that remembers every case you have ever worked for them.
A separate product for official office use. Campaign functionality is not included.
The same inbound message, before and after it hits your office queue.
Nobody looked anything up. The record was assembled the moment the message arrived.
A queue and a case. Not a database your staff have to learn.
Email, web forms, phone notes, walk-ins and letters enter a single office queue — shared across your staff, so nothing sits unread in one person's inbox.
Each message is matched to the public voter file, flagged in or out of district, grouped with anything that constituent has contacted you about before, and routed to the staffer who handles that issue.
Open a case, assign it, set the follow-up, draft the reply, close it. The record stays on the constituent's timeline permanently — so a call a year from now starts with context instead of an apology.
Every channel in one shared queue with assignment, status and read state. Two staffers never answer the same letter, and no message quietly ages out.
District, registration status, precinct and voting history matched from the public voter file automatically — so your office knows who it is answering before it answers.
Cases with owners, status, due dates and a full activity trail. You can answer "what is open right now, and what is late" without asking anyone.
Every case, message and logged conversation on one constituent record — intact across staff turnover and across terms. Context survives the people who created it.
High-volume advocacy blasts are grouped and answered together. Routine replies come pre-drafted for a staffer to review and send. The system does the work; your staff approve it.
What your district is contacting you about, how positions are trending by issue, response times by staffer, and what is still open — as a live view and a scheduled report.
A public office has different rules than a campaign. So this is a different product, not a mode.
Accounts designated as government-funded are provisioned without campaign functionality. We will provide the written configuration description your procurement or ethics counsel needs for review.
Public offices are asked to evaluate constituent systems that publish no pricing, no security posture and no integration documentation until after a sales call. We think that is backwards for an entity spending public money. Ask us for the security overview, the data-handling description, the integration list and a written price — you will get all four before you are asked to sit through a demo.
It is a constituent relationship and casework system for legislative and elected offices. Every message your office receives — email, web form, phone note, or a conversation logged in the district — lands on one constituent record with a full history. Staff open cases, route them, work them, and close them, and the office can see at a glance what the district is actually asking for.
Two ways. First, verification: most systems treat an inbound message as an anonymous email address, so a staffer has to look up by hand whether the sender is even a constituent. Here that answer is already on the message — in district or not, registered or not, which precinct — before anyone opens it. Second, adoption: the common complaint about legacy constituent CRMs is that only a fraction of members ever use them, because they amount to another inbox. This system triages, summarizes and drafts, so it removes work instead of adding a place to check.
Public voter registration files — the same official records available to any candidate, office, or member of the public under state law. When a message arrives, it is matched against that file to confirm district, registration status and voting history. No private data brokers, no purchased consumer dossiers.
No. This is a separate product configured for official office use. When an account is marked as government-funded, campaign functionality is not part of it — there is no canvassing, no campaign management, and no electioneering surface in the product an office receives. That separation is a configuration of the account, not a policy staff are asked to follow, and we will document it in writing for your procurement and ethics review.
Per office, billed annually, with the price published rather than quoted after a discovery call. We will give you a written quote and a full feature list before you talk to anyone in sales. Offices evaluating a switch can run it alongside an existing system during a pilot term.
A pilot with one office. We load your district from the state voter file, connect your inbound email, and import open casework if you have it in a system today. Staff training is short by design — the interface is a queue and a case, not a database. Offices are typically working live cases inside a week.
We will load your district, connect your inbound mail, and have your staff working live cases inside a week. Tell us about your office and we will put a written proposal in front of you.
Per office · Published pricing · Written before the sales call