Over the years, I've experimented with various methods for gathering website feedback from clients—everything from emails and long word documents to Figma flows with pasted screenshots and even dedicated tools. Unfortunately, none of these approaches ever felt quite right, and my team tends to stop using them after just a week. I'm really interested to hear what others are currently using for this process. Additionally, does anyone find that their internal QA looks different from client feedback reviews?
4 Answers
Have you considered trying Spotfix? It's a widget specifically designed for feedback and bug reporting. Clients can leave their thoughts directly on the website, and it all gets organized into a dedicated board as tasks.
I totally get how frustrating it can be to untangle client feedback, especially when they're sending Loom videos alongside Google Docs. I've switched to using givefeedback.dev recently, and it's been a game changer. It records both screen and audio natively and uses AI to generate a list of actionable next steps. It's made my workflow so much smoother.
Lately, I've been using Loom along with a shared Google Doc, and it's been working quite well for me. It allows for clear communication without too much fuss.
This is definitely a common struggle. Many workflows fail because they make things too complicated for clients. I've found that getting contextual feedback directly on the live site or prototype works better; it's clearer and faster to act on. For internal QA, we focus on structured testing and edge cases, while client feedback is more about design and usability. Keeping those processes separate really helps. Tools like Runable can also be useful as they tie feedback directly to the UI, but the key is making it as easy as possible for clients to share their thoughts.

Related Questions
Keep Your Screen Awake Tool
Favicon Generator
JWT Token Decoder and Viewer
Ethernet Signal Loss Calculator
Glassmorphism CSS Generator with Live Preview
Remove Duplicate Items From List