Feature Requests

In addition to the reporting dashboard, having the ability to setup automated usage reports per tenant would be very convenient for clients wanting to track how much they're users are using the product.

Currently, workflows are rigid and linear - they run every step regardless of what's actually needed, and they can't gather additional information or adapt based on the specific request. This creates inefficiency and incomplete outputs. What I am trying to do currently is create a workflow for Opportunities that automatically creates a scope of work and tells the user what products will be needed. What This Ideal Workflow Does: Starts Smart - When an opportunity comes in, the workflow: Reads the opportunity details. Automatically searches all our tools for everything we know about this client (Adding to the "Unified API access" request) Asks follow-up questions if anything is unclear or missing. (Adding to the "continue chat" feature request) Adapts to Need - The workflow intelligently determines what's required: If the request mentions replacing a server, it activates the "Server Standards" module. If it's about networking, it activates the "Network Configuration" module. Only runs the steps that are actually relevant to this specific request. Keeps Humans in Control - At each step: Users can pause and have a conversation to refine requirements. The system asks "Ready to proceed to the next step?" before moving forward. Maintains all context from previous conversations. REAL-WORLD EXAMPLE Opportunity comes in: "Client needs server upgrade" Workflow pulls all client history, current infrastructure, past tickets. Identifies this needs the "Server Standards" step. Skips irrelevant steps like "Website Development" or "Security Audit". Allows user to discuss specific requirements at each step. Proceeds only when user confirms readiness.

Problem As an MSP, we rely on multiple platforms (Autotask, ITGlue, Lifecycle Insights, RMM, Microsoft 365, etc.). Each has an API, but they remain siloed. My technicians constantly bounce between systems to find data, create tickets, check configs, or pull metrics. This wastes time and increases errors. Proposal Allow Hatz.ai to connect to any third-party tool via API keys or OAuth. Admins could register integrations (like ITGlue or Autotask), define permissions, and then technicians could query those systems directly through the AI. How it would work Admin securely provides an API key (or OAuth connection) inside Hatz.ai . Permissions are scoped (read-only, write access, specific endpoints). In conversation, a tech can say: “Create an Autotask ticket for this incident and link the client’s ITGlue documentation.” “Pull all Microsoft 365 licenses expiring this month.” “Summarize Lifecycle Insights metrics for Client A.” The AI transparently shows which API calls it will make, executes them, and returns results with links or summaries. Benefits Single pane of glass: Techs interact with Hatz.ai instead of juggling 5+ portals. Faster problem-solving: AI can cross-reference data (e.g., Autotask ticket + ITGlue network diagram + RMM status). Compliance-friendly: Logs show every API call, who triggered it, and what data was returned. Scalability: Once the framework exists, any API-enabled tool can be plugged in—no custom dev each time. Example MSP Use Cases “Check ITGlue for firewall config and confirm against Datto RMM patch compliance.” “Update Autotask ticket notes with Lifecycle Insights risk data.” “List all M365 mailboxes over 90GB and cross-reference with Autotask licensing.” Why it matters With this, Hatz.ai stops being just “smart chat” and becomes the operations nerve center. It glues the MSP stack together through natural conversation, making every tech more effective and every workflow faster.

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.

I was doing a demo for example and an app about calculating time wasted in meetings was the first app to show up on the Automations page. There are also apps that may violate an acceptable use or other HR policy that can be added/created.

It would be game-changing if Hatz.ai supported real-time voice conversations, similar to how ChatGPT offers a voice mode. https://chatgpt.com/features/voice/ Instead of typing everything, users could speak naturally and hear the AI respond with a voice of its own. This would make interactions feel faster, more human, and more accessible—especially when multitasking or away from a keyboard. Key benefits: Hands-free productivity: Great for brainstorming, note-taking, or troubleshooting while on the move. Accessibility: Supports users who prefer or need audio over text. Engagement: Conversations feel more natural and interactive than chat windows. Think of it like having a smart colleague you can talk to, not just type at.

We would like to show clients who are using Hatz how much time they are saving, as we have people who are using tons of usage! But not a way of telling them "you're saving 60 hours a week by using AI" if there was a way we could break this down, saying "you've used this automation, this saved has 10 hours" etc. As well as linking this to the usage so it's easier to explain to clients where time is being saved and why their usage is so high.

Provide the ability to select one or more user groups when publishing an Automation/Workflow. Only users within the selected groups should then be able to see and use the automation.

I’d love to see a dictation/voice-to-text input option in ChatGPT. Typing out long, detailed prompts can be time-consuming, and being able to speak naturally would let me provide more thorough context, faster. I use dictation in other tools like Copilot and find it extremely useful. Having a microphone button to speak prompts directly in ChatGPT (with support for punctuation and auto-formatting) would save time, improve accessibility, and make interactions feel more natural.

To be able to see what images are attached in a chat, maybe a thumbnail so I know what image is referred.