That's an excellent idea! Call it "drive-by bug report"? Or "casual bug report"? I am now thinking how to combine the two channels - one is the regular support

That's an excellent idea! Call it "drive-by bug report"? Or "casual bug report"? I am now thinking how to combine the two channels - one is the regular support channel where everything gets tracked and answered (we put a lot of work into it), and one is for drive-by reports (so we just collect them and make statistical inference but don't work hard on each incident). Most of my users are logged in so I know who they are. How about this: 1. Is something broken on this page? [button] 2. [button clicked] We've made a note of your report! We analyze all such reports periodically. Would you like to expedite this particular issue? [yes/no button] 3a. Form abandoned, no further UI action. 3b. [No] Ok, we will treat this as a low-priority issue. If you have any details to share please put them here (optional field). 3c. [Yes] Ok, we will treat this as a high priority issue. Once you fill out this form someone will get in touch with you asap. (What were you trying to do) (What was the desire outcome) (Is it something that used to work but no longer does) (...). So 1-2-(3a|3b) is the casual path, and 1-2-3c is the firm path... Suggestions?