Example context. Preview only. Nothing is submitted.
When to sendFrom a page-level ‘Report a problem’ link, while the visitor can still describe what happened.
- 01
Report a problem with this page
The two answers describe one event. Keeping them together makes the report easy to review and avoids a page break for each sentence.
See the questions
- What were you trying to do?
- The intended action gives the report context.
- What went wrong?
- Accept an ordinary description of the failure without requiring technical steps.
Using the answers
Read the task and problem together, then route the report to the page or product owner. Do not infer prevalence from a voluntary problem-reporting form.
When to choose another form
A technical reporter can provide reproduction steps, or someone needs account-specific support.
Before you publish
Keep the page and release context with the response, and connect reports to a triage queue.
Provide a separate support route for personal or account-specific problems.