SymptomLink to this section
You have read the article and the answer is not there, or something in the product is wrong and you want a person.
Three ways inLink to this section
Send feedback from inside the app. The account menu, Settings → Help & support, and the footer of every help article open the feedback dialog. It attaches the page you are on and can attach the details of the last error, which is usually what solves the problem. Use this for bugs and for "this article did not match what I see".
Request a change on the roadmap board. For a feature you want or a change you would like, the public roadmap and requests board collects requests where other writers can upvote and add to them. Every help article's Request a change exit opens the board's composer with that article attached, so the team sees what you were reading. Requests that ship are announced on the changelog.
Email. Write to the support address on the contact page. Replies typically arrive within one business day. Use email for billing questions and for anything that involves your account rather than a project.
What to includeLink to this section
- What you were doing, and what you expected.
- The project's name and the draft line, if it concerns one.
- For a skill run: the skill, the scope, and roughly when it ran.
- A screenshot, if the problem is on the screen.