Customer Service / Customer Support Live
Technical Issue Diagnosis
Read the diagnostic export a customer sent in alongside what they reported, and work out what the evidence actually shows — separating what the logs prove from what the symptom merely suggests.
- Run on demand
- ~6 credits per run
- v1.0.0
What does Technical Issue Diagnosis do?
Technical Issue Diagnosis is a production AI agent in the customer service section of the Leverge agent store, built for the customer support process. Read the diagnostic export a customer sent in alongside what they reported, and work out what the evidence actually shows — separating what the logs prove from what the symptom merely suggests. It runs on demand, works through 3 steps and returns 5 outputs, including what the evidence points to.
What it needs
-
What the customer reported
-
Diagnostic export or log
The log, HAR, or diagnostic bundle the customer attached.
-
Environment
What it does
- Reading the diagnostic export
- Working out what the evidence shows
- Writing the next steps
What you get back
- What the evidence points to
- Next steps
- Candidate causes
- What the log actually proves
- What is missing from the export
After each run it asks: “Was this the right read of the log?”
When it runs
Run on demand
Oversight
Runs under scoped, least-privilege credentials with every action written to an audit log. Anything that moves money, alters a contract or reaches a customer requires human approval before it executes.
Customer Support
Other agents in customer support
Ticket triage, resolution drafting and feedback analysis
-
Account Change Request
Check whether the person asking for an account change is entitled to make it, then draft either the confirmation or the verification request. Nothing is changed and nothing is sent.
-
Chat Transcript Summary
Turn a live-chat log into the two things needed afterwards: a ticket record the next agent can act on, and a clean transcript the customer can be sent.
-
Complaint Tracking
Track every open complaint against the commitments made to that customer — which are past the promised date, which have gone quiet, and which were closed without the customer ever agreeing they were.
-
FAQ Gap Monitor
Check the published FAQ against what agents are actually replying, and find the entries that have quietly gone out of date as well as the questions that were never added.
-
Inquiry Self-Service Deflection
Work out how much of last month's inbound could already have been answered by the help centre, which articles were missing, and which questions should never be deflected at all.
-
Knowledge Article Drafting
Draft a publishable article from a resolved case, checked against the existing knowledge base first so it extends what is there instead of quietly contradicting it.
Next Step
Deploy Technical Issue Diagnosis, or adapt it
It runs as-is against the inputs above. Most deployments diverge — a different source system, a different tolerance, a different approval path. A 30-minute technical call establishes which.