Get help and report a problem
Find an answer or send a report that the team can act on.
Use Help Center search for a guide or open Ask AI to ask a question in your own words. Both use the product documentation. They cannot inspect your private releases, tasks, comments, or financial records.
For a sequence of practical guides, choose a learning path. For a specific failure, start with troubleshooting.
On desktop, choose Report a problem in the sidebar. On mobile, open Settings, find About, and choose Help & feedback. Pick the appropriate report category and describe the issue. This report form is separate from the Help Center conversation.
Open Ask AI. You can use this conversation without signing into a workspace.
Ask a product question or choose Talk to a person once the conversation has loaded. You do not have to finish an assistant exchange first.
Add the specific problem and relevant context. If you came from an article or search, its context can accompany the conversation.
Follow the conversation status. Waiting for mgmtOS Support means the request is in the queue, not that a person is already online. Replies appear in this conversation.
Read Ask AI and contact support for source links, session recovery, and privacy boundaries.
For a standalone report, open Report a problem. Sending that form requires your workspace session, but not an active subscription. When signed out, it preserves the displayed article and search context through sign-in. If signing in is the problem, use the guest conversation instead.
What you were trying to do.
The release, task, or screen involved.
The steps that led to the problem.
What you expected and what happened instead.
The exact error text and approximate time, if available.
In Planner, I moved Night Drive to the next Friday. The date changed briefly, then returned and showed a save error. I expected the new date to remain. The issue happened around 14:30 in my desktop browser.
The signed-in report form includes account and workspace context. When session recording is active, the in-product support flow can attach a replay reference. The chat includes the messages you send and the available article or search context; the support team can read that conversation.
Do not paste passwords, session cookies, API keys, invitation tokens, or full payment information into either flow. A public Help Center does not make your conversation a public article.
In chat, check for your message in the history. If delivery could not be confirmed, use Retry send for that same message instead of composing a duplicate. A resolved conversation has a Reopen conversation action.
For the report form, keep the confirmation or reference you receive. If delivery is unconfirmed, avoid immediately submitting the same report again. Correct a validation error before retrying. Neither flow promises a response time.