Questions and feedback
Open Assistant in a project to ask questions, report problems, or suggest improvements. Assistant in Profile also supports general questions without choosing a project.
Submit a question or suggestion
Describe your question directly or choose one of six starting points: Usage help, Report a problem, Experience feedback, Feature suggestion, Account and permissions, or Charges and orders. Selecting a card only changes the input hint; it does not send a message or erase your draft.
Use Switch project in the Current project row to select the affected project. General questions do not require one. Existing conversations retain their original project; switching projects starts a new question.
You do not need to identify the technical cause or responsible team first. Include information appropriate to your request:
| Request | Helpful information |
|---|---|
| Usage question | The task you want to complete, your current page, and what you have tried |
| Bug or unexpected behavior | Steps to reproduce, actual and expected results, time of occurrence, client, and version |
| Experience improvement or feature request | Your use case, what is difficult, and the improvement you would like |
| Account or order issue | The message you received, the relevant workspace, and any visible order or request reference |
If an error entry has already attached diagnostic information, review your description before submitting. Do not send passwords, verification codes, API keys, signing keys, or payment credentials in a message.
Investigation and handling
The platform can investigate using your description and accessible business records. You may be asked for more information when records are missing. A missing record alone does not prove an action never happened.
AI replies carry an AI label. AI can help organize information, explain observed facts, and provide guidance supported by available sources. For matters requiring a platform decision, rely on an explicit response and a verifiable result. Receiving a reply does not mean a refund, fix, or feature release has been completed.
For application generation or preview problems, associate the affected project where possible. Project conversations include a diagnosis card. Use View diagnosis details inside the card to inspect accessible persisted execution results, including state, outcome, verification state, and evidence references. General conversations do not display project diagnostics. An execution still in progress has no final result; missing records do not establish that nothing went wrong. Summaries exclude raw model messages, source, and credentials.
Questions, additional information, and replies remain in the same conversation and are available to platform support. Continue application changes in the project’s build conversation.
Follow up on a conversation
Open the separate History page in Assistant, then select a conversation to read replies and check status. It lists all your own conversations in the current workspace and labels each conversation with its project. Add information to your own conversation while replies are available instead of submitting duplicates.
Conversation status describes the progress of support communication. Closing a conversation does not by itself establish that a bug was fixed, a suggestion was accepted, or a feature shipped. Look for an explicit response and a verifiable product change.
Your conversations are handled by you and platform support. Other workspace members cannot read them or reply on your behalf. Changes to project access affect diagnosis access. If a send result is uncertain, keep the original input and retry that send; the system returns the stored receipt without creating a duplicate.
Use the composer plus button to upload images, Markdown, JSON, PDF, or Office documents. Attachments can be sent without text. Each message allows up to four files totaling 20 MiB: 5 MiB per image, 1 MiB total Markdown, and 10 MiB per other document. Finish uploading before sending; sent attachments remain accessible from their messages.
Assistant uses extracted document text and image input supported by the configured model. Extracted text is bounded; scanned PDF pages and embedded Office images are not automatically recognized. Provide a separate image or text for those contents. Each response loads at most the four most recent attachments; older files may need to be provided again. A reply does not establish that every attachment was read in full.
Common questions
Does a successful preview mean publishing succeeded? Preview and publishing are separate actions. Check the project’s publishing result, then verify the published address or delivered artifact.
Does switching projects move an existing report? A submitted conversation retains its associated project as context. Start another conversation for a different project.
Does submitting a suggestion mean it will be built? Submission records your request. Acceptance and availability require a subsequent decision and explicit result.
Why am I asked to sign in again? Your session may expire. After signing in, check the original conversation or operation result before retrying.
See the Product user guide for the main workflow.