Escalation Checklist Overlay

WHAT IT DOES

Provides a structured escalation checklist for managing support tickets and customer issues through the escalation process. The script displays a comprehensive checklist with built-in steps including Issue Categorization, Severity Assessment, Technical Analysis, SME Consultation, Management Notification, Customer Communication, Resolution Plan Created, and Resolution Executed. Each step can be marked complete, and the system tracks when each step was completed with timestamps. You can add notes to any step, add custom steps, and track overall progress with a percentage indicator and visual progress bar. The checklist is saved per ticket, ensuring continuity across sessions.

WHERE IT RUNS

Works on all websites (match pattern *://*/*), making it perfect for support portals, ticketing systems, customer service platforms, or any web-based incident management workflow. Each ticket gets its own independent checklist, allowing you to manage multiple escalations simultaneously. The checklist state is saved per ticket identifier, ensuring continuity across sessions and page reloads.

HOW TO USE

Install the script and the escalation checklist appears in the panel. Enter a ticket identifier to associate the checklist with a specific ticket. Work through the escalation steps in order, checking items off as you complete them. Add notes to any step to capture important details. Click "Add Step" to add custom steps for your specific escalation process. The progress bar updates in real-time showing completion percentage. View timestamps to see when each step was completed. Use the actions buttons to reset the checklist, complete all steps, or clear completed steps. The script saves your progress automatically as you work.

REAL MECHANISM: TICKET-KEYED PERSISTENCE WITH TIMESTAMP LOGGING AND CELEBRATION ENGINE

This script uses a ticket-based storage architecture where each ticket gets its own isolated checklist state. The getTicketId() function retrieves the current ticket identifier from GM_setValue or generates a new one. Data is stored using GM_setValue with a key format of "escalation_checklist_" plus the ticket ID, ensuring data isolation between tickets. The data structure includes a steps array where each step has an id, text, completed boolean, completedAt timestamp, and notes string. When a checkbox is toggled, the completedAt property is set to Date.now() if checked or null if unchecked, providing precise audit logging. The renderChecklist() function calculates progress using filter() and length, then renders each step as a flex row with a checkbox, text container, optional timestamp display, and delete button. Timestamps are formatted using toLocaleString() for human-readable display. Notes fields are rendered as input elements that persist notes on blur events. The celebration engine triggers when all steps are completed and celebrationEnabled is true, creating 20 animated emoji elements with randomized positions, font sizes (16-36px), and animation durations (2-5 seconds) using CSS keyframes, with automatic cleanup after 4 seconds. All operations are reactive, with automatic persistence and UI updates through saveEscalationData() and re-render.

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 which provides the BGPanel framework and storage APIs. All data (steps, notes, timestamps, and ticket identifiers) is stored locally in your browser using GM_setValue and never sent anywhere. No analytics, no tracking, no external calls. The script only reads the current domain and ticket identifier to isolate checklists and never accesses user data, passwords, or sensitive information. Checklists are saved per ticket identifier, so ensure you enter a unique identifier for each escalation you manage.