Built for investigating, not just labeling
Every part of Triagic exists to answer one question faster: what actually happened, and why. Here is the whole product, thirteen surfaces under four verbs, and the guarantees underneath it. One seat plan, with optional add-ons for Checkups and Forms + email.
One path of four: a ticket, from arrival to reply
The most common path, in five steps, each governed by something an admin configures. The other three start from a question in the Console, a number on a dashboard, or a schedule, and run through the same agent.
- 1
The ticket arrives
By webhook, or by a poller that runs every two minutes. Emails, phone numbers, IDs, IP addresses and card numbers are redacted before any of it reaches a model, and then the identity fields are extracted: who this is about, and which account.
- 2
Context is assembled
Vector search pulls the five most similar past tickets with their confirmed root causes. If a PostHog funnel is configured, the step this user fell out of in the last 72 hours comes with it.
- 3
A playbook is chosen
A classifier matches the ticket against every enabled playbook's description and routing hints. Assigning one by hand pins it, and the classifier leaves that ticket alone from then on.
- 4
The agent investigates
Up to 25 tool iterations across the data sources that playbook allows. Every call is read-only, and every call is shown in the UI as it happens. The result is a root cause with evidence cited per system.
- 5
A person answers
The report drafts a reply to the customer. Someone reads it, edits it, and presses Send. The agent has no email tool, by construction.
- The pipeline in detail
Every call in that sequence is logged with its model, tokens, latency and cost. An investigation is several calls and shows up as one folded total.
IntakeLive chat
A chat bubble that rings the people on duty
Put a chat on your own site. A visitor writes, the desktop apps of the available people on the widget's team ring, and whoever accepts can investigate the chat before answering. Live chat is off until Triagic support turns it on for your organization.
- One snippet, allowed sites
- Paste the snippet before the closing body tag on every page that should show the chat bubble. Allowed sites go one per line, and chats from any other site are refused.
- It rings who is available
- Route a widget to a team, or leave the team empty and every available member of the organization is rung. Taking chats is the Available switch in the app's header.
- End-to-end encrypted
- Messages and files are encrypted between the visitor's browser and the agent's app. They pass through a relay run on Cloudflare, and neither Triagic nor Cloudflare can read them. Nothing is stored unless an agent saves the chat as a ticket.
- Investigate this chat
- Pick a playbook and the integrations to use. The same read-only reads as a ticket, every query shown, and a suggested reply that a person sends.
- Save as ticket
- The conversation becomes a ticket, or is added to the visitor's open one, so the evidence stays with the request.
- When nobody is available
- Show a message only, or one of your live forms with embedding turned on. Cloudflare Turnstile can check visitors are human before a chat starts.
InvestigateConsole
Ask across every system at once
Not every question has a ticket behind it. A customer is on the phone, an alert fired, or you want to check something before anyone files anything. The Console is the same agent with no ticket attached.

- Plain language, live tool calls
- Ask what happened. The agent queries your databases, reads logs and checks metrics while you watch each call land. No pre-built dashboard to maintain.
- Developer and support answers
- One toggle sets who the answer is written for. Developer mode gives table names, error codes and log excerpts. Support mode rewrites the same finding in plain English with a suggested reply you can send as-is.
- Pin a playbook to a thread
- Applying a playbook's instructions and allowlist to a whole conversation makes it faster and stops it rummaging where the answer isn't. Leave it unpinned when you genuinely don't know where to look.
- Threads that remember
- Each investigation is its own thread, private to you, replaying the last 20 turns so a conversation builds. Tool traces stay in the UI and out of the model's context, so the audit trail costs no tokens.
- Pick the model per thread
- The picker offers your organization's configured deployments. Order of resolution is the thread's choice, then the install's runtime default, then the fallback.
- Charts in the answer
- Answers can render charts and diagrams inline, from the rows the agent read. Copy, Email and Create issue work on every answer.
WatchDashboards
Numbers you can open without spending AI
An admin describes what the team should watch. AI writes the queries once, and from then on the dashboard is those saved queries, run straight against your own data sources.

- Built from a prompt
- Say what you want to see and pick the sources. Triagic reads their schemas and proposes KPIs and charts. Untick what you don't need, and each one you keep becomes one saved read-only query with its chart.
- Priced before you pay
- The proposal shows a build price per item, and every button that spends AI shows its price first. A per-run cap, $1.00 by default, stops a run that goes over and keeps what it already built.
- Free to open and refresh
- Opening a dashboard, switching between 7, 30 and 90 days and pressing Refresh replay the saved queries with no model. A broken query can be repaired by AI or edited by hand, and the hand edit is free too.
- Your access, your machine
- Queries run from each viewer's desktop over their own connections. A chart over a source someone can't open shows them a locked tile, and results are never sent to Triagic.
WatchReports
A standing brief, every morning
A report is a playbook run on a schedule. Each run lands on the Reports page as a new edition, so the Console stays for the questions you ask yourself.

