‘Tell us what you think’ in a footer does nothing if the box is a blank mailto. The form should tag feedback as a request type, names the page or product, and stores the details so product can actually triage.
Digest to the PM, instant to on-call if you add an urgent type.
Those two fields create the queue.
A small ‘feedback’ at article end beats a hidden contact page.
Close the loop when you ship the fix.
A feedback form is how users report friction: a confusing US checkout ZIP field, a UK VAT line, a broken docs page. It is not a testimonial widget and it is not NPS. The request pack gives you a type (general, urgent, follow-up) so a security note is not mixed with a typo.
Research teams will still run interviews. This page is the always-on mailbox that does not depend on a researcher being staffed.
‘It is broken’ without a URL is how tickets bounce.
Say you will not reply to every note. Honesty raises completion more than a fake SLA.
In-app widgets are great. Marketing sites still need a public URL.
Linked from docs and the product footer.
Use in-app. This form catches people who already rage-quit the app.
Not a system of record. Invite them here.
Useful. They miss the Tuesday outage.
Docs are often Hugo or Docusaurus. Place a short form at the bottom of each article and pre-fill page_or_product if you edit per page.
ZIP or postcode rarely belongs here unless the feedback is about delivery. Keep the form short.
Make email optional on the form if you want that. Abuse may rise.
Ask for a link. Native upload is optional later.
No. Use a survey tool for scores; use this for words.
Do not promise one in the auto-reply unless it exists.