cause stays with the fire marshal
Cass drafts confident public messaging that never speculates on cause or origin — that call belongs to the fire marshal and investigators, and she writes around it the way a seasoned fire PIO does.
for the fire service
built in the fire service. literally.
Hey Cass was founded by a fire-rescue PIO who kept showing up to working fires as the only communicator on scene. Cass knows your incidents, your chain of command, and why cause always stays with the fire marshal.
she knows the shape of your incidents.
structure fire
wildfire or brush fire
hazmat release
mass-casualty incident
These aren't marketing categories — they're the scenario knowledge Cass actually runs on when your agency sets up as the fire service.
from first hold statement to all-clear
Hold statements in the first thirty minutes, road closures and shelter info across your social channels, WEA-ready alert copy in both character lengths, and the next-update cadence tracked on the operational-period clock.
the ICS-214 keeps itself
Every statement, media contact, and action logs itself into a real ICS-214 activity log while you work — and the after-action report drafts itself from what actually happened.
the quiet weeks work too
Fire prevention week, hydrant testing notices, a clever smoke-alarm reminder, a thank-you to the crew that worked the overnight fire — community posts are in scope, in whatever tone you ask for.
she watches your headlines
Monitoring tracks coverage that mentions your agency — fire, rescue, hazmat, evacuation — so the story never gets ahead of you.
one incident, one screen.
2-Alarm Apartment Fire — Harbor Blvd
active incidentop period 75:56:34
cass
Good evening — you're hour 75 into this one. No public update in 70h 41m. Where I'd go next: push the next one.
3 ready2 released0 media
next steps
No public update in 70h 41m — push the next one before the info vacuum opens
3 drafts ready to review & release
19 doctrine checklist steps to go
Hey Cass
draft a statement · ask anything
Incident info
scene map · 2 on roster
overviewcassstatementslog
2-Alarm Apartment Fire — Harbor Blvd
active incidentop period 75:56:34
statements · ready to release
public statement
Riverbend Fire Rescue is responding to a 2-alarm apartment fire on Harbor Boulevard.
Two residents have been displaced — no injuries reported.
The building is being assessed for structural safety. Cause is under investigation.
Avoid the area if possible to keep access open for emergency crews.
mark releasedIC sign-off required
up next · WEA alert
Avoid Harbor Blvd btwn 3rd–7th. Fire activity. Use Bay Ave.
58/90 · both lengths drafted
overviewcassstatementslog
2-Alarm Apartment Fire — Harbor Blvd
active incidentop period 75:56:34
activity log · feeds your ICS-214
09:12Hold statement released — public
09:40Briefed IC — next update 10:00
09:52Media staging set up on Harbor & 5th
10:04Social post published — road closure
10:31Media inquiry received — Channel 7
10:48Press release drafted — pending IC
11:02IC sign-off — press release
11:05Press release released — public
every action time-stamped — the 214 and the after-action write themselves
overviewcassstatementslog
what the fire service asks us.
Does Cass understand fire-service chain of command?
Yes. Cass is grounded in NIMS/ICS doctrine — she drafts for IC approval, keeps SITREPs separate from public releases, and defers cause and origin to the fire marshal and investigators every time.
Can Cass handle a working incident from my phone?
That's the design center. Open the incident from the scene, and statements, media requests, social posts, the activity log, and press operations all run from one mobile screen.
What does it cost for a fire department?
Beta is free today, and founder seats lock their rate for life. Standard plans publish on the pricing page — no quote walls.
you've been the only PIO long enough.
Request early access →