Written by ND SOFT LLC · Published July 14, 2026 · Updated July 14, 2026
Do not copy the customer message and call it a bug
The first message usually describes impact, not cause. “Export is broken” could mean a browser download block, a report filter, a permissions change, a timeout, malformed data, or a product defect. Support should confirm documented behavior and collect a reproducible boundary before assigning engineering work.
Write one precise issue statement
Use a sentence that names the action, condition, and failure. Example: “CSV exports above 500 rows omit the Notes column while the same report at 499 rows includes it.” This is more useful than “CSV export problem” because it gives engineering a variable to test and preserves the customer impact.
Capture the minimum reproducible sequence
Record the starting state, exact actions, observed result, expected result, environment, approximate time, safe identifiers, and whether the behavior repeats. Do not ask for passwords, private keys, unrestricted tokens, payment-card data, or full customer datasets. Request a redacted request ID or report ID when it is enough to locate server-side evidence.
- Starting state and permissions
- Exact actions in order
- Expected and actual result
- Browser, device, version, or integration context
- Timestamp and safe correlation identifier
- Workaround and business impact
Separate impact from severity
Impact describes what the customer cannot do. Severity is an operating decision based on scope, workaround, data risk, affected accounts, and business consequence. A single blocked customer can be urgent without proving a system-wide outage. The report should explain the severity suggestion and leave the final priority decision with the responsible team.
Keep unknowns visible
A useful report does not fill missing fields with assumptions. Mark the browser version, account state, deployment version, or reproduction status as unknown and assign the next evidence request. This prevents a polished AI summary from turning an inference into a fact.
Keep the support and engineering records connected
The escalation should link back to the originating ticket, while the customer thread receives status updates in plain language. Engineering can request focused evidence through support without creating a second disconnected conversation. When the issue is resolved, the final explanation can become an approved knowledge article or response rule.