Feature Requests

Would love to have a HatzAI desktop app that connects to everything on my laptop so that I can reference things and take action in apps, shell scripts, etc.

Currently, when a chat, agent, or workflow generates a document or file-based deliverable on the Hatz.ai platform, it produces a randomly generated AWS link. This link is publicly accessible to anyone who has it, which constitutes "security by obscurity" which is not a recognized or acceptable security control. This creates several critical concerns for enterprise and regulated customers: • Data Exposure Risk o Generated files are not access-controlled, meaning sensitive outputs could be accessed by unintended parties. • No Integration with Customer Storage o There is currently no ability to write outputs directly to customer-owned storage repositories such as Microsoft 365 (SharePoint/OneDrive) or internal/external file systems. • Compliance & Regulatory Gaps o Without the ability to route files to governed storage, customers cannot maintain their compliance posture or meet data residency and handling requirements. • Security Framework Control Failures o This limitation makes it difficult or impossible to satisfy technical controls required by frameworks such as SOC 2, ISO 27001, NIST, HIPAA, and others. Requested Features: Implement access-controlled, authenticated file links (at minimum) to replace open AWS URLs. Enable native integrations with customer storage repositories, starting with Microsoft 365 (SharePoint/OneDrive) and common file systems. Allow customers to define where file outputs are stored, ensuring data stays within their governed environments. This is a foundational capability for enterprise adoption and security-conscious customers. Thank you for considering this request!

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

There is no ability to write to sharepoint, one drive, post files in teams. This is really killing automation flows as I cannot properly create anything. I have gone round and round and all the permissions are good, everything is setup. Except hatz cannot write/upload anything to sharepoint/onedrive or teams. There by killing agents and workflows! I have talked to larper and I have worked with support.

Hi team! I am submitting a feature request on behalf of our Sales team. We are receiving increasing client interest in a dedicated Microsoft Excel Add-in to assist with spreadsheet data manipulation, analysis, and automation directly within the Excel application.

Problem: Our technicians frequently use Microsoft Teams for communication, collaboration, and incident resolution. While Hatz.AI 's chat and agent functionalities are incredibly valuable for accessing information, troubleshooting, and generating solutions, there's currently a disconnect. Technicians often have to switch between Teams and the Hatz.AI platform to leverage AI assistance. This context switching disrupts their workflow, adds friction, and can delay resolution, especially when dealing with complex problems that require rapid access to AI-driven insights during ongoing conversations. Proposed Solution: We request the development of an official integration that allows Hatz.AI 's AI chat and agent capabilities to be seamlessly accessible directly within Microsoft Teams. This could manifest as: A Teams App: A dedicated Hatz.AI app within Teams where technicians can initiate chats with the AI, access specific agents, or trigger AI actions without leaving the Teams interface. A Teams Bot: A Hatz.AI bot that can be invoked within team channels or private chats to answer questions, provide information, or perform tasks using Hatz.AI 's underlying AI models. Message Extensions/Connectors: The ability to highlight text in a Teams conversation and send it to Hatz.AI for analysis, summarization, or to generate a response, which can then be inserted back into the chat. Expected Benefits: Implementing this integration would significantly enhance the value and usability of Hatz.AI for our organization, leading to: Improved AI Usage & Adoption: By making Hatz.AI readily available within their primary communication tool, technicians will naturally integrate AI assistance into their daily workflow, increasing overall AI adoption. Streamlined Workflows & Productivity: Eliminating the need to switch applications reduces context-switching overhead, allowing technicians to stay focused and work more efficiently. Faster Problem Resolution: Technicians can get instant AI assistance for complex issues directly within their resolution conversations, accelerating troubleshooting and decision-making. Enhanced Collaboration: AI-generated insights and solutions can be easily shared and discussed within Teams channels, fostering better collaboration and knowledge sharing among team members. Reduced Training Burden: Integrating AI into a familiar environment like Teams may reduce the learning curve for new users and encourage broader utilization. We believe this integration would be a game-changer for improving technician efficiency, leveraging Hatz.AI 's power more effectively, and ultimately leading to faster and more consistent problem resolution across our operations.

At the moment this is only available to the MSP admin, but allowing the tenant admin access to configure custom roles and permissions beyond the basic Chat Only, General and workshop users. On our Tenant I have setup some custom roles that nearly are identical to the normal permissions with the exception of the group administrator, a specifically designed role that I can give to a Department head or manager that they can administer the groups etc. but not be able to adjust any of the tenant settings.

Best of both worlds! The interaction of an Agent and the ability to invoke a multistep workflow as needed within the same conversational context. An example could be chatting with a market research agent, pulling information from web sources for your comparison, and then calling a workflow to carry out several required tasks before creating a document.

Summary Allow MSP partners to assign unique custom subdomains to each of their tenants within the Hatz MSP portal, replacing the default shared URL (e.g., msp.hatz.ai ) with a tenant-specific subdomain (e.g., clientname.hatz.ai ). Problem Statement Currently, all tenants managed through the MSP portal share the same base URL. This creates a lack of differentiation between clients and limits the MSP's ability to deliver a white-labelled or branded experience to each of their customers. From a client's perspective, logging into a generic shared URL reduces the perception of a tailored, professional service. Proposed Solution Introduce the ability for MSP administrators to configure a unique subdomain for each tenant they manage, using the format: [clientname]. hatz.ai Key Requirements Per-Tenant Subdomain Assignment MSP admins should be able to set or edit a subdomain for each tenant from within the MSP management portal. Subdomains should be unique across the platform to avoid conflicts. Subdomain Routing When a user navigates to clientname.hatz.ai , they should be automatically scoped to that tenant's environment — including branding, users, and settings.