This would definitely require client-side UI changes. We should still be able to get the users current URL from the feedback report if they choose to share that, which we could use to determine the suggestions that were served.

Agree that we should prioritize this to gain better confidence with our suggestions. 

I believe EoC on iGSA has a "Send feedback" link in the CAS. Can we use that as the entry point to get users to in-product feedback?

Yes, we could add some UI element to launch in-product feedback directly. This would have to be client-side, though, unless we deliver the link as a fake card.

(not entirely sure a fake card would work, we'd have to try it out)

A fake card seems like it would be somewhat confusing from a user standpoint, right (since it would look like a suggestion)? My preference would be updating the client UI if at all possible.

Should we kick this over to Chris to design the UX?

Eng timeline for client-side depends on the UX design, but I'd expect this to be a "medium" task.

My 2-cents is that we can get good information from the existing Help & Feedback item in the app menu and that this doesn't seem critical for M67, but happy to let PMs/TPMs work out priority and request merges/grant approvals.

Or, if this is critical, is there a backup designer while Chris is OOO (he's out through April 25)?

How critical are we thinking here? I can take a pass at this and could have an update soon. 

I think this is fixed. We're doing a footer link for M67 and moving the link to the overflow menu for M68+.