Tickets
AuraScore 81/100

Enterprise Diagnostic Walkthrough and Bug Reproducibility Script

Author a structured technical support call script to guide enterprise customers through complex diagnostic logging and bug reproduction.

Use this template when a complex, intermittent software defect requires Tier-3 support to conduct a live interactive session with an enterprise user. It ensures precise log gathering, permission compliance, and smooth technical handoffs.

Template

Role: Principal Technical Support Engineer specializing in deep diagnostics, developer tooling, and enterprise software triage.

Context

  • Failing module: {{product_module}}
  • Operating environment: {{client_operating_env}}
  • Observed issue: {{reported_symptom}}
  • Diagnostics utility: {{telemetry_tool}}
  • Known occurrence rate: {{reproducibility_rate}}
  • Customer technical proficiency: {{customer_technical_level}}

Task

Create a step-by-step diagnostic session script for a live remote troubleshooting call, guiding the customer through isolating an elusive bug and collecting telemetry traces for engineering escalation.

Method

  1. Analyze {{reported_symptom}} against {{client_operating_env}} to identify required debugging privileges and diagnostic endpoints.
  2. Calibrate spoken explanations to match {{customer_technical_level}}, avoiding patronizing language while ensuring absolute technical precision.
  3. Compose an introductory security disclaimer confirming screen-recording consent and sensitive data scrubbing protocols.
  4. Write clear verbal instructions directing the customer to initialize {{telemetry_tool}} and isolate {{product_module}}.
  5. Design an active reproduction sequence accounting for {{reproducibility_rate}}, providing pivot steps if the bug fails to trigger on demand.
  6. Script the log capture, verification, and sanitization extraction phase to prevent customer PII from entering support tickets.
  7. Detail closing guidance that manages customer expectations regarding Tier-3 engineering triage timelines.

Constraints

  • MUST explicitly prompt the customer to pause recording or mask fields when entering credentials or proprietary tokens.
  • MUST include exact command-line syntax or UI navigation paths formatted in inline code.
  • MUST NOT promise specific patch release dates or code commits during the call.
  • Spoken lines must include checkpoints confirming customer consent before executing elevated commands.

Output format

1. Pre-Session Readiness Checklist

5-item verification list of required tools, access tokens, and baseline logs.

2. Live Diagnostics Script

Segmented conversational script containing: Security Briefing, Diagnostic Tool Setup ({{telemetry_tool}}), Step-by-Step Repro Workflow ({{product_module}}), and Log Verification.

3. Troubleshooting Pivot Matrix

A table with 3 contingency scenarios (e.g., Bug Not Reproducing, Tool Crashing, Permission Denied) and direct verbal pivot lines.

4. Engineering Handoff Summary Template

A structured ticket template (max 150 words) mapping collected artifacts to developer triage fields.

Self-review

  • Are commands tailored specifically to {{client_operating_env}}?
  • Does the script account for the user's proficiency level in {{customer_technical_level}}?
  • Are data privacy and credential safeguards explicitly highlighted before log extraction?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-tickets
technology-software
tier-3
debugging
troubleshooting