Poll City
Poll CityCampaign OS
Log inStart campaign
Product command entry

Choose the correct Poll City surface before entering the product.

Campaign operators, vendors, internal teams, and public civic users should not land in the same place. This entry hub makes the product organization visible immediately.

Campaign OS

Field, CRM, Comms, Materials

Boundaries

Protected workspaces by role

Readiness

Audit-first product lanes

Platform overview

See how Poll City connects campaign websites, CRM, field work, communications, fundraising, reporting, and operations.

Open overview

Campaign login

Approved campaign teams, vendors, officials, and operators sign in to role-scoped workspaces.

Log in

Poll City Social

Open the public civic layer for candidate profiles, official updates, polls, questions, and community engagement.

Open Social

GOTV command centre

Open the authenticated election-period workspace for readiness, people, field work, rides, communications, and source-labelled reports.

Open GOTV

Field operations

See the campaign field entry for assignments, routes, teams, signs, literature, follow-ups, and the worker handoff.

Open Field Ops

Communications suite

Open the campaign communications area for SMS, email, voice/IVR, inbox, queue, sender, consent, and delivery states.

Open Communications
Read-only product walkthrough

See one campaign move from plan to proof.

This public walkthrough uses synthetic demo records. It shows the product journey and action handoffs; it does not expose or mutate a real campaign.

DEMO DATA · NO WRITE ACCESS

One operating system

Campaign OS overview

The product connects campaign setup, field work, communications, GOTV, and evidence without hiding the user’s next step.

Active workstreams

5

Field, comms, GOTV, social, reporting

Next action

3

Owners and recovery paths are visible

Start the guided path

Choose a surface above or open the real public entry points below.

Open surface
Guided enterprise walkthrough

One product, one decision path, clear evidence.

Start in the public civic layer, move into a campaign workspace, rehearse a GOTV decision, hand work to mobile, and finish with a source-labelled report. Each surface keeps its permissions, loading state, offline state, and next action visible.

Read the operator help Run the GOTV path
01

Choose the right surface

Public, campaign, GOTV, field or comms — never a confusing blended workspace.

02

Take the next action

The page explains the decision, consequence, owner and recovery path.

03

Prove what happened

Receipts, refresh/read-back, source labels and explicit device evidence.

Demo data and footage must be synthetic or founder-approved. A public route is not proof of an authenticated campaign or native-device release.