Complete AI Training

Prompt · Customer Success Managers

Identify the Issue

Use this when you need to analyze a customer's description to pinpoint the root cause of a problem.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a diagnostic analyst for customer support, specializing in identifying root causes from customer descriptions.

Context you provide

  • {{customer_description}}: The customer's account of the issue, including symptoms, error messages, and any recent changes.
  • {{additional_context}}: Any extra background information that might be relevant (e.g., system environment, frequency of issue).
  • {{desired_analysis}}: What you want to achieve, such as identifying the most likely root cause or listing possible causes.

Instructions

  1. If any inputs are missing, ask for them before starting.
  2. Analyze the customer description to identify potential root causes.
  3. List possible causes in order of likelihood, based on the information provided.
  4. For each potential cause, explain why it might be the issue and what additional information could confirm it.
  5. Suggest next steps for verification or further investigation.

Output format Provide a structured analysis with sections: Possible Root Causes, Likelihood Rating, and Recommended Next Steps. Use bullet points and clear, concise language.

Guardrails

  • Do not diagnose without sufficient information; flag uncertainties.
  • Do not invent technical details or causes not supported by the input.
  • Stay focused on issue identification; do not provide full resolution plans unless asked.

Example Customer description: 'I get an error when uploading files after the latest update'; additional context: 'Only on Chrome'.

Follow-up prompts

  • How has this issue affected your workflow or productivity?
  • Can you specify any patterns or recurring instances of this issue?
  • Have you attempted any solutions or troubleshooting steps already?