--- name: bulk-ticket-operations description: Enable mass actions on multiple tickets simultaneously for efficiency during outages or widespread issues including bulk close, update, tag, merge, reassign, and templated customer notifications. Use when managing outage response, handling product incidents, performing maintenance on ticket queues, sending mass notifications, or executing scheduled bulk operations. Triggers on phrases like "bulk ticket operations", "mass ticket update", "bulk close", "outage response", "incident ticket management", "mass notification", "bulk assign", "ticket merge". --- # Bulk Ticket Operations Enable mass actions on multiple support tickets simultaneously for efficiency during outages, widespread issues, or queue maintenance — reducing hours of manual work into minutes of controlled, auditable bulk operations. ## Workflow ### 1. Bulk Operation Planning and Execution 1. **Common bulk operation scenarios**: ``` BULK OPERATION SCENARIOS ======================== SCENARIO 1: Product Outage Response Situation: API down affecting 234 customers who submitted tickets Bulk actions needed: • Add tag: ["outage", "API-down", "2026-01-15"] • Add internal note: "API outage — engineering investigating — ETA 2 hours" • Send customer notification: "We're aware of the API issue and working on it" • Pause SLA timer (outage-related tickets exempt) • Assign to: On-call specialist queue (for follow-up when resolved) Impact: 234 tickets updated in <30 seconds Without bulk: ~23 hours of manual work (6 min per ticket) SCENARIO 2: Feature Fix Deployment Situation: Bug fixed and deployed, 89 open tickets related to issue Bulk actions needed: • Send customer notification: "The issue you reported has been resolved" • Add tag: ["fix-deployed", "awaiting-confirmation"] • Resume SLA timer (for customer confirmation) • Auto-close after 48 hours if no customer response Impact: 89 customers notified in <15 seconds SCENARIO 3: Queue Cleanup Situation: End-of-month queue maintenance Bulk actions needed: • Close tickets with no activity for 14+ days (156 tickets) • Send closure email: "We haven't heard back — ticket auto-closed" • Add tag: ["auto-closed", "no-response"] • Archive related internal notes Impact: Queue reduced from 2,340 to 2,184 tickets SCENARIO 4: Team Reassignment Situation: Specialist going on PTO, 45 open tickets need reassignment Bulk actions needed: • Reassign to: Available specialist (balanced distribution) • Add internal note: "Reassigned from [agent] who is on PTO" • Set priority: Normal (not urgent unless SLA at risk) Impact: 45 tickets reassigned in <10 seconds SCENARIO 5: Status Page Incident Merge Situation: Known issue posted on status page, 67 tickets duplicate Bulk actions needed: • Merge into: Master incident ticket • Notify customers: "Your ticket is linked to our status page update" • Mark as: "Duplicative — tracking in master ticket TKT-99234" Impact: 67 tickets consolidated, single point of tracking ``` 2. **Bulk operation execution workflow**: - Define selection criteria (search query to identify affected tickets) - Preview affected tickets (count, sample, risk assessment) - Configure bulk action (what to do, message template, conditions) - Dry run: Test on 5 sample tickets before full execution - Execute: Process all tickets with progress indicator - Verify: Post-execution report showing success/failure counts - Rollback: Undo capability within 24 hours ### 2. Templated Customer Communication 1. **Bulk notification templates**: - Outage acknowledgment: "We're aware of the issue affecting [feature] and our team is investigating" - Fix deployed: "The issue you reported has been resolved. Please test and let us know" - Auto-closure: "We haven't heard back in 14 days — your ticket is being closed" - Maintenance window: "Scheduled maintenance on [date] may affect [feature]" - Policy change: "Update to our [policy] effective [date]" 2. **Personalization within bulk**: - Customer name: {{customer_name}} - Original issue reference: {{ticket_subject}} - Ticket number: {{ticket_id}} - Agent name: {{agent_name}} - Company name: {{company_name}} - Personalized follow-up: "As mentioned in your ticket about {{original_issue}}..." ### 3. Safety Controls and Audit Trail 1. **Safety mechanisms**: - Confirmation required: "This will affect 234 tickets — confirm?" - Irreversible action warning: "Bulk close cannot be undone for closed tickets" - Rate limiting: Max 500 tickets per operation (prevents system overload) - Scheduled execution: Option to run during off-hours - Approval workflow: High-impact operations require manager approval 2. **Audit trail**: - Who: Agent who initiated bulk operation - What: Specific actions taken (fields changed, messages sent) - When: Timestamp of execution - Which tickets: Complete list of affected ticket IDs - Why: Required reason field documenting business justification ## Templates & Frameworks ### Bulk Operations Dashboard ``` BULK OPERATIONS DASHBOARD — January 2026 ========================================== RECENT BULK OPERATIONS (Last 30 Days): Total operations executed: 23 Total tickets affected: 2,890 Average tickets per operation: 126 Average execution time: 12 seconds Success rate: 99.7% (3 tickets failed across all operations) OPERATION DETAIL: Date/Time | Operation | Tickets | Success | Failed | Agent | Reason -------------|----------------|---------|---------|--------|------------|--------------------------- Jan 15 14:30 | Outage response| 234 | 234 | 0 | Sarah M. | API outage — customer notification Jan 14 10:15 | Fix deployed | 89 | 89 | 0 | Tom R. | Bug fix deployed — resolution notification Jan 12 09:00 | Queue cleanup | 156 | 156 | 0 | Lisa K. | End-of-week auto-closure (14+ days no response) Jan 10 16:45 | Team reassign | 45 | 45 | 0 | Alex P. | David K. on PTO — ticket redistribution Jan 8 11:20 | Incident merge | 67 | 67 | 0 | Maria L. | Status page incident — duplicate consolidation Jan 5 14:00 | Outage response| 312 | 312 | 0 | Sarah M. | Database connectivity issue — customer notification ... (17 more operations) EFFICIENCY IMPACT: Estimated manual hours saved: 187 hours this month Calculation: 2,890 tickets × avg 3.9 min saved per ticket Cost savings (at $25/hr loaded): $4,675/month = $56,100/year Without bulk operations: 2,890 tickets × 3.9 min = 187 hours of manual work With bulk operations: 23 operations × 30 sec = 11.5 minutes of actual work Efficiency gain: 99.4% OPERATION BREAKDOWN BY TYPE: Operation Type | Count | Tickets Affected | Avg Time | Success Rate ----------------------------|-------|-----------------|----------|------------- Customer notification | 8 | 1,240 | 18 sec | 100% Tag/label update | 5 | 890 | 12 sec | 100% Auto-closure | 3 | 420 | 25 sec | 99.5% Reassignment | 3 | 156 | 10 sec | 100% Merge/consolidate | 2 | 134 | 35 sec | 100% Status update | 1 | 50 | 8 sec | 100% CUSTOMER COMMUNICATION IMPACT: Bulk notifications sent: 1,660 Customer replies to bulk notifications: 234 (14.1%) Ticket reopens from bulk auto-closure: 18 (1.2%) Customer complaints about bulk communications: 2 (0.12%) ✓ CSAT impact: No measurable negative impact from bulk communications ERROR ANALYSIS: Failed tickets: 3 (0.1% failure rate) Failure reasons: Ticket already closed (different process): 2 Permission denied (restricted ticket): 1 Auto-retry successful: 0 (manual correction needed) SYSTEM HEALTH: Processing capacity: 500 tickets/operation (current max) Average processing speed: 5,200 tickets/second System load during bulk operations: Minimal (<2% CPU increase) ``` ### Bulk Operation Template ``` BULK OPERATION TEMPLATE — Outage Response ============================================ OPERATION NAME: API Outage — January 15, 2026 OPERATED BY: Sarah Mitchell (L2 Support Lead) DATE/TIME: January 15, 2026 — 14:30 UTC APPROVAL: Auto-approved (standard outage response) SELECTION CRITERIA: Ticket status: Open Tags contain: ["API", "error", "timeout", "500-error"] Created after: January 15, 2026 — 12:00 UTC Result: 234 tickets matched ACTIONS CONFIGURED: 1. Add tags: ["outage", "API-down-2026-01-15"] 2. Add internal note: "API outage detected 14:15 UTC. Engineering investigating. ETA resolution: 16:00 UTC. SLA paused for all affected tickets." 3. Send customer notification (template: Outage Acknowledgment): "Hi {{customer_name}}, We're currently experiencing an API outage affecting multiple endpoints. Our engineering team is actively investigating and expects resolution by 16:00 UTC today. Your ticket ({{ticket_id}}) has been flagged for priority follow-up once the issue is resolved. You can track real-time status here: [status page link] We apologize for the disruption and appreciate your patience. Best regards, {{agent_name}} Support Team" 4. Pause SLA timer (resume after outage resolved) 5. Assign to: On-call specialist queue (for follow-up) DRY RUN RESULTS (5 sample tickets): TKT-99201: ✅ All actions applied successfully TKT-99208: ✅ All actions applied successfully TKT-99212: ✅ All actions applied successfully TKT-99219: ✅ All actions applied successfully TKT-99223: ✅ All actions applied successfully EXECUTION RESULTS (Full operation): Total tickets processed: 234 Success: 234 (100%) Failed: 0 Execution time: 23 seconds Notifications sent: 234 (all delivered) SLA timers paused: 234 POST-OPERATION: Customer replies received (within 1 hour): 34 (14.5%) Customer re-opens: 0 Negative feedback: 0 Status page views (from notification link): 890 FOLLOW-UP ACTIONS: ⏳ When API restored → Bulk "Fix Deployed" notification ⏳ Resume SLA timers on all 234 tickets ⏳ Monitor for 24 hours for recurrence ⏳ Remove outage tags after 7 days ``` ## Integration Points - **Help desk** (Zendesk, Intercom, Freshdesk): Ticket selection, bulk updates, notification sending - **Status page** (Statuspage.io, Atlassian Status): Incident correlation, customer redirect - **Communication** (Slack, email): Bulk notifications, team alerts, operation confirmations - **Automation** (Zapier, Make): Scheduled bulk operations, triggered bulk actions - **Analytics** (Tableau, Power BI): Bulk operation metrics, efficiency tracking - **Audit systems**: Complete audit trail for compliance and review ## Edge Cases - **Bulk operation affects too many tickets**: Search criteria too broad — matches 5,000 tickets instead of intended 500: - Safety limit: Hard cap of 500 tickets per operation (requires splitting) - Preview: Always show matching count before execution - Confirmation: "This will affect 500 tickets — confirm?" for high counts - Manager approval: Operations affecting 200+ tickets require approval - Rollback: 24-hour undo window for all bulk operations - **Customer response to bulk notification creates chaos**: 200 customers reply to "fix deployed" notification, overwhelming team: - Expectation setting: "No need to reply unless you're still experiencing issues" - Auto-handling: Replies routed to dedicated "post-fix" queue (not general) - Auto-close: If reply is just "thanks/working", auto-close and reply acknowledgment - Monitoring: Ticket volume spike detection post-bulk notification - Agent guidance: Bulk response templates for post-fix communications - **Bulk auto-closure reopens tickets**: 18 customers had active issues but tickets auto-closed after 14 days: - Softer closure: "Closing this ticket — please reply if you still need help" - Auto-reopen: Customer reply within 7 days of closure auto-reopens - Follow-up email: "Is your issue resolved?" before auto-closure - Exception: High-priority tickets exempt from auto-closure - Monitoring: Track reopen rate to adjust auto-closure threshold - **Bulk operation during peak hours causes system slowdown**: Processing 500 tickets spikes CPU and slows help desk: - Rate limiting: Process 100 tickets at a time with 5-second intervals - Off-hours scheduling: Bulk operations scheduled for low-traffic periods - Async processing: Operation runs in background, agent continues working - Progress indicator: Real-time progress visible to agent - Fallback: System throttles bulk operations if load >80% - **Bulk notification contains incorrect information**: Wrong outage ETA sent to 234 customers: - Quick correction: Follow-up bulk notification with correction - Template review: Pre-approval for high-impact templates - Version control: Track changes to bulk templates - Communication: "Correction: Previous update stated [wrong info]. Correct info: [right info]" - Audit: Log incorrect notification as incident for process review ## Output ### Monthly Bulk Operations Report ``` BULK OPERATIONS MONTHLY REPORT — January 2026 =============================================== VOLUME: Operations executed: 23 Tickets affected: 2,890 Average per operation: 126 tickets EFFICIENCY: Manual hours saved: 187 hours/month Cost savings: $4,675/month = $56,100/year Efficiency gain: 99.4% (vs manual processing) OPERATION TYPES: Customer notifications: 8 (34.8% of operations) Tag updates: 5 (21.7%) Auto-closures: 3 (13.0%) Reassignments: 3 (13.0%) Merges: 2 (8.7%) Status updates: 1 (4.3%) Other: 1 (4.3%) RELIABILITY: Success rate: 99.7% (3 tickets failed across 23 operations) Average execution time: 12 seconds Zero system disruptions from bulk operations ✓ RECOMMENDATIONS: 1. Increase daily bulk operation limit (current: 10, requested: 15) 2. Add "bulk tag removal" operation (currently manual) 3. Create "scheduled bulk operation" feature (recurring cleanup) 4. Implement bulk operation template library (save common operations) 5. Add bulk operation analytics to team dashboard ```