Support and feedback¶
When you run into issues with MatrixOne Intelligence (MOI), Genesis, or MatrixOne Cloud instances—or want to share product feedback—use the console assistant, support email, feedback API, or documentation feedback tools below.
Support channels¶
Channel |
Best for |
Where to open |
|---|---|---|
Console Feedback Assistant |
Submitting troubleshooting requests or product suggestions from a workspace and tracking ticket status |
Feedback Assistant launcher inside the MOI workspace |
Email support |
Account onboarding, billing checks, private deployment assistance, or urgent incidents |
Contact Us menu in the top-right console header, or email contact@matrixorigin.cn |
Feedback ticket API |
Creating and querying tickets from internal tooling or scripts |
|
Documentation feedback & edits |
Reporting missing steps, inaccuracies, or submitting fixes to documentation pages |
Was this page helpful? widget and Edit this page on GitHub in the right sidebar |
Submit a ticket in the console¶
Sign in to MOI, enter the affected workspace, and open Feedback Assistant.
On the New Feedback tab, enter the Title, Description, Expected Behavior, Actual Behavior, Reproduction Steps, and Suggested Priority, then click Confirm & Submit.
While troubleshooting with a workspace agent, you can also ask the agent to draft a feedback ticket card, review the fields, and confirm submission.
Switch to Feedback History to track ticket status (Submitted, Processing, Replied, Resolved, or Closed) and administrator replies.
Email support and what to include¶
For account, billing, or urgent operational assistance, select Contact Us in the console header or email contact@matrixorigin.cn.
Include the following details to help locate the issue faster (never share API keys, personal access tokens, or passwords):
Workspace name or ID: Copy it from the Workspace switcher.
Task or request identifiers: Relevant import task ID, workflow run ID, conversation ID, SQL
Query ID, or GenesisRequest ID.Timestamp and environment: Approximate time of the failure, region or deployment tier, and SDK/CLI version if applicable.
Error message and reproduction steps: Exact HTTP status code, error payload, or redacted console screenshots.
Self-service troubleshooting links¶
Before opening a ticket, start with Troubleshooting and FAQ and the Error codes and status reference, or inspect the module guides below:
Account readiness and roles: Before you begin and Member management.
SDK, CLI, and version compatibility: Version compatibility and artifacts and Developer overview.
Messaging channel connection issues: IM integration troubleshooting.
Ingestion and job execution status: Load tasks and Job monitoring.