Team / Brand rollout
You need repeatable QR workflows for a team, campaign, or brand system.
Use this when the question is pricing, rollout scope, hosted dynamic QR, bulk work, or branded print operations.
Discuss a rollout →Contact
Use email when the QR job needs a human decision.
Discuss a team rollout, hosted dynamic QR need, brand workflow, real bug, missing template, or product decision with enough context to move quickly.
Email lanes
Choose the kind of message before you write it.
Separate rollout, bug, template, and product feedback emails so the next step is clear before the thread starts.
Bug report
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 →Template request
You need a new QR type, preset, or workflow.
Best for asking for a new template, use-case page, visual preset, or a better workflow for a specific job.
Request a template →Product feedback
You know the direction, but the UX is getting in the way.
Use this for product-level feedback, missing controls, confusing steps, or conversion friction you noticed while building.
Send feedback →What to include
Send the context that makes the issue reproducible.
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.
For rollouts, give the operating shape
Mention team size, QR volume, whether destinations may change after print, brand requirements, and any print deadline.
Say which QR path you used
Mention the exact page or template, for example URL, WiFi, vCard, redirect QR, or a specific guide.
Include the real output problem
State what happened in practice: bad scan, wrong open target, export issue, print issue, or missing option.
Add reproducible context
Include device, scanner app, browser, export format, and the safe-to-share payload or a close example.
Say what you expected instead
The fastest way to get a useful response is to describe the correct result you were trying to produce.
Try this first
Some issues are faster to solve inside the product than over email.
If the next best action is self-serve, it should be obvious here instead of hidden behind one contact address.
Compare pricing boundaries
If you are deciding between free static QR, hosted dynamic QR, or team workflows, use the pricing page before opening email.
Open pricing →Check dynamic QR availability
If the main question is edit-later behavior, confirm whether this deployment can create hosted short links first.
Check dynamic setup →Fix a QR that will not scan
Open the troubleshooting path before you email, especially if the issue may be payload or print related.
Open scan troubleshooting →Choose the right generator first
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 →Use utility tools directly
For scanning, bulk work, or print sizing, the tool library is faster than opening an email thread.
Open tools →