Clear feedback helps the team confirm impact, reproduce a problem, and set priority. Submit it through the in-product Feedback page instead of leaving only “it does not work” in a comment.
Choose the right type
- Issue report: something expected to work fails, stalls, or produces an incorrect result.
- Feature request: a proposed capability or workflow improvement.
- Security or privacy issue: a possible account, payment, sensitive-data, or suspicious-app risk.
- Billing and entitlement issue: payment, plan, allowance, or benefit status does not match.
- Content report: a community post, comment, or micro app may violate the rules.
For urgent account or payment risk, use the appropriate security channel first and do not post details publicly.
What an issue report should include
Use this structure:
- One-sentence summary: what happened and what it affects.
- Environment: web or desktop, version, operating system, and browser.
- Steps: clicks and inputs starting from a stable point.
- Actual result: the message, error text, or unexpected behavior.
- Expected result: what should have happened.
- Impact: whether it happens every time and whether it blocks progress.
- Attachments: only necessary screenshots, recordings, or sanitized logs.
Example summary:
The Windows desktop app still shows signed out after browser authentication; it reproduces after restart.
What a feature request should include
Describe the real situation, not only a button name:
- who has the problem;
- how it is handled today and where the cost occurs;
- the result you want;
- which behaviors are essential and which are preferences;
- any safety, privacy, or compatibility constraints.
Protect sensitive information
Remove before submitting:
- passwords, verification codes, recovery tokens, and access tokens;
- full payment-card and identity-document numbers;
- private file content, messages, and contact details;
- unrelated browser tabs, notifications, or desktop content.
If an error contains a long string, check whether it might be a credential. If unsure, replace it with a placeholder and state that it was redacted.
After submission
A report may move through received, needs information, in progress, resolved, or not planned states. The status and replies on the feedback page are authoritative.
When more information is requested, continue in the original record instead of opening duplicates. If the issue disappears, add the last occurrence and any change that may have affected it.
Content reports and appeals
Identify the content, the specific rule, and necessary evidence. Do not organize duplicate reports. If you disagree with an outcome, explain the facts and reasoning in the same record without publishing private or review information.