wowprompt

Ticket tagging and triage rules for a support queue

A tagging taxonomy, priority matrix, and routing rules built from a sample of real tickets. Use it when your queue is messy, tags are inconsistent, or urgent tickets wait behind simple ones.

A support triage guide with a tag list, a priority matrix by impact and urgency, and routing rules for each team.
The output this prompt produced, unedited.

The prompt

Goal

Design a simple, consistent way to tag, prioritise, and route support tickets so the right team handles each one within target response times.

Inputs

  • Sample tickets: [paste 20 to 50 ticket subjects or first lines, with personal details removed]
  • Teams that handle tickets: [for example billing, technical, logistics, account]
  • Current response time targets: [targets by priority, or "none yet"]
  • Business hours and time zones: [details]
  • Tools: [helpdesk name and whether it supports automation rules]

Output format

  1. Tag taxonomy: no more than 15 tags, in a table with Tag, Definition, Example ticket from the sample
  2. Priority matrix:

| Impact \ Urgency | High | Medium | Low |

Each cell shows P1 to P4 with a target first-response time.

  1. Routing rules: "If tag is X and keyword includes Y, assign to team Z at priority P"
  2. Edge cases: five ambiguous sample tickets with the correct tag and a reason
  3. Weekly review routine in 4 steps for keeping tags clean

Check before answering

  • Every sample ticket fits at least one tag; list any that do not and propose a fix.
  • Tags do not overlap: two agents tagging the same ticket choose the same tag.
  • Security issues, payment failures, and legal threats always route to P1 or P2.
  • Rules use keywords and fields the listed helpdesk can read, without needing manual review.
ticket triagesupport ticket taggingpriority matrixhelpdesk routingsupport slaqueue management

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity