Known Error Database Entry

Document a known issue with workaround for the knowledge base

🧪 Tested by a human Beginner 👤 It Admin 👤 Support
Create a known error database entry for [ISSUE]. Include: (1) Error title and ID, (2) Symptoms the user sees, (3) Affected systems and versions, (4) Root cause explanation, (5) Workaround steps, (6) Permanent fix status and ETA, (7) Related incidents. Format for searchability in a knowledge base.

Works on

⭐ M365 Copilot (Best) 🟢 ChatGPT

Copy & Open in

🟢 ChatGPT

Prompt is copied to your clipboard when you click

Tips for Best Results

  • Use the exact error message as a searchable keyword
  • Update the entry when a permanent fix is released
  • Link related incidents so patterns are visible

📎 More Prompts

Blameless Post-Incident Report

●●●
Write a blameless post-incident report for [INCIDENT]. Include: (1) Executive summary (2 sentences), (2) Timeline of events with timestamps, (3) Impact assessment (users, revenue, SLA), (4) Root cause analysis, (5) What went well in the response, (6) What could be improved, (7) Action items with owners and deadlines. Tone: factual, constructive, forward-looking.
⚡ M365 🟢 GPT ⭐ Claude

Diagnostic Decision Tree

●●
Create a diagnostic decision tree for [ISSUE TYPE — network connectivity / application crash / login failure / slow performance / email delivery]. Structure as: If symptom A → check B → if yes → do C, if no → check D. Include: expected outcomes at each step, escalation triggers, and resolution confirmations. Write for a Level 1 support technician.
⚡ M365 ⭐ GPT 🟠 Claude

Email Delivery Troubleshooting

●●
Help me diagnose email delivery failure. Scenario: [DESCRIBE — emails not received / going to spam / bouncing / delayed]. Check: (1) Message trace in Exchange Admin, (2) SPF/DKIM/DMARC alignment, (3) Transport rules that might redirect, (4) Recipient mailbox issues, (5) IP reputation, (6) Content filtering triggers. Provide step-by-step diagnosis with Exchange admin paths.
⚡ M365 ⭐ GPT
💬