# Triagic documentation

> What Triagic is, how the web portal and the desktop app divide the work, and where to start depending on who you are.

Source: https://triagic.com/docs

Triagic turns a support ticket into an answer. A ticket arrives, Triagic extracts who
it is about, looks up that user's funnel drop-off, finds similar past tickets, and
then an AI agent investigates **read-only** across your own infrastructure
(databases, logs, metrics, error tracking, Kubernetes, cloud) and writes up a root
cause with the evidence it found. A person reads that, edits the suggested reply and
sends it. [Email goes out only when a human presses Send](/docs/desktop/tickets#emailing-the-customer).

The same agent runs [checkups](/docs/checkups): standing read-only procedures (a
warehouse cost review, an access review, a SOC 2 readiness walkthrough) pointed at
your whole environment instead of one ticket.

Nothing is hosted for you. The agent runs on your machines and talks to your systems
with credentials you supply.

## Two pieces, one product [#two-pieces-one-product]

- [Web portal (this site)](/docs/admin): Where an organization is administered: people, teams, playbooks, shared credentials, AI provider keys, spend caps, audit log, billing. Admin work only; no tickets are worked here.
- [Desktop app](/docs/desktop): Where the work happens: the ticket inbox, investigations, the Console, history and usage. It runs the MCP tool calls locally against your infrastructure.

The portal is the source of truth for configuration. The desktop app pulls that
configuration down on a schedule and executes against it. See
[How configuration reaches the desktop](/docs/concepts/config-sync) for the
mechanics.

## Start here [#start-here]

**You are setting up an organization for the first time.**
Read [Architecture](/docs/concepts/architecture), then work through the
[Admin setup checklist](/docs/admin). Budget about half an hour: most of it is
pasting credentials.

**You were sent a login and told to install the app.**
Go straight to [Install the desktop app](/docs/desktop/install), then
[Sign in](/docs/desktop/sign-in). You do not need anything from the admin section.

**You want to write a good playbook.**
[Anatomy of a playbook](/docs/playbooks) explains each field and what the agent
does with it; [Example playbooks](/docs/playbooks/payments-and-payouts) are five
complete, copyable ones.

**You want numbers the whole team can open.**

- [Dashboards](/docs/desktop/dashboards): KPIs and charts over your own data. An admin describes one and AI writes the queries once; opening and refreshing it never spends AI.

**You want to review something rather than work tickets.**
[What a checkup is](/docs/checkups) covers the shipped library, running one, and how
findings are tracked between runs.

**You are evaluating Triagic.**
[Roles, plans and seats](/docs/concepts/roles-and-access) covers the 14-day free
trial, what a seat costs and who can do what. [Security model](/docs/admin/security)
covers what leaves your network (very little) and what does not.

## Conventions in these docs [#conventions-in-these-docs]

> **Note:** Portal vs. desktop
>
> Pages under **Administration** describe the web portal you are reading this on.
> Pages under **Desktop app** describe the installed application. Where the same
> concept exists in both (playbooks, integrations, AI providers), the portal is
> authoritative and the desktop is a mirror.

Anything shown as `code` is a literal value: a field name, a key, an environment
variable, a URL path. Anything shown in **bold** is a label you will see on screen.