Send a useful support report

A useful report identifies the same transaction and a reproducible sequence, rather than only saying “slow” or “wrong amount”.

Steps

1. Record version, edition, language, store and online/offline state.
2. Describe the menu, steps, expected outcome and actual message, with time and document number.
3. For amounts include goods, quantities, units, prices, tax and methods; for stock include warehouse and approval state.
4. Capture relevant screen context while hiding credentials, payment secrets and unrelated personal information.
5. State whether all computers are affected, whether it repeats and what has already been tried. Preserve uncertain payments before further action.