Customer Service / Customer Support Live
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.
- Runs on a schedule
- ~7 credits per run
- v1.0.0
What does Complaint Tracking do?
Complaint Tracking is a production AI agent in the customer service section of the Leverge agent store, built for the customer support process. 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. It runs on a schedule (every monday at 09:00), works through 4 steps and returns 5 outputs, including complaint handling.
What it needs
-
Complaint register
One row per complaint, with what was promised and when it was last touched.
-
Policy
What it does
- Reading the complaint register
- Checking each complaint against what was promised
- Writing the brief
- Preparing the complaints brief for approval
What you get back
- Complaint handling
- Brief
- Commitments missed
- Every open complaint
- Message to complaints oversight
After each run it asks: “Does this reflect where the complaints are?”
When it runs
Runs on a schedule — Every Monday at 09:00.
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.
-
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.
-
Order Status Response
Match a customer asking where their order is to the right line in the order book, and draft a reply that states only what the record actually confirms.
Next Step
Deploy Complaint Tracking, 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.