Junk Automated Tickets

Pattern Description

This pattern covers tickets that enter Zendesk but contain no real technical support issue for the wiki. They are usually spam, bot/native-messaging transcripts, internal tests, survey or status replies, logistics-only notes, or sales/HR/admin requests misrouted into support.

Evidence

• Junk, test, or duplicate-admin records: #1 is a sample/junk ticket, #40234 is an internal test ticket, and #41879 is a hiring inquiry closed as non-support.
• Automated or bot-created conversations: #42231 is a bot/native-messaging quote request with no staffed troubleshooting, #42191 is a survey-thread reply turned records lookup, and #22231 was classified into this same junk pattern set.
• Internal logistics or operational-only threads: #2257 is an RMA receiving log, #33391 is only a status inquiry, and #29933 was redirected because it was a sales or routing question.
• Broad recurrence: this rebuilt set contains 493 tickets consistently marked as junk, non-issue, redirect-only, merge-only, or not useful for issue-page evidence.

Impact

• These tickets distort issue frequency if mixed into technical evidence.
• They consume triage time without producing reusable troubleshooting knowledge.
• They also inflate support volume with sales, HR, survey, bot, and admin traffic.

Recommendations

• Auto-tag junk, automation, survey-reply, internal-test, sales, and admin-logistics using subject and channel patterns.
• Exclude these tickets from issue-page evidence and technical trend counts by default.
• Route non-support conversations to sales, HR, or operations earlier when possible.
• Keep a lightweight pattern label so future ingest runs can classify them consistently.

Referenced by

No incoming references yet.