Most sites already have a way to report a problem: a contact page, or an email address in the footer. Both technically work. Both lose most of the reports they receive, and they lose the good ones first.
Three ways a contact form leaks reports
- Distance — the reporter has to leave the broken page to find the form, and the context goes with them
- Ambiguity — free text produces "it does not work", with no page, no browser, and no steps
- Ownership — a shared inbox belongs to everyone, which means it belongs to nobody, and engineering does not read it
What changes with a widget
The form is on the page where the problem is, so nothing has to be described from memory. The fields ask for the specific things a triager needs. And the destination is the issue tracker, so a report becomes a work item rather than an email somebody might forward.
Keep the contact form
This is not a replacement for how customers reach you about billing, sales, or anything requiring a human reply. It is a dedicated path for "something on this page is wrong", which is a different message with a different destination.