- Editions, not threads
- One series per playbook, with its cadence, such as every weekday at 09:00 in your time zone. Unread editions are marked and counted in the sidebar, and arrows step through earlier editions.
- Watch it run, or don't
- Open a running report to see the plan and each tool call as it happens. When it finishes, the trace folds into How this report was made, and a desktop notification tells you it landed.
- Follow-up questions under the report
- Ask below an edition and the answer runs under the same playbook and allowlist, with its own tool calls, shared with everyone who can see the playbook.
- Run now, on the org's identity
- Admins can start an edition straight away. Scheduled and manual runs use the organization's system identity and model credentials, never an individual's key, and show up in Usage.
ActIssues
From finding to the tracker
Integrations are how the agent reads your systems. Issue trackers are how a finished investigation leaves Triagic, as a draft a person checks first.
- Create issue, drafted from the evidence
- On any Console answer, report or ticket investigation. The draft carries the summary, root cause, evidence and a link back, and you pick the repository, labels and assignees before anything is posted.
- Comment on the one that exists
- Search the repository's own issues and post the same draft as a comment, or a note on GitLab, instead of filing a duplicate. Issues already filed from the same triage need an explicit confirmation.
- A batch from one prompt
- Paste a roadmap or a list of bugs into the Console and ask for issues. The agent drafts up to 15 at once, checks each against the repository's open and recent issues, and turns matches into updates. Nothing is filed until you review the batch.
- Traceable both ways
- Filed and commented issues show as linked issues on the ticket, and each filing and comment writes an audit entry with the provider, project and issue key.
ControlGuarantees
What it can't do is the feature
You are about to hand an AI agent credentials to production. The guarantees below are enforced in the tool layer and in the code path, not by asking a model to behave.
- Read-only, filtered before the run
- Write, mutate and delete tools are filtered out before any agent run sees them, when a server connects and again at every dispatch. Catalog integrations expose only the tool names verified as reads; any other server has to annotate a tool read-only or it isn't exposed at all.
- Your credentials, least privilege
- A handful of upstream servers have no read-only mode of their own, and those are named in the docs. Point every integration at a read-only user or a read-scoped token and the guarantee stops depending on any single layer being bug-free.
- PII redaction on every path
- Emails, phone numbers, national ID numbers, IPv4 addresses and Luhn-valid card numbers are stripped from the subject, body and metadata before a prompt is assembled. Background triage, the Console, ticket chat, classification and similar-ticket search all run it. None of them skip it.
- Encrypted at rest, twice
- Credentials are AES-256-GCM encrypted under the platform key, and re-encrypted on arrival under a key that never leaves that machine. No endpoint and no admin screen returns a plaintext secret; API responses carry masked values only.
- Shared credentials without sharing them
- A member can use a shared integration and cannot recover its secret or repoint it. The member-facing view has no credential fields at all, not even masked ones, and editing shared configuration takes an admin.
- Append-only audit log
- Every mutation to authentication, organizations, teams, playbooks, integrations, issue trackers, filed issues, emails sent and playbook assignment writes a row with actor, action, target, before and after, and a timestamp. Admins only, enforced by the service rather than hidden in the nav.
- A spend cap that actually stops runs
- One monthly USD number for the organization. Every LLM call is logged individually with its model, token counts, latency and cost, snapshotted at write time so correcting a price later never rewrites history.
- Cost and latency you can read
- The Usage page carries totals, per-model latency percentiles, a per-task split and a daily cost chart, with links back to what caused each call. An investigation folds its several calls into one number.
What Triagic deliberately doesn't do
These are design decisions, not gaps in the roadmap. Each one is the reason someone is willing to connect production in the first place.
- It doesn't write to your systems
- There is no write path to enable. The tool filter is global and applies to ticket investigations, Console questions and checkups alike.
- It doesn't email anyone
- The agent has no email tool. Not disabled, not gated behind a permission. A person opens the draft, edits it, and presses Send.
- It doesn't copy your data anywhere
- No pipeline, no warehouse sync, no third-party copy of your database. The app runs on your machine, against your systems, over your network. If you need a VPN to reach production, so does Triagic.
- It doesn't resell you model capacity
- Your provider key, your contract, your rate limits. Triagic never proxies model spend through a shared account.
- It doesn't reclassify old tickets quietly
- Classification runs at ingest or on an explicit re-investigation. A ticket already in the inbox will not silently pick up a playbook written afterwards.
- It doesn't certify anything
- The SOC 2 readiness review is an evidence-collection exercise, not an audit and not a certification. Only a licensed CPA firm can perform a SOC 2 examination.
See it work on a real ticket
Every feature on this page is unlocked from day one. Start a 14-day free trial, no credit card required.


