A PRACTICAL NOTE · Daily workflows

How to apply this guide

Capture what happened, what you expected and how to reproduce the issue without sharing private data.

Start with

Say the device, app version and feature first. For example: “On the iPad, the button stayed disabled after I selected a language.” State what you tried before the issue.

Check before you finish

Review the text before sharing it through the product support path. Keep questions, observations and suggested fixes separate. A reproducible short report is easier to verify than a long speculative one.

Evidence to keep: Keep the target field open and verify that the complete reviewed result reached the intended destination. This page’s key limit is: Capture what happened, what you expected and how to reproduce the issue without sharing private data.

Start here

Useful feedback describes a reproducible difference between expected and actual behavior. Voice capture helps you describe it while the details are fresh.

Start with the environment

Say the device, app version and feature first. For example: “On the iPad, the button stayed disabled after I selected a language.” State what you tried before the issue.

Use one example

List two or three reproduction steps and the visible outcome. Substitute a synthetic name, message or recording. Check your words and attach screenshots only when they do not expose personal information.

Give expected and actual results

Review the text before sharing it through the product support path. Keep questions, observations and suggested fixes separate. A reproducible short report is easier to verify than a long speculative one.

Keep exploring