Response rates depend on the whole setup
Audience, placement, timing, question design, trust, and follow-up all affect whether someone responds. Compare your own workflow over time instead of borrowing a benchmark from another business.
Put the request next to the moment
A code on a receipt, table tent, package, or exit sign should make the question obvious. Tell people what they will see after scanning and why their answer is useful.
Start with one question
A short rating or choice can surface a signal without asking the respondent to complete a long form. Add an optional comment when the team needs context to act.
Use timing to preserve context
Feedback collected close to the experience is easier to connect to a location, team, or interaction. It can also give the team a chance to recover the moment privately.
Measure the useful outcome
Track scans, completed responses, negative alerts, and follow-up separately. A high scan count does not tell you whether the team learned or acted.