Support Ticket Duplicate Detector Summary

WHAT IT DOES

AI-powered support ticket duplicate detector that identifies potential duplicate tickets by analyzing content and patterns. The script reads a support ticket or issue description from the current page—title, description, category, and user context—and generates a summary that detects potential duplicates by comparing with common patterns or known issues. The AI analyzes the ticket content to identify if it matches or resembles existing known issues, patterns, or common support requests, helping support teams identify duplicates quickly and reduce ticket volume. You can customize the report format (brief/detailed) and toggle inclusion of similarity scoring, known patterns, suggested resolution, and priority flags. The user reviews the output before copying or using it.

WHERE IT RUNS

Works on all support ticket and issue pages (match pattern *://*/*), including help desk platforms, ticketing systems, issue trackers, and any page containing support tickets or issue descriptions.

HOW TO USE

Install the script and navigate to any support ticket or issue page. The Support Ticket Duplicate Detector Summary appears in the panel. Configure your preferred report format and toggle inclusion of similarity scoring, known patterns, suggested resolution, and priority flags using the settings controls. Click "Detect" to analyze the current page. The AI extracts ticket content and generates a duplicate detection summary. Review the output in the panel. Click "Copy to Clipboard" to copy the analysis for reference or sharing. Adjust the settings and regenerate if you want a different level of detail.

REAL MECHANISM: DOM CONTENT EXTRACTION WITH AI DUPLICATE DETECTION AND REVIEW GATE

This script uses a hybrid extraction approach that prioritizes structured content when available. First, it checks for WebMCP (navigator.modelContext), a W3C proposal that exposes structured tools on the page. If available, it calls getContent() to obtain structured ticket data. If WebMCP is not present—the common case today—it falls back to DOM scraping using targeted selectors for ticket sections (ticket-title, ticket-description, issue-title, issue-description, support-ticket, ticket-details, issue-details, case-details, support-request, and ticket-body). It also scans for ticket-related keywords (ticket, issue, problem, error, bug, request, support, help, unable, can't, not working) in paragraphs and headings. The extracted text is sent to an AI backend via GM_xmlhttpRequest, which processes it with a system prompt that includes the user's report format and inclusion preferences. The AI returns a duplicate detection summary (up to 150 words) with potential matches, similarity scoring, and recommendations. The response is displayed in a bordered container for review before copying. Copy-to-clipboard uses GM_setClipboard. All settings (reportFormat, includeSimilarityScoring, includeKnownPatterns, includeSuggestedResolution, includePriorityFlags) are persisted via GM_setValue. The script enforces a review-before-use pattern: the user must read and approve the AI output before copying it.

THE PANEL

Drag the panel anywhere on screen by clicking and holding the header. It snaps to screen edges when released. Collapse it to a small bubble by clicking the minimize button, and expand it back by clicking the bubble. Resize the panel from any corner. Press Escape to close the configuration panel. Your position and size preferences are saved automatically per site.

PLEASE NOTE

This script requires the free BotGentz browser extension and an active AI subscription for the detection service. AI-generated summaries should be reviewed for accuracy before use—the AI may misinterpret ticket content or miss relevant duplicates. The script reads the current page content and sends it to the AI backend for processing; no data is stored or logged. Websites change frequently; if the script stops detecting ticket content, check for updates to the extraction selectors.