Communications & Alerts
Compose one bilingual message and reach every resident in their chosen language — by email, text, and app push — with delivery tracked all the way through.
Staff write the alert once in English (Spanish is optional and auto-translated), pick the channels and the audience, preview the reach, and send. Every recipient gets it in the language they prefer, and the dashboard shows who was delivered, sent, queued, or skipped.
What you can do
Write once, bilingually
One form with English and Spanish title and body. English is required; Spanish is optional and auto-translated, so a single draft serves both languages.
Email, SMS & push
Toggle the channels for each alert. Pick any mix of email, text message, and mobile-app push for the same message.
Everyone or a segment
Send to all constituents, or build a segment by language, ZIP code(s), and tags (matching any or all tags).
See the reach first
Before you send, a live preview shows how many of your constituents the segment reaches, broken out by email / sms / push.
Manage constituents
Add residents with name, emails, phone/cell, mailing address, ZIP, tags, and a preferred language — the contact book the alerts draw from.
Track every send
Each alert reports counts for delivered, sent, queued, skipped, and failed — refreshed live while a dispatch is still in flight.
EOC alerts & staff push
Emergency Operations sends its alerts through this channel, and staff notifications now also push to the staff mobile app — so a message reaches residents and the field at once.
A typical workflow
- Compose the alert — type the English title and message; add Spanish or let it auto-translate.
- Pick channels & audience — choose email, SMS, and/or push, then "All constituents" or a segment by language, ZIP, and tags.
- Check the reach — the live preview confirms how many people, and on which channels, before anything goes out.
- Create the draft — the alert is saved as a draft so you can review it.
- Send — one click dispatches it; each resident receives it in their preferred language.
- Watch delivery — the "Sent & scheduled" list shows delivered / sent / queued / skipped / failed counts as they land.
A closer look
A boil-water notice or road closure goes out in minutes. Staff write it in English, the Spanish version is filled in automatically, and a single send reaches the right ZIP codes across email, text, and app push — with a per-status delivery report so nobody is left wondering whether the message arrived.
Staff:
/dashboard/communications. Per-channel pages for SMS, the Mobile App, and Social Media branch off the same bilingual workflow. Residents set their preferred language; messages follow it.Works with
311 / Service Requests for resident status notices · Emergency Operations sends its send-alert through this channel · Records for request correspondence — and any module that needs to notify residents of a status change.