Triage customer support before you reply
ChatGPT sorts a batch of support tickets into answer now, needs a fact, and can wait, before anyone writes a reply.
A queue with one next action per ticket, so the urgent ones are not buried under the rest.
- 1
Paste subjects and first lines
Enough to see the ask. Leave off attachments and anything you would not read aloud.
- 2
Work Answer now first
Open those tickets in the help desk. The other bands wait until this band is empty.
- 3
Ask for the missing fact
On Needs a fact, send the question the triage named, or fetch it yourself. Do not guess.
The prompt to paste
Triage this customer support queue. I will paste subjects and the first lines. I will not paste passwords, payment numbers, or full account records. Sort each ticket into one band: - Answer now: a customer is blocked, and we already have the fact we need. - Needs a fact: name the single fact missing before anyone should reply. - Can wait: no one is blocked today. Say why. For each ticket add one next action a person can do in a few minutes. Do not draft the customer reply. Do not promise refunds, credits, or ship dates. If two tickets look like the same incident, group them and say so.
Urgency in the subject line is not urgency. You still read the ticket you are about to answer.
Sample case written by Hidden Logic Lab. Not affiliated with ChatGPT.
More in Support
Get new cases in your inbox
Weekly notes on new use cases and agent workflows. No product pitches.