Contacting support
What to include in a support request
Platform and version, the steps you took, the result you expected, the result you got, and the identifier of whatever went wrong. One complete message is answered faster than five short ones, because each round trip costs a working day.
Steps
- Say which platform you are on — web, iOS, Android or the Chrome extension — with the browser or OS version.
- Give the steps, the expected result and the actual result, in that order.
- Add the identifier that finds the object: the workspace, the QR code, the bulk job id, or the API
requestId. - For a scanning problem, add print size, material and the two device models you tested on.
- For an API problem, add the HTTP status and the error
code— with theAuthorizationheader masked.
How to check it worked
Read your message back and ask whether someone without access to your screen could reproduce the problem from it alone.
What usually goes wrong
- A screenshot with no description, so nobody knows what should have happened.
- “It does not work” with no identifier, which cannot be looked up.
- Sending the API key instead of the request id.
Did this get the job done?
This did not help
Write to us with the platform and version, the steps you took, the result you expected, and the workspace or QR code involved. Mask any secret before you attach anything.
Write to support