Use-Case Help, Workflow Design, and Paid Enablement
Hatz Support can help when a product feature is not working as expected. Custom workflow design, prompt consulting, implementation strategy, and ongoing use-case delivery are not break/fix support. Those requests should use enablement, customer success, or a paid engagement path.
Support can help with
Troubleshooting errors, tool execution, documented product behavior, or reproducible issues in a workflow, agent, app, artifact, integration, or file flow.
Clarifying documented capabilities and known limits.
Identifying whether an issue is a bug, configuration problem, unsupported capability, or use-case design question.
Collecting the details needed for product support or engineering to investigate.
Enablement or services may be the better path for
"Can someone build this workflow for me?"
"How should I design this customer use case?"
"Can you write or tune my prompts?"
"Can you train my end users?"
"Can someone implement this across multiple customers or tenants?"
"Can Hatz advise on a full operational rollout?"
Free enablement paths
For use-case guidance or workflow-building patterns, start with the free enablement paths when available. Advisory requests such as "how do I build X?" should start with docs or free enablement before ticket creation.
Use Case Workshop: one-to-many help for use-case ideation and workflow-building patterns. Sign up at https://hatz.ai/office-hours#uc.
Feature Fridays: product education, new feature walkthroughs, and examples. Sign up at https://hatz.ai/office-hours#ff.
Monthly Roundtables: broader Hatz product and AI landscape updates for MSP partners. Sign up at https://hatz.ai/roundtable.
Docs, templates, and recordings: self-serve examples and reference material.
Paid enablement and services
Hands-on implementation, scoped workflow buildout, custom training, prompt consulting, or ongoing use-case delivery should use a paid engagement or account-team handoff. Support can route the request, but it is not handled as a break/fix support ticket.
If an existing feature is failing
If you are not asking for design help and instead an existing Hatz feature is failing, create a support ticket. Include the workspace or tenant, workflow/agent/app/chat link, expected behavior, actual behavior, model or tools used, screenshots or errors, and whether production work is blocked.