Something broke or scans incorrectly.
Use this when the QR renders wrong, exports badly, or works on one device but fails on another.
Email a bug report →Report a real bug, request a missing template, or send product feedback with enough context to reproduce the issue quickly.
Keeping bug reports, requests, and product feedback separate makes the response path much cleaner.
Use this when the QR renders wrong, exports badly, or works on one device but fails on another.
Email a bug report →Best for asking for a new template, use-case page, visual preset, or a better workflow for a specific job.
Request a template →Use this for product-level feedback, missing controls, confusing steps, or conversion friction you noticed while building.
Send feedback →Most slow feedback threads happen because the original message does not say what QR was used, what failed, or what the correct result should have been.
Mention the exact page or template, for example URL, WiFi, vCard, redirect QR, or a specific guide.
State what happened in practice: bad scan, wrong open target, export issue, print issue, or missing option.
Include device, scanner app, browser, export format, and the safe-to-share payload or a close example.
The fastest way to get a useful response is to describe the correct result you were trying to produce.
If the next best action is self-serve, it should be obvious here instead of hidden behind one contact address.
Open the troubleshooting path before you email, especially if the issue may be payload or print related.
Open scan troubleshooting →If the issue is really “I picked the wrong QR type,” go back to the main QR hub and start from the job.
Open QR hub →For scanning, bulk work, or print sizing, the tool library is faster than opening an email thread.
Open tools →