Turn messy support tickets into reproducible bug reports

Our support inbox produces tickets like "app broke when I hit save" and "it's slow again". Engineering bounces about half of them back asking for steps. What I want out the other end: - Steps to reproduce, numbered - Expected result vs actual result - Severity, with a one-line justification - An explicit "missing information" section rather than guesses What I have tried: asking directly for a bug report. The problem is it invents plausible reproduction steps that the customer never actually mentioned, which is worse than no steps at all because engineers waste time following them. I need something that refuses to fill gaps. Has anyone got a prompt that reliably separates what was stated from what is missing?