Most small cities and towns already own a mass-notification tool. CodeRED, run by Crisis24’s OnSolve division, is one of the most widely deployed: a phone-tree-descended system that pushes calls, texts, and emails to residents who sign up. If your city uses it, or is evaluating it, this is a factual look at what it does well, where the category as a whole runs into limits for a small city, and what to weigh before renewing or switching.
What alert-only platforms do well
CodeRED and platforms like it exist for one job, and that focus is a real strength. They are built to reach a lot of people fast with a simple message: severe weather is coming, a boil-water order is in effect, a road is closed. For agencies whose entire requirement is “get a warning out,” a mature, widely adopted alert tool is a reasonable, defensible choice, and plenty of small cities have used one for years without complaint.
The limits show up not in how the alert sends, but in everything a city needs to do around it.
The architectural gap: alert-only vs. all-in-one
An alert system answers one question: how do I broadcast a message. It does not answer the questions that come right after. Where does a resident report a pothole, a downed sign, or a code violation, and who gets it? How does a resident pay a utility bill or a permit fee? Where does a resident go to ask the city a question and get an answer, in their own language, at 9pm on a Sunday? Is there anything that rewards residents for showing up to a cleanup or a town hall?
An alert-only platform has no answer to any of those, because they are outside its scope by design. That’s not a knock on the product; it’s the category. The practical effect for a small city is that the alert tool sits alongside a separate 311/reporting system (or none at all), a separate payment portal, a separate website, and no resident-facing app beyond the alerts themselves. Each piece is its own login, its own vendor relationship, and its own budget line.
Bloomz for Cities takes the opposite approach: Smart Alerts (app push, email, SMS, and voice at once, with zone/geo targeting and automatic National Weather Service severe-weather rebroadcast) live in the same subscription as issue reporting, payments, and an AI assistant that answers resident questions from the city’s own site and documents. One resident-facing app, one back office, one bill. See the full alert-system comparison for the feature-by-feature breakdown.
What the November 2025 CodeRED outage showed
In November 2025, Crisis24’s OnSolve CodeRED platform was hit by a ransomware attack. According to reporting from BleepingComputer and Malwarebytes, the INC ransomware group gained access on November 1 and encrypted systems on November 10, taking the platform offline or unreliable for roughly two weeks for towns, cities, police, and fire agencies across the country. Both outlets reported that resident data, including names, addresses, phone numbers, and passwords for hundreds of thousands of subscribers, was exposed. Crisis24 restored service from an earlier backup, meaning some accounts and data from after that backup point did not come back.
We’re not citing this to score a point off a competitor’s bad week; outages and breaches happen across the industry, and the point isn’t that CodeRED is uniquely vulnerable. It’s architectural: when the alert system is the emergency communication infrastructure and nothing else, an outage in that one system leaves a city with no channel at all during the window it matters most. A platform where alerts, the resident app, 311 reporting, and payments run on shared, redundant infrastructure spreads that risk differently than a single-purpose tool that a city depends on for exactly one function. It’s a reason to ask any vendor, alert-only or all-in-one, about their incident history, backup cadence, and what a resident actually loses if the platform goes dark for two weeks.
What “alerts plus everything else” actually gets a small city
Consolidating onto one platform isn’t just about avoiding a second vendor. It changes what residents can do:
- Two-way, translated conversation. Alert platforms, including CodeRED, send outbound messages that can be translated into the recipient’s language. None of them let a resident write back in their own language and have that reply route, translated, to the right staff member. Bloomz is built for that two-way exchange — no competitor in this category offers it; the rest translate outbound only.
- 311-style reporting in the same app. A resident who gets a storm alert can, in the same app, photograph the downed limb blocking their street and pin its location, with the report routed to the right department automatically. That’s Bloomz BeHeard for Cities.
- Utility bill pay and e-bills. The same channel that sent the boil-water alert can carry the e-bill and take the payment. See Bloomz Pay for Cities.
- A civic rewards program. Points for volunteering, cleanups, and civic participation, redeemable at local businesses — a category no alert-only platform, and no competitor we’re aware of, has built. More on that in what a civic rewards program actually is.
How to evaluate a CodeRED alternative
A few questions cut through the marketing on either side:
- Does it do more than alert? If the answer is no, you are choosing a notification tool, not a resident engagement platform, and that may genuinely be all you need. Be honest about which one you’re actually shopping for.
- Is translation two-way, or outbound only? Ask the vendor to demonstrate a resident replying in a language other than English and show you where that reply lands.
- Is pricing published or quote-gated? A published number lets you compare and budget before a sales call.
- What’s the redundancy story? Ask any vendor, alert-only or platform, what happens to resident communication if their system goes down for a week, and how they’d know.
- Does the price fit under your purchasing threshold? Bloomz for Cities publishes pricing starting at $4,630 per year for the core platform, a figure that lands under most states’ formal-bid thresholds, so most small cities can buy on a straightforward purchase order rather than an RFP cycle.
The bottom line
CodeRED and its category peers are competent at the one thing they’re built for: getting a warning out fast. The question for a small city isn’t whether alert-only tools work — they do — it’s whether an alert is the only resident-facing capability worth having on one bill, in one app, with one login. For a city that also wants 311 reporting, utility payments, a real AI assistant, and a way to recognize residents who show up, the case for consolidating is architectural, not adversarial. See the full comparison, or look at what Bloomz for Cities includes and what it costs, published, before you ever book a call.