The most useful features are the ones that help you finish a task without getting in the way.
Read article
A clear screen gives every action a purpose. Start with the task you want to finish, then look for the next useful step rather than exploring every setting at once.
When you need help, describe the outcome you expected. A specific example is much easier to follow than a list of features that seem confusing. Include the screen you were using and the action you selected.
The knowledge base is a useful starting point for common questions. If the answer needs more context, keep the conversation together in a support ticket.
Explore the help guides, or contact support with your question.
A small amount of context can make a screenshot much more useful to the person helping you.
Read article
Capture the part of the screen that shows the problem, together with enough context to identify where it happened. Avoid sending an entire desktop when only one message matters.
Before sharing an image, remove passwords, personal details, and information belonging to other people. Write out any error message too, so the person helping you can copy and search it.
Explain what you selected just before the screenshot and what you thought would happen. That short description connects the picture to the problem.
Explore the help guides, or contact support with your question.
Keep your work safe, collect the details, and give a stubborn problem a useful starting point.
Read article
First, save a copy of any unsaved work. Reloading a page or restarting an app can clear text you have already entered.
Check your connection and note the exact error message. Try one change at a time so you can tell which step made a difference. If an extension may be involved, compare the same page in a private browsing window.
If the issue continues, write down your browser, device, page address, and the steps you tried. These details help support understand the problem without asking you to start over.
Explore the help guides, or contact support with your question.
Keep a support conversation easy to follow, even on a small screen.
Read article
Use a short subject that names the problem. On a phone, it is especially helpful to put the key information at the beginning of your message.
Mention your device and browser, and describe whether the issue happens on Wi-Fi, mobile data, or both. Only share details that are relevant to the request.
You can return to My tickets to continue an existing conversation. Keeping replies in one place helps everyone follow the steps you have already tried.
Explore the help guides, or contact support with your question.
A few useful notes now can save time if you need help later.
Read article
Keep the app name, the place you downloaded it from, and any order reference somewhere you can find them. These details make it easier to identify the right product when you ask for help.
Use the official update route for the app. Before changing versions, make sure important work is saved and check whether the update includes instructions that apply to you.
If you contact support, include the version you are using and the exact problem you can reproduce. Never include a password, payment-card number, or private access code.
Explore the help guides, or contact support with your question.