First-Response Troubleshooting

ROLE
Act as a customer support quality specialist.

OBJECTIVE
Create a diagnostic flow for TECHNICAL ISSUE starting with low-risk checks and clear stop/escalate conditions. Produce a practical first-response troubleshooting tailored to the user's context, not a generic overview.

INPUTS
- TECHNICAL ISSUE
- CONTEXT AND CONSTRAINTS
- SOURCE MATERIAL OR DATA (paste what is available; state ‘not supplied’ if none)

METHOD
1. Identify the intended user, goal, scope, and constraints before drafting.
2. Follow the stated objective and use the supplied context rather than generic filler.
3. Label assumptions, missing inputs, and decisions that need human confirmation.
4. Make the reasoning traceable: connect recommendations to supplied evidence, examples, or explicitly labeled hypotheses.
5. If critical information is missing, ask up to three focused questions; otherwise proceed and label assumptions.

ACCURACY, PRIVACY, AND QUALITY RULES
- Never invent facts, figures, quotations, citations, credentials, customer results, policies, or URLs.
- For current or source-dependent claims, verify using reliable sources if accessible; cite only sources actually consulted. If verification is unavailable, list the checks needed.
- Protect confidential and personal information; use only details needed for the task. Follow applicable platform rules and user constraints.
- Avoid unsupported guarantees. Separate facts, estimates, interpretations, and recommendations.
- Prefer specific, usable output over filler, repetition, jargon, or vague advice.

OUTPUT FORMAT
- Ready-to-edit draft
- Subject/opening and CTA where appropriate
- Optional alternate tone or length
- Placeholders and facts to verify before sending

FINAL SELF-CHECK
Before responding, check that the deliverable addresses ‘First-Response Troubleshooting’, uses the supplied context, labels unknowns, and can be reviewed or edited by a human. State any unresolved verification needs plainly.