Feedback form QR codes
Listen while the experience is fresh
Create a short hosted form with ratings, text answers and multiple-choice questions. Guests scan and respond without creating an account.
Make it useful from the first scan.
Ask only what you need. Responses expire after your chosen retention period, from 7 to 365 days. Export answers as CSV before they expire. The organization can see submitted answers; explain that clearly to your audience.
Explain where answers go before asking for them
A feedback QR code opens a hosted form that a guest can answer without creating an account. Start with the decision you hope to make from responses. If you need to understand a service delay, a focused rating and optional comment may be more useful than a long survey covering unrelated topics. Give questions plain labels and make multiple-choice options distinct enough that respondents can find an appropriate answer.
Tell people who receives answers and how long you keep them. The workspace supports a retention period from seven to 365 days, and responses expire according to that setting. Export answers you legitimately need before expiry and manage downloaded copies under your own retention process. An export is a separate copy; deleting or expiring a hosted response does not remove a spreadsheet already downloaded by a team member.
Public forms should not invite passwords, payment credentials or unnecessary personal details. Add a short explanation above an open text question if people might otherwise include sensitive information. Keep participation voluntary and do not present feedback as a prerequisite for ordinary service. Review the form on a small phone before printing: question order, answer choices and the completion message should make sense. Volunteers answering a survey may not represent every customer. A rating average can guide investigation, but it does not explain the cause without context. Review response counts alongside averages, and make sure the people reading free text have a reason to access it.
A worked example
A repair desk wants to know whether pickup instructions are clear. It creates one rating question, a choice about which instruction was confusing and an optional comment. The introduction explains who reads responses and the chosen retention period. Staff scan a paper sample and submit a test answer to check the thank-you step. Each week the manager reviews themes alongside response counts and exports only data needed for the review, storing that copy with its own deletion date. The desk keeps a normal support contact for urgent issues.
Common mistakes to avoid
- Inviting confidential details in free text.
- Ignoring retention for downloaded exports.
- Treating a handful of ratings as everyone’s opinion.
Prepare, test, then publish.
- Choose the destination and check its details.
- Generate your code and preserve its white border.
- Test the artwork at the intended size, on a real phone.
Keep an accessible alternative such as a short written website address alongside the code. A QR image should make information easier to reach.
Frequently asked questions
How long are answers kept?
Choose the supported retention period in the workspace, from seven to 365 days. Check that setting before publishing and tell respondents what it means for their answers.
Can I export responses?
The workspace supports CSV export. Export before expiry when appropriate, and protect the downloaded file because it becomes another copy of the answers with its own lifecycle.
Who can respond?
Guests can use the public form without creating an account. Anyone with the link may reach it, so avoid treating link possession as identity verification or membership proof.