PublicInput isn't a subscriber list with an email tool bolted on. It's a full CRM built for public agencies. Every contact your agency has ever engaged — across every subscriber list, project, division, and channel — lives in one record, so the right residents get the right message without anyone rebuilding a list from scratch.
We run the migration. Subscribers, topic subscriptions, opt-outs, bulletin history, and templates come across into one account.
Most agencies run outreach on tools that were built to send, not to know. A list holds an address and a topic. It doesn't hold where someone lives, what language they read, which divisions have already talked to them, or what they said the last time you asked.
So every new project starts over. Staff export, filter, de-duplicate, and re-upload. Two divisions message the same household in the same week and neither one knows. And the question a manager actually asks — did we reach the people this decision affects? — can't be answered from a list.
Most state agencies already run their notices on GovDelivery, and the subscriber list is the part nobody wants to risk. You don't have to. We run the migration: subscribers, the topics they picked, opt-outs, your bulletin history, and your templates and branding come across into one account, and residents keep getting what they signed up for at the same addresses.
Your subscriber records and the topics they are signed up for load into your account, with opt-outs preserved.
You keep sending from your current system while the migration runs, and you pick the cutover date.
Bulletins residents saved links to come across and get a permanent page in your account.
You check counts by topic, opt-outs, and test sends against your own records first.
Every field below is something you can segment on, report on, or route a message by. That's the difference between a database of addresses and a CRM: the record carries enough about a person to decide whether this message is for them.
| On the record | What it lets you do | Where it comes from |
|---|---|---|
| Location | Target a county, region, legislative district, or drawn area | Address, geocoding, or a map point the resident placed |
| Demographic data | Report on who you reached, and who you didn't | Self-reported survey fields and Census-linked geography |
| Division & program | See every part of the agency that has engaged this resident | The program or campaign that created the interaction |
| Topic interest | Send only to the people who asked to hear about this | Topic subscriptions and opt-ins across the agency |
| Language preference | Deliver the right translation automatically | Stated preference or the language they engaged in |
| Channel & consent | Reach by email or text, and honor every opt-out agency-wide | Sign-up source, with opt-out applied to the whole record |
| Past engagement | Segment on behavior — who commented, who opened, who never has | Every campaign, comment, survey, and meeting interaction |
When a resident unsubscribes, it applies to the record, not to one division's list. You don't have to trust that five teams each processed the same request in five different systems.
Location, demographic data, division, topic interest, and past engagement can be stacked into one audience in the moment you need it. A static subscription list can't do this — it can only give you the people who happened to sign up for that list.
The segment is drawn from every contact the agency holds, so people who engaged through another division's project are included automatically.
Geography, demographics, topic, division, and behavior combine in one definition. No export step, and no version of the list living on someone's desktop.
Save the segment and send to it again. Adjust one condition to spin off a related audience without starting over.
Because the segment is built on the record, the same fields that defined the audience are available when you report on reach and representativeness.
Every email, text, comment, survey response, and hearing sign-in attaches to the contact record and stays visible to every team that needs it. Nobody has to ask another division what this resident has already been told.
Before a new outreach push, you can see who has already been surveyed about this program and what they said.
When a resident calls, staff can see the projects they've engaged with and the messages they've received, instead of starting cold.
Participation, who was reached, and how their input was handled come out of the same system as the campaign — not a reconstructed spreadsheet.
Staff turnover doesn't reset institutional memory. The history lives on the record, not in an inbox.
Most agencies end up paying for an email tool that isn't purpose-built for government, a separate texting platform, a separate CRM or contact database, a separate survey tool, and other point tools for forms, hearings, and web notices — on top of the staff time it takes to keep them all in sync.
One platform instead of an email tool, a texting platform, a separate CRM, and a separate survey tool.
One login, one training process, one support relationship — across every division using it.
No more manually syncing contact lists between systems that don't talk to each other.
A walkthrough takes about 30 minutes. We'll show you what a contact record looks like once every division's engagement lands on it, how a segment is built across location, language, topic, and past behavior, and what migrating your existing subscriber lists involves.
