Write a support request someone can investigate.

1. Describe one problem and its impact

Start with a plain sentence: “The export button becomes unavailable after I choose a file.” Then say what you expected instead and why the problem matters. Distinguish a feature question from a broken feature, billing question, or account-access problem so the request reaches the appropriate route.

Use observations rather than a diagnosis you cannot establish. “The page stayed blank” is more useful than “your database is corrupted.” Note when the problem first appeared and whether it happens every time. If you only observed it once, say so rather than promising that someone else can reproduce it.

2. Record the smallest useful sequence

List the starting page or application screen and the actions immediately before the failure. Use a harmless sample where possible. If reproducing the issue could create an order, publish content, or lose work, describe what already happened instead of repeating that action just to gather evidence.

For a browser problem, identify whether it affects one page or several. Do not assume that a second symptom has the same cause.

3. Collect technical details selectively

Firefox provides a Troubleshooting Information page containing installation details and diagnostic information. Mozilla documents both a text report and raw-data copy option. The page includes information such as the Firefox version, extensions, and modified preferences that may help investigate a specific issue.

Use the support team’s requested format and review what you plan to share. Mozilla says the copied report omits the profile-folder line for privacy; that does not mean every other diagnostic field is appropriate for a public forum. A concise version number may be enough for an initial question.

Sources: [1]

4. Check the destination and the attachment

Use the help route linked by the actual service. Mozilla explicitly says it does not provide telephone support and warns about people charging for supposed Mozilla assistance. Other companies have different support models, so verify their own documentation rather than applying Mozilla’s policy to everyone.

Inspect screenshots for names, messages, open tabs, email addresses, account balances, or private filenames unrelated to the problem. Create a separate redacted copy and reopen it to check the result. Never include a password, recovery code, or payment-card security code in a support request.

Sources: [2]

5. Keep the case and outcome together

Save the request, submission date, official destination, and any case number. Add replies and test results to that record rather than opening several indistinguishable tickets. If the responder proposes a change, first understand what it affects and preserve work that could be lost.

When the issue is resolved, note the application version, the relevant change, and the task that now works. If it remains unresolved, record the next question instead of marking the case complete. This leaves a useful history for your future self without turning an untested explanation into a confirmed cause.