Keryx Message
Secure messaging that already knows which incident you mean.
Keryx Message is the internal chat application for public safety teams — call takers, dispatchers, supervisors, and responders — for exchanging messages and emergency data in seconds. It runs inside an agency-controlled channel that is encrypted, retained, and tied to the incident record from the first message.
What it does
Radio carries a voice, not a photo. So when a responder needs to send a picture of a licence plate, a dispatcher needs to push a caller's exact location, or a supervisor needs to reach three units at once, teams reach for whatever is in their pocket. That usually means a consumer messaging app: fast, familiar, and entirely outside the agency's control. Nothing is retained, nothing is linked to the incident, and the conversation that decided a response lives on a personal phone.
Keryx Message gives the agency its own channel with the same speed and none of the exposure. Conversations are organised around incidents, units, and roles rather than ad-hoc groups. Location, media, caller details, and structured incident data are shared with one action and open in context on the other end. Every message is encrypted, timestamped, and kept according to the agency's retention policy — so the thread that shaped a response is part of the record, not a screenshot someone has to be asked for.
Capabilities
Incident rooms that create themselves
When Keryx Dispatch opens an incident, a room opens with it — assigned units, the dispatcher, and the record already inside. Units joining the incident join the room; when the incident clears, the room archives with it.
Emergency data, not just text
Share a location pin, caller details, a photo, a video still, a document, or structured incident data with one tap. Recipients open it in context — a pin lands on their map, a record opens in their console — rather than as a loose attachment.
Acknowledged, not merely delivered
Priority messages ask for an explicit acknowledgement. Who has confirmed and who has not is visible to the sender, and anything unacknowledged past the threshold escalates to a supervisor or to radio automatically.
Cross-agency rooms with scoped access
Invite a neighbouring agency into an incident room for mutual aid. They see the incident thread and shared data for as long as they are part of the response, and nothing else in your system.
Built for the field
Mobile-first with a low-bandwidth mode, offline queuing that sends when coverage returns, and push notifications tuned to priority. Works the same on a handheld, an in-vehicle terminal, and the dispatch console.
Retained, auditable, exportable
Every message and attachment is stored immutably with author, time, and incident. Retention follows agency policy, legal hold is a switch, and any thread exports as an evidential record on request.
Standards and interoperability
Built on the open specifications the emergency services community has already agreed on, so it connects to what you run today and what your network is migrating toward.
- End-to-end encryption
- Messages and attachments are encrypted on the device and in storage; the agency holds the keys, not a third party.
- CJIS Security Policy
- Designed to operate within the access, audit, and encryption controls agencies handling criminal justice information are held to.
- GDPR
- Retention, minimisation, and subject-access workflows for agencies operating under European data protection law.
- EIDO
- Shares structured incident data in the standard Emergency Incident Data Object format so it opens correctly in other Keryx modules and partner systems.
- SAML / OIDC
- Single sign-on against the agency's identity provider, with multi-factor authentication enforced for every account.
- APNs / FCM
- Native push delivery on iOS and Android with priority classes, so an urgent message breaks through where a routine one waits.
Why centres choose it
— Context arrives with the message
Nobody asks “which call?”. Because rooms are tied to incidents, every message already carries the who, where, and what — and the data shared inside it opens in the right place.
— Replaces the group chat nobody should be using
Teams adopt it because it is as fast as the consumer app they were using. The agency adopts it because, for the first time, that traffic is encrypted, retained, and theirs.
— Proof, when it matters
After-action reviews, complaints, and court requests are answered from a timestamped record, not from screenshots recovered off personal phones.
Part of the Public Safety suite
See Keryx Message inside a live incident room.
We will open an incident with your team, share location, media, and structured data across the room, and show you the retained record afterwards.