Feature Requests

It would be great to have an Export button available in the Admin Portal that allows us to easily download usage data (e.g. training stats, login activity, etc.). This would help with reporting, tracking adoption, and sharing updates internally or with customers.

I'm using the Microsoft integration to pull my daily agendas and it's working fine, but all event times are showing in UTC. Please add a time zone setting so times can be adjusted to the user's local or preferred time zone. It should also automatically adjust for daylight-saving changes.

We had a request for historic usage adoption data, to see how adoption has progressed over a few months. I think this would be a great addition. Just the historic number of credits used per user for a couple months to see who is using the platform consistently

Add the ability to edit a prompt that has already been sent (see attached screenshot of ChatGPT for an example). Our clients often use this feature because they share chats and sometimes don't get a prompt right the first time.

It would be nice to have an option to prefill an input or set a default choice for user inputs in the workflows. For example, if I have a text box that asks the user to list the common tools that they use, it would be nice for that text box to pre-fill with the common tools that all employees use.

I am working on a workflow in the workshop, and it will require someone to understand how to use the app. There is currently not a field where I can add instructions for the end user on the apps purpose and instructions for the workflow's use. This would be a great addition to the workflow items that would help end users understand how to use more complex apps.

When copying the results from an AI-generated draft email, the copied content includes internal “thinking” information (e.g. reasoning steps, placeholder notes) . This makes the output less polished for direct use or sharing.

Allow Hatz to function as an MCP client that can connect to custom MCP servers, enabling access to user-developed integrations built on the MCP protocol. These should be available to chat, automations and workflows once connected.

Session Custom Instructions (essentially user-level context prompt) so that initial session context can be set at user level for general non-automation/workflow sessions.