RIP-Fix Framework – ChatGPT Troubleshooting Prompt Engineering for the gentle IT Support Engineer and the Trusty Helpdesk - (By Ivoryfox Creative - Forged in Chaos)

Tutorials & Methods
, , , , ,
1

RIP-Fix Framework – ChatGPT Troubleshooting Prompting Guide

Document Type: Prompt Engineering, Troubleshooting Guide
Owner: Ivoryfox Creative
Last Updated: 8/7/2025
Version: 1.7.0

Purpose

The RIP-Fix Framework is a structured prompting method for IT Support Engineers to use with ChatGPT to produce clear, actionable, and consistent troubleshooting documentation for IT incidents.

This framework ensures:

  • Technical accuracy for internal teams.
  • Simple explanations for end-users.
  • Consistent documentation in CRM, ticketing, and knowledge base systems.

Scope

Applicable to:

  • All IT incidents requiring root cause analysis and resolution documentation.
  • Use in service desk, NOC, and field engineering environments.
  • Compatible with ChatGPT or equivalent AI assistants.

Definitions

RIP-Fix stands for:

  • Root Cause – Why the issue happened.
  • Impact – Who/what is affected.
  • Priority – How urgent/severe the issue is.
  • Fix – Immediate and long-term solutions.

Procedure

1. Gather Incident Information

  • Collect all available details:
    • Error messages
    • Logs and screenshots
    • Timeline of events
    • Systems/users affected
  • Use bullet points for clarity when inputting into ChatGPT.

2. Apply the RIP-Fix Prompt

Using the RIP-Fix Framework, analyze the following IT issue:
[Insert issue description here]

Root Cause

Identify the most likely cause(s), with both:

  • Technical detail
  • Plain-language explanation

Impact

Describe which:

  • Systems are affected
  • Users are affected
  • Business processes are affected
    Include the scale of impact.

Priority

Assign severity:

  • Critical
  • High
  • Medium
  • Low

Justify the rating based on operational and business factors.

Fix

Provide both:

  1. Quick Workarounds – Immediate, temporary solutions.
  2. Best Practice Resolutions – Long-term, permanent fixes.

Include:

  • Step-by-step instructions
  • Verification steps to confirm the fix

THE FOUR PILLARS OF RIP-FIX

R – Root Cause (Isolate, Understand, Resolve)

  • Identify exact technical cause(s).
  • Include plain-English explanation for non-technical audiences.
  • Example:
    • Technical: DHCP service stopped on core switch due to firmware bug.
    • Layman: The system that assigns devices their network address stopped working due to a software glitch.

I – Impact (Understand what is at stake)

  • List affected:
    • Systems
    • Users
    • Business processes
  • Indicate scope (isolated, department-wide, company-wide).
  • Example:
    • Systems: All Windows desktops in HQ.
    • Users: 85 staff unable to log into email.
    • Business Impact: SLA breach risk, delayed client responses.

P – Priority (For CRM/Ticket Notes & KB Data)

  • Assign Critical, High, Medium, or Low.
  • Justify rating based on:
    • SLA
    • Operational impact
    • Security risk
  • Example:
    • Priority: Critical
    • Reason: Company-wide email outage halts sales and support.

Fix – Two Layers

a1. Workarounds – Immediate, low-risk actions to restore service.
Example: Route email through backup mail server until main server is patched.

a2. Best Practice Resolutions – Permanent, tested solutions with verification.
Example: Apply vendor firmware update, restart DHCP service, monitor for 48 hours.

Use Case - Example

Incident: Laptop cannot connect to Wi-Fi after Windows update. Other devices unaffected.

ChatGPT Output (Condensed):

  • Root Cause:

    • Technical: Windows update replaced Wi-Fi driver with incompatible version.
    • Layman: Update changed the Wi-Fi software, which no longer works with this laptop’s hardware.

  • Impact:

    • 1 user affected (Sales department).
    • Business impact: Delays in meetings and CRM updates.

  • Priority: Medium – Single-user, productivity affected.

  • Fix:

    • Workaround: Connect via Ethernet or USB Wi-Fi adapter.
    • Best Practice: Roll back driver, block update, test, and monitor for 48 hours.

**Refinement Commands

After ChatGPT’s initial output, follow up with targeted requests:

  • “Add CLI commands to verify the root cause.”
  • “Include PowerShell examples for the fix.”
  • “Add a simple explanation for end-user communication.”

**Pro Tips

  • Be specific in your incident details — the better the input, the better the output.
  • Always request examples, steps, and explanations (commands, logs, screenshots).
  • Ask for two versions — technical (for IT docs) and plain-language (for client comms).
  • Save best-performing prompts — reuse for similar incidents to speed workflow.

Mark Twain’s productivity advice

“If it’s your job to eat a frog, it’s best to do it first thing in the morning.
And if it’s your job to eat two frogs, it’s best to eat the biggest one first.”

3 Likes