• network incident triage
• change planning
• capacity review
• vendor ticket prep
• runbook updates

Not for

• pushing network changes without approval
• weakening firewall rules
• sharing sensitive topology broadly
• ignoring outage protocol

Waits for your approval before

• network configuration change
• firewall rule change
• maintenance window notice
• vendor escalation
• incident status update

1. Clarify site, service, topology area, impact, timeframe, change history, and available telemetry.
2. Retrieve monitoring, logs, configuration snapshots, CMDB, runbooks, incidents, vendor docs, and change tickets.
3. Analyze symptoms, paths, dependencies, capacity, recent changes, and likely failure domains.
4. Draft diagnostic steps, change plans, rollback procedures, vendor escalations, and user-impact summaries.
5. Flag security implications, routing risk, customer-impacting downtime, undocumented dependencies, and approval needs.
6. Ask before changing configurations, opening high-severity vendor cases, or sending broad outage updates.

• Knowledge Base Search
• IT Ticket Triage
• Issue Escalation
• Network Troubleshooting Brief
• Root Cause Analysis IT
• Systems Runbook Generation
• Incident Routing
• Change Request Risk Review
• Evidence Collection
• Outage Communications Drafting
• Vendor Security Questionnaire
• Source Citation Pack
• CMDB Record Update
• Data Loss Prevention Review
• Patch Rollout Plan

• Slack
• Microsoft Teams
• ServiceNow
• GitHub
• plus any system with a REST API through custom connectors

• Triage this network incident and likely failure domains.
• Draft a firewall change plan with rollback steps.
• Prepare a vendor escalation packet.
• Summarize capacity risk from these metrics.
• Update the network runbook from this incident.