Residents see one city. Your vendors do not.
Alerts, 311, agendas, records, recreation and payments in one contract and one control panel, instead of a renewal for each.
A notice, a pothole report, a permit and a records request attach to the same address and survive residents moving in and out.
250+ languages in both directions: a resident replies in their own language and staff read it translated.
Residents, messages and reports are not metered, so a bigger town or a busy storm does not raise the bill.
Contact lists and neighborhood boundaries move first. Your current system stays live until Bloomz is confirmed sending.
Your name, seal and colors in the App Store and Google Play, with a no-login public mode for the website, news, meetings and calendar.
A stack of tools becomes one.
Whatever you run today, here is what comes across.
Contact lists, neighborhood boundaries and message templates move first, so alert coverage never lapses. Boundaries are drawn on the map or imported from the GeoJSON or KML your GIS already produces.
See the comparison →Departments and report categories are set up with your public works team. Your clerk and public works decide how reports already open are handled.
See the comparison →Programs, facilities and fee schedules are loaded, and registration windows reopened in the branded app. A season in progress can finish where it started.
See the comparison →Boards, members, seats and terms, recurring meeting schedules, and the agenda and minutes archive you want online.
See the comparison →Departments and the intake form. Your clerk decides how requests already in progress are carried over.
See the comparison →Keep your current website and run alerts, 311, agendas, records and payments beside it, or move to the optional City Website on the same panel.
See the comparison →Subscriber lists become Connect newsletters and neighborhood groups, sent on the same channels as alerts.
See the module →Stays your system of record. Bloomz holds utility service accounts and statements for residents, and the register you export seeds the household record.
See the module →One record per household, one feed per resident.
Your utility register stays the system of record. Bloomz becomes the system of action: every alert, report, meeting and payment lands on the household the register already defines.
Send the parcel or utility register your city already keeps: parcel number, service address, meters, owner of record and contacts. Our onboarding team maps your columns, so nobody reformats a spreadsheet.
Before anything is written you see what would be created: households, residents, and an owner or renter role inferred for each primary contact. Your clerk can override a role. Nothing is invited yet.
Each parcel becomes a household record. Contacts with an email or phone become residents; names without a channel stay as household contacts. Running the file again updates, never duplicates.
Addresses are geocoded and placed inside the neighborhood boundaries you drew or imported. Anyone the map cannot place lands in a Needs Placement list with the reason, so you fix a handful, not a thousand.
Your clerk reviews, then invites. Residents arrive already in the right neighborhood, on the web app first and in your city's own app once it clears store review, and the first alert reaches them in their language.
| Parcel # | Address | Water meter | Owner | Primary contact |
|---|---|---|---|---|
| 0000-00-A | 100 Example St | W-0001 | Sample Owner | Sample Contact |
Illustrative row, not a real resident. Your own column names are mapped for you.
The City of Fort Meade, FL is Bloomz's launch partner. We ran its real parcel register through the importer and verified the result live: households created, residents attached, addresses placed in neighborhoods, and a second run updating records instead of duplicating them.
The onboarding team runs the import for your city; there is no spreadsheet for you to reformat.
Use the utility or parcel register the city already has.
Four steps from register to live.
Dry-run preview, then the real run. Alert contact lists and templates move across so coverage stays continuous.
Boundaries placed, households sorted into neighborhoods, departments configured.
Role-based sessions for the clerk, finance, public works, recreation and communications.
Your clerk reviews and sends invitations in week 4. Residents join on the web app first, and in the city's own app once it clears app-store review (30 to 45 days end to end). The first alert goes out in 250+ languages.
Questions cities ask about switching.
Send us your register.
See your city in the app.
A short call to look at your current vendors, your register and your timeline.