Feature Requests

We should have the right to publish/hide apps at will.

I would like the ability to upload .pcap files for packet analysis.

Providing a mobile-friendly version or dedicated app for the platform would allow users to access tools and features on the go, ensuring flexibility and convenience across devices. Request from PCH Customer

This request proposes adding a user profile configuration feature to Hatz AI Secure Chat. The feature would allow users to store personal and professional details such as their name, role, industry, and communication preferences so the AI can automatically apply this context in future conversations. Major AI chat platforms already provide similar personalization capabilities, and offering this within Hatz AI would support a seamless transition for users seeking a secure alternative. Problem Users who move from mainstream AI chat tools expect the system to remember basic information about them. Without profile persistence, Hatz AI Secure Chat requires users to repeatedly restate who they are and what they do. This creates friction and makes responses feel less consistent. As a result, the experience feels less polished compared to free tools that users are accustomed to. Proposed Solution Introduce a secure, user-controlled profile area within Hatz AI Secure Chat where individuals can enter details such as their name, job title, organization, role, and any preferred context. The AI should automatically reference this stored information when generating responses to ensure continuity across chats. All data should remain private and editable, with clear controls over what the AI can use. Benefits Adding this feature increases personalization, reduces repetitive input, and enhances the overall user experience. Matching the capabilities of other widely adopted AI tools will make it easier for users to adopt Hatz AI as their primary platform while benefiting from its stronger security model. Consistent context also improves accuracy and reduces variability in chat outputs. Use Cases A business professional could save their role and industry so Hatz AI consistently tailors guidance to their field. Employees within an organization could store their team and responsibilities to receive more relevant internal support. New users switching from other AI platforms would find the onboarding familiar, which lowers the barrier to adoption and strengthens the appeal of Hatz AI as a secure alternative.

This request proposes adding optional, session-scoped memory to secure chat sessions in Hatz AI. Allowing the system to retain relevant context across interactions would create a more continuous, user-friendly experience comparable to what users expect from leading AI platforms. Problem At present, secure chats in Hatz AI operate as isolated sessions with no retained context. Users must repeatedly re-explain background information, preferences, and ongoing work. This creates friction and discourages adoption of secure chat for longer workflows. Additionally, many end users are accustomed to memory-enabled experiences in other AI platforms such as ChatGPT. When they switch to Hatz AI’s secure chat, the lack of continuity feels like a step backward, reducing engagement and limiting the perceived value of the secure environment. Proposed Solution Introduce an optional memory system for secure chat sessions that allows relevant context to persist across interactions. Users should have explicit controls to enable or disable memory and to view, edit, or delete stored items. Memory categories should be configurable, allowing users to decide what types of information can be retained. All data must remain encrypted and isolated, maintaining Hatz AI’s existing security guarantees while enhancing usability. Benefits A persistent memory feature would significantly improve conversational efficiency and consistency. It would reduce repetitive setup, support ongoing workflows, and create a user experience aligned with what customers already expect from modern AI tools. By making secure chat feel more familiar and intuitive, Hatz AI can encourage wider adoption and deliver a more competitive, high-quality experience. Use Cases Teams working on multi-step projects could maintain evolving context across secure chats without starting from scratch. Support scenarios could preserve relevant details across multiple interactions. Professionals using Hatz AI for research, planning, or iterative drafts would benefit from persistent preferences and project history, allowing secure chat to match the fluid experience they are used to in other AI platforms.

Would like to see the AI Phone agent have the option to create a ticket in CW rather than sending an email. Or could have both actions.

We have had requests to cap user usage so you don't have one person taking up 90k credits and the rest of the organization suffers because of that one person. They would like to take that high user and cap them so everyone can have equal access to the models

Requesting the capability to have an agent start with a preselected message such as an intro to how to use the agent, a question for the user, etc

This request is for the ability to configure the ConnectWise integration at an organization level rather than requiring each user to enter API credentials individually. At present, every user must input the company ID, public key, private key, and client developer ID before they can enable the integration. This creates unnecessary repetition and increases the exposure of sensitive credentials. This request aims to allow an admin to enter these details once during the initial setup. Users would then only need to connect the integration to their profile without entering any key information. This reduces risk, limits access to private and public keys, and simplifies onboarding for anyone who needs to use the integration. This improvement would strengthen security practices and streamline the experience for teams relying on ConnectWise throughout the platform.

Currently, all users can individually connect integrations like Microsoft Teams, outlook, Excel, with no way for administrators to restrict or control who is allowed to enable them. Tenant-level and/or role-based controls that allow admins to enable, disable, or limit specific integrations for certain users or groups. This would improve security, compliance, and manageability especially for MSP environments. Also giving the MSP the ability to turn on integrations under the admin portal for the customer instead of requiring "client admin"