> For the complete documentation index, see [llms.txt](https://docs.icraft.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icraft.design/support-and-feedback.md).

# Support & Feedback

iCraft is committed to providing users with **timely, professional, and ongoing technical support and usage guidance**.Whether you encounter issues with **modeling, scene design, animation editing**, or matters related to **accounts, purchases, asset management**, you can contact us through the following official channels.

***

## Support Channels Overview

We provide diverse support channels for different usage scenarios:

* Discord User Community：[iCraft Editor](https://discord.com/invite/3M9xuaB2FR)
* Official Email：<icraft@gantsoftware.com>
* Official Social Media Direct Message Support：
  * Xiaohongshu：[Follow us](https://www.xiaohongshu.com/user/profile/678712a4000000000500bc6f)
  * Douyin：[Follow us](https://v.douyin.com/rWyQfG4ixb4/)
  * Bilibili：[Follow us](https://space.bilibili.com/3546882682915403)
  * Youtube：[Follow us](https://www.youtube.com/channel/UC6wQsIYOA8u1JCPqx1NuQcg)

Users may choose the most convenient channel based on their habits.

***

## Best Practices for Submitting Issues

To help us resolve your problem **faster**, we recommend providing the following information when contacting support:

📌 **Feature module in use:** (e.g., Model Optimization, Animation Setup, AI Rendering, Templates Library, etc.)

📌 **Detailed problem description:** What happened? What is your expected result?

📌 **Step-by-step reproduction steps:** At which step did the issue occur?

📌 **Screenshots or screen recordings:** Visuals of the issue are highly recommended

📌 **Device & environment:** Browser type, OS version, enterprise account status, etc.

***

## Support Scope

Our support mainly covers:

* Feature usage guidance
* Frequently asked questions (FAQs)
* Preliminary technical troubleshooting
* Bug reporting and follow-up
* Product suggestion collection
* Account and order inquiries

The following cases may require separate handling or business support:

* Enterprise-level customization
* Dedicated on-premises deployment
* Deep API/SDK integration
* Business contracts and procurement processes

***

{% hint style="warning" %}
**Service Hours**

* Official support is available during **working hours: 9:00–18:00 (Beijing Time)**.
* Responses on community channels may be delayed; we will process all user feedback as soon as possible.
  {% endhint %}

{% hint style="info" %}
**Friendly Reminders**

* Please consult only through **official channels** to avoid disclosing sensitive information such as account passwords.
* Follow community guidelines and maintain a friendly discussion atmosphere.
* For complex technical issues or urgent assistance, we recommend using the Discord User Community for faster response.
* Enterprise users may contact their dedicated contact person for in-depth support.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.icraft.design/support-and-feedback.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.