Bug report triage from customer messages

Turn vague customer descriptions into a structured bug report with severity, reproduction steps, likely area and missing information.

LLazyPrompt(@lazyprompt)Customer SupportAnalyzeWorks with any model
No ratings yetSign in to rate
Save 0 Fork Report
Prompt template
Act as a QA-minded support engineer. Convert the customer text below into a structured bug report for the engineering team.

Product: {{product}}
Customer text:
{{customer_text}}

Known context (version, plan, platform, recent releases): {{context}}

Produce:
1. **Title**: specific, under 80 characters, symptom-first.
2. **Summary**: 2 sentences.
3. **Steps to reproduce**: numbered; mark any step inferred rather than stated as "(inferred)".
4. **Expected vs actual behaviour.**
5. **Environment**: only what is stated or in the context.
6. **Severity**: Critical / High / Medium / Low with a one-sentence rationale using this scale: {{severity_scale}}.
7. **Likely duplicate or related area**: only if the text strongly suggests one.
8. **Missing information**: the 3-5 most useful questions to ask the customer, in a friendly message I can send, written so a non-technical person can answer.
9. **Is it a bug?** Say whether this might be expected behaviour, user error or a feature request, and why.

Never invent steps, versions or error messages. Facts only, with guesses clearly labelled.
Example output
**Title:** iOS app crashes when attaching a photo to a task **Summary:** A Team-plan customer reports the app closes whenever they attach a photo to a task. Reportedly worked last week, before the v4.2 release. **Steps to reproduce** 1. Open a task in the iOS app (inferred). 2. Tap attach and choose a photo (inferred). 3. App closes. **Expected vs actual:** Photo attaches; app terminates instead. **Environment:** iOS app, Team plan, version not confirmed (v4.2 released 5 days ago). **Severity:** High. A core workflow for field teams is unusable and no workaround was mentioned. **Related area:** Possible regression in v4.2 attachments or photo permissions (unconfirmed). **Questions to send** "Thanks for the details! Could you tell us your iPhone model and iOS version, whether it crashes with photos from the camera or from your library, and whether it happens with every photo?" **Is it a bug?** Likely yes, a crash is never expected behaviour.

Why it works

Labelling inferred steps keeps engineers from trusting guesses, and the ready-to-send question message saves a round trip. Include your severity scale so the rating matches how your team actually prioritises.

Licensed CC0 (public domain) Version 1 · history