Screenshot-ready guide
Use this article with current in-app screenshots when the workflow needs visual confirmation. Keep screenshots focused on the exact field, button, or page state being explained.
When opening a support request, include the page URL, the action you were trying to complete, the expected result, the actual result, and the time the issue happened. Screenshots are useful when they show the exact field, modal, button, or error state.
Do not send passwords, one-time verification codes, full payment card details, private keys, or unrelated confidential documents through support messages.
If the issue blocks a project application, billing action, company verification, or account access, include that priority in the request so support can triage appropriately.