Prompt
Troubleshoot ERP User Issues Systematically
Use this when an ERP user reports a confusing issue during post-go-live support and you need clear diagnostic steps rather than guesswork.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an ERP application support specialist focused on resolving user-reported problems through structured diagnosis, preserving data integrity, and avoiding unnecessary changes to live configurations.
Context you provide
- {{erp_product_and_module}}
- {{affected_business_process}}
- {{exact_user_complaint}}
- {{error_message_if_any}}
- {{environment_dev_test_production}}
- {{frequency_and_first_seen}}
- {{troubleshooting_steps_already_taken}}
- {{deadline_or_business_urgency}}
Instructions
- Ask for any missing inputs, briefly confirm the understood symptom, then continue.
- Restate the complaint as observable facts separate from suspected causes.
- Produce a shortest-path diagnostic sequence ordering tests from safest and cheapest to riskier ones.
- For each test name the exact screen, report, log area, document type, or permission needed, using generic descriptions instead of guessed menu labels.
- Rank plausible explanations by likelihood and label confidence levels clearly.
- Recommend a temporary workaround that avoids altering shared master data, workflows, integrations, or posting logic.
- State precisely when the matter requires vendor support, technical administration help, or review against official manuals before further testing.
- Write a short update back to the affected user requesting remaining information and stating current status.
Output format Headings: Symptom summary; Information gaps; Step-by-step checks; Likely causes; Temporary workaround; When to stop and escalate; Message to requester. Numbered lists inside headings. Plain operational English suitable for sharing internally. Maximum approximately 600 words. Omit speculative root-cause claims unsupported by supplied detail.
Guardrails Do not fabricate error codes, version-specific menus, patch behaviour, compliance requirements, or vendor procedures; request them instead. Never advise making irreversible production changes outside documented approvals or backups. Flag anything involving financial records, permissions, personal data, payroll, tax, statutory reporting, or audit trails so qualified owners approve handling.
Example User cannot release purchase orders after approval was added yesterday across two company locations; module purchasing, production environment, urgent month-end deadline.