A PRACTICAL NOTE · Email workflows

How to apply this guide

Ask for the device, app version and a harmless reproduction without requesting private recordings.

Start with

Request the platform, app edition, build, and one harmless sample phrase. Ask what happened when the customer started, stopped and tried to paste. Ask whether the transcript appeared before sending questions about the microphone.

Check before you finish

Make sure the draft asks one question per step and does not promise a fix before the issue is reproduced. Paste it into an unsent reply and verify the recipient.

Evidence to keep: Before sending, verify the recipient, requested action, dates and sign-off in the finished draft. This page’s key limit is: Ask for the device, app version and a harmless reproduction without requesting private recordings.

Start here

Support triage needs observable steps, not a dump of the customer’s data. A spoken reply can be quick if you name the exact information that would distinguish the issue.

Ask for a small safe sample

Request the platform, app edition, build, and one harmless sample phrase. Ask what happened when the customer started, stopped and tried to paste. Ask whether the transcript appeared before sending questions about the microphone.

Avoid collecting unnecessary material

Do not request passwords, account tokens or a private original audio file when a test with synthetic wording will do. If a screenshot is needed, tell the customer what to leave out.

Check the finished response

Make sure the draft asks one question per step and does not promise a fix before the issue is reproduced. Paste it into an unsent reply and verify the recipient.

Keep exploring