Talk to a human

What to include so we can help fast

For product questions, the more concrete the message, the faster the answer: the page or QR code you were working with, what you expected, and what happened instead. A screenshot beats a description. If a code in the wild misbehaves, include where it is printed and roughly when it was created — that usually pins the cause in one round-trip.

Before writing, two shortcuts may save you the wait entirely: the help center answers the most common how-do-I questions, and the guides cover printing, sizing and scan-safety topics in depth. For partnership, volume or team questions, mention your use case and rough scale — see also Qrcado for teams and enterprise. We read everything that arrives; replies come from a person, not an autoresponder.

Feature requests and honest criticism are welcome — several of the QR types and settings in the product exist because someone wrote in and described a job the tool did not cover yet. If you believe you have found a security issue, say so in the subject line so it is triaged first, and please do not publish details before we have had a chance to fix it.