6.5Working with Support

Customer-Reported Bugs and Feedback Loops

The support team is the closest function to the customer. They hear about bugs, usability issues, and missing features before anyone else. A strong QA-support partnership creates a direct feedback loop from production back to the development process.

What QA Gets from Support

From Support	Value to QA
Bug reports from customers	Real-world scenarios that testing may have missed
Frequency data	"50 customers reported this issue" adds urgency to a bug
Reproduction steps from users	Sometimes clearer than QA's own reproduction because users describe what they wanted, not what they clicked
Feature requests with pain points	Informs test design for upcoming features
Environment data	"This happens on Safari on iPad" narrows the reproduction

What Support Gets from QA

From QA	Value to Support
Known issues list	Support can proactively tell customers "we're aware and fixing it"
Workarounds	Documented workarounds that support can share immediately
Release notes	"This bug is fixed in the next release" gives support a timeline
Bug status updates	"BUG-1234 is in progress, ETA Friday" helps support manage customer expectations
Regression confirmation	"The fix has been verified" so support can close tickets

Building the Feedback Loop

1. Create a shared channel (Slack, Teams) where support can flag potential bugs directly to QA
2. Define a lightweight triage process for customer-reported issues: support describes the problem, QA verifies reproducibility, development prioritizes
3. Share the known issues list with support before every release
4. Include customer-reported bugs in sprint metrics to show the team how quality decisions affect real users
5. Invite a support representative to sprint reviews periodically so the team hears the customer voice directly