The everyday problem
A useful support report explains what action produced the problem and what result was expected. A screenshot alone may show the symptom without identifying the company, workflow or sequence needed to investigate it.
A workable process
Write down the screen name, time, last few actions and relevant document reference. Include the exact message if one appeared. State whether the issue happens every time or only in one example. Use redacted screenshots when customer or business details are not needed.
A practical example
Instead of saying printing is broken, explain that a saved bill opens in preview but the selected receipt printer produces no output, while another approved test prints correctly. This gives support a narrower starting point without guessing the cause.
Before you finish
Avoid repeatedly changing settings while gathering evidence. Keep track of attempted fixes and their results, and share sensitive data only through the support channel agreed by the business.
Try this check with your team
Describe the smallest repeatable sequence that produces the issue, including company context, screen, selected option and a sanitised document reference. State what happened and what should have happened. Include the exact error wording if one appeared.
What the result tells you
This helps support distinguish a data-specific issue from a device or configuration problem. Share approved sample data where possible and avoid putting passwords or unrelated customer records into a screenshot or support message.
See this workflow in Speed Plus.
Bring a sample transaction and your questions to a product demo.
Book a free demo ↗