From what Ive seen and looked int thus far, not quite what you're describing yet, but there's a piece of the foundation already there. v4 NewUI ships a Constituents module — a searchable contact database built to manage community contacts for phone-based caller lookup, so operators can auto-fill caller info and see notes/warnings when a call comes in. Right now that's name, multiple phones, email, address, and a free-text notes/warnings field — no DOB, no photo upload, no vehicle field, and no linked "detainment" or mobile-booking workflow tied to incidents. Building out what you're picturing — a full subject profile with medical flags, photo, vehicle info, and a booking-style workflow searchable across tickets — is a real feature ask, not a small tweak, so I wouldn't expect it without someone filing a concrete request. Worth opening an issue on the GitHub tracker with your specific fields/workflow so it's in front of the maintainer. One thing worth thinking through on your end regardless of whether TicketsCAD builds it: a private security company storing DOB, medical conditions, and photos on members of the public — plus a "mobile booking" record tied to a detainment — is a different animal than the volunteer fire/EMS/CERT use case this project is built around. That kind of data (especially medical) usually comes with real retention, consent, and liability questions depending on your state, since private security doesn't have law enforcement's booking authority. Worth running past whoever handles compliance/legal for your company before you build a workflow around it, separate from whether the software supports it.
P25 support (vs. the existing MotoTRBO/DMR):
Current radio messaging is built around DMR radio messaging, and historically that integration work centered on MOTOTRBO SMS messages over a radio network so units get dispatch alerts on their radio screen. DMR and P25 are different digital protocols under the hood, so P25 support isn't just flipping a switch on what's there — it'd be its own integration effort. I haven't seen it on any published roadmap. Same advice: file it as a feature request on the repo issue tracker if it's something you need — that's how DMR and the other channel integrations got prioritized in the first place.
What the Zello integration actually gets you as a dispatcher:
It's a real built-in integration, not just a link-out — the repo ships a Zello WebSocket proxy as part of the app. Practically, that means push-to-talk channel traffic can flow into the same console you're dispatching from instead of needing a separate Zello app window open — so PTT comms sit alongside your incidents, units, and the rest of the communications stack the same way SMS, email, and Slack do.
As a side note zello has 2 "flavors of access" Consumer and Commercial. both have drawbacks but in your case would need to be commercially put together and that's a monthly/per user subscription (verify with TOS before you take this as face value)