Documentation
Build, support and ship on your own terms.
Everything you need to run TicketMan AI yourself: the platform and its self-healing support loop, and the drop-in Diagnostics SDK that feeds it. Screenshots are being added; the reference below is complete.
Platform
Overview
What TicketMan AI is: a self-hostable, general-purpose software-support platform.
The self-healing loop
The Dev Server plan: from a captured crash to a shipped fix, with a human wherever you want one.
Self-hosting quickstart
The moving parts of a self-hosted TicketMan AI deployment and how to bring them up.
AI and models
Bring any of five model providers, or run fully local, with editable prompts and a full audit log.
Security and data ownership
How TicketMan AI keeps your data, keys and AI boundary inside your own walls.
Diagnostics SDK
Overview
Drop-in .NET, Node.js and Python packages that turn crashes into pre-categorized, AI-triaged tickets.
Quick start
Install, set two environment variables, and start reporting crashes to TicketMan AI.
Configuration reference
Every environment variable the Diagnostics SDK reads, with defaults and activation rules.
What data is collected
A field-by-field inventory of what the SDK sends, what is masked, and what is never collected.
Desktop integration
Capturing UI-thread exceptions in WPF and WinForms, and crash semantics on shutdown.
Troubleshooting
When reports do not arrive: the self-log, spool, rate limits and container gotchas.
User manual · Requesters
Welcome to TicketMan
How to sign in to TicketMan and find your way around after you log in.
Getting help
How to open the Get Help page and choose the right kind of request.
Creating a ticket
How to fill in a request form, add attachments, and submit your request.
The help assistant
How the help assistant answers your question before a general request becomes a ticket, and how to still create the ticket.
My tickets
How to find the tickets you have submitted and understand their status.
Following your ticket
How to read your ticket page, reply, and reopen a resolved ticket within 14 days.
Email and your tickets
How sending and replying to email can open, update, or continue a ticket.
User manual · Agents
The ticket workspace
How to read the dashboard, filter and sort the queue, and act on one or many tickets at once.
Working a ticket
How to read a ticket's detail page and change its status, priority, and assignment.
Conversations and replies
How to reply to a requester, add internal notes, and see whether a message went out.
AI assistance
The on-demand and automatic AI help available on a ticket, and what happens when it is not set up.
Confidential tickets
What the confidentiality level badges mean, what a redacted ticket looks like, and how to raise or lower a level.
Reopened tickets and follow-ups
The 14-day window for reopening a resolved ticket, and how a follow-up ticket links back to the original.
The diagnostics dashboard
How error reports from monitored applications become tickets, and how to read the diagnostics dashboard and panel.