Troubleshoot a Client Technical Error
Receive a description of a technical error from a client and need to diagnose the likely cause and next steps.
Prompts for your job
Receive a description of a technical error from a client and need to diagnose the likely cause and next steps.
Use this when a CSS style is not applying to an element and you want ranked possible causes with concrete fixes.
Need to diagnose why a partner's deal registration failed, stalled, or was rejected and decide the next steps.
Use this when a client says their payment did not go through and describes what happened.
Use this when a reaction did not work as expected and you need ranked possible causes and practical fixes.
Get a guest description or photo of a leak, noise, or broken item and need likely causes.
Are on site, a vendor is running late, and you need fast options to adjust the run of show or layout.
Need to diagnose a user-reported software problem from a description or screenshot.
Have an appraisal below the purchase price and need clear, ranked options for your client.
Have a production delay symptom and want a ranked list of possible causes plus quick checks to confirm them.
Use this when an employee's benefit claim has been rejected and you need to identify the likely cause and the correct next step.
Are on set or in prep and a scene is not landing, and you need ranked, shootable fixes fast.
Are on set, something has broken or fallen through, and you need ranked fixes fast.
Have a slow dashboard and want likely causes and optimization steps.
Use this when a loan file has gone quiet or been suspended and you need to reason through the likely cause and the next move.
Need to diagnose why an employee's leave request is stuck, denied, or not processing correctly in your HR system.
Know what a breaker does but not yet why it trips.
Can describe a hum, buzz, crackle, or no-sound problem in your rig and want a ranked list of likely causes with safe tests.
Hear hum, echo, clipping, or dropout and can describe the gear and room.
Have soft footage and can describe camera settings, lens, and shooting conditions.
Use this when a parent describes nipple pain, clicking, or poor milk transfer and you need a ranked list of possible causes and next steps.
Use this when an affiliate reports a link that is broken, misdirecting, or not tracking and you need a structured diagnosis.
Can describe a broken interaction in your game and need likely causes plus next steps to share with art and code.
Use this when campaign data looks wrong and you need to debug UTMs, tags, or platform discrepancies.