Turn a customer complaint into a bug report for engineering

Turn the customer ticket below into a bug report for our engineering team. Engineers will use it to reproduce and fix the problem, often without talking to the customer, so it must contain only observed facts, in steps they can follow.

Customer ticket and replies:
"""
{{ticket}}
"""

What support has checked or tried, including whether we reproduced it:
"""
{{support_notes}}
"""

Account and technical details we have (plan, browser, device, app version, account ID): {{technical_details}}

Our severity levels:
"""
{{severity_levels}}
"""

Use this format, with these exact labels:
Title: under 12 words, in the form "Area: what fails, when", for example "Invoices: PDF export fails for invoices over 100 lines".
Summary: two sentences.
Environment: plan, browser or device, version, and account ID.
Steps to reproduce: numbered, one action each, starting from a named screen.
Expected result:
Actual result: including any error message, copied exactly.
Frequency: every time, sometimes, or once, and whether support reproduced it.
Impact: who is affected, how many customers if known, and whether there is a workaround.
Suggested severity: one level from the list above, with a one-line reason.
Attachments mentioned: screenshots, logs or files the ticket refers to.
Questions for the customer: what we still need to know.

Rules:
- Separate what the customer saw from what they think caused it. Put any theory of theirs in Summary as "Customer believes...".
- Do not invent steps, versions or error text. Write "Not in the ticket" for anything missing.
- Leave out the customer's name, email, phone number and payment details. Keep the account ID only.
- Leave out apologies, frustration and back-and-forth that do not change the facts.
- If the severity levels say "none", leave out Suggested severity.

The report must be clear enough that an engineer can start reproducing the bug from the steps alone. If the ticket describes more than one problem, write a separate report for each. If the steps are too vague to reproduce, say so at the top and make the questions for the customer specific enough to fill the gap.