ctHelixMobile™ is the field-mobile platform of the ctHelixOne™ suite. Map-first, offline-tolerant, and built so the officer in the seat has the same picture the dispatcher has — minus the noise they don’t need.
The early surface ships as /m inside ctHelixCAD™ at launch. The full platform is in development.
First / next
ctHelixMobile™ is a planned product. The PIN-based companion that ships inside ctHelixCAD™ at launch is the operating early version — evolving toward the broader platform from there.
A PIN-based unit and supervisor companion that ships as part of ctHelixCAD™. Field units self-set status, see assignments, and add notes. Supervisors get a scoped read-only board. Included in every ctHelixCAD™ deployment when CAD launches.
See the /m companionThe broader field-mobile platform that subsumes /m and extends well past it — full field reports, evidence capture, map-first navigation, offline tolerance, and tight integration with ctHelixRMS™.
Talk about timingWhat ctHelixMobile™ will do
The dispatcher console is the wrong UI for the seat. ctHelixMobile™ is built around the questions an officer actually asks the radio.
The map is the primary surface — units, posts, incidents, and self all live on one canvas. Tap to act; long-press to inspect.
Installs from a browser. Updates instantly. Works on the phone or tablet your officer already carries.
Loses signal, doesn’t lose data. Reports, photos, and notes queue locally and sync on reconnect with conflict-aware resolution.
Fill out structured forms in the vehicle. Reports submit into ctHelixRMS™ for supervisor review with the same audit trail as console-entered records.
Geo-stamped, time-stamped, hashed at capture. Evidence travels with its provenance into the records system.
Acknowledge dispatches, set status, and notify dispatch — all without speaking, when speaking isn’t safe.
Same PIN model that powers ctHelixCAD™’s /m surface. Sliding sessions, separate auth surface, no shared identity with the dispatcher console.
Configurable per agency. Use-of-force, FI cards, vehicle inspections — whatever your operations actually fill out.
A note on the auth model
ctHelixMobile™ inherits the auth model that already runs on /m: PIN-based field auth, short-lived sliding tokens, no shared identity with the dispatcher console. A compromised PIN never grants console access.
Field officers writing structured reports inside ctHelixMobile™ will use a stronger personal identity tied to their roster record — but still isolated from the console’s identity surface. Your security team gets the model documented before deployment.
Tell us what your officers actually do in the vehicle — we’ll show you the surface we’re building, and we’ll tell you when it’ll be ready for yours.
