Skip to main content
Examples use a wholly fictional cross-border marketplace merchant-recruitment scenario: onboarding information, product categories, target markets, missing documents and human follow-up. They are not drawn from real customers and state no platform policies, fees or admission promises.
The default entry is AI Workbench; see the workbench guide. The legacy Assistant Chat steps for #, / and images below apply only where that drawer and command list are actually available. Check the currently supported commands before sending. Chat does not automatically read the current page or selected window, or replace saving configuration.
Assistant Chat is the conversation drawer on the right of the top bar. Beyond asking questions, you can type # in the input box to bring up forced commands (#work to start work, #stop to pause work, #help to view all commands, and more), or type / for natural-language suggestions such as “Please help me organize today’s conversation records”. This page covers two things: getting everyday tasks done with commands, and finding the right place to correct the AI — and coach it — when it answers wrong, so it becomes a coworker who understands your business better.

When you’ll need this

  • You want the AI to start or pause work, or turn group chat replies on or off, right away — without digging through configuration pages.
  • You want to turn the AI’s daily or weekly reports on or off.
  • You need to add just one key piece of knowledge, without going through document upload and generation tasks.
  • The AI answers inaccurately, mistakes someone’s identity, or speaks in a group where it should not — and you need to find the right place to correct it.

How to get there

Top bar, right side → “Assistant Chat” (the hover tooltip reads “Open admin assistant chat”). The drawer opens from the right side of the page; its title is “Admin assistant chat”, and the input box is at the bottom of the drawer. It is not bound to the “Selected window” on the left.
The scope note at the top of the drawer reads: “This entry is not bound to the communication window selected on the page. It cannot confirm that window’s configuration is in effect.” To verify a communication window’s configuration, test it with anonymized recruitment conversations on that channel — do not draw conclusions from the replies here.

Steps

1

Open the drawer and understand its conversation scope

Once it opens, look at the conversation area and the input box first. When there is no message history, the conversation area reads: “Chat with the admin assistant using the existing chat service. The window selected on this page is not supplied as a test target.”How to tell it worked: the title reads “Admin assistant chat”, and the input box placeholder is “Please enter your question”.Note: switching pages or changing the “Selected window” does not change the conversation scope of this drawer.
2

Type "#" to bring up forced commands and send one

Type # in the input box and a command list pops up above it, containing every forced command and its description. Use ↑ ↓ to move through the list, press Enter to select, press Esc or click outside the input box to dismiss — or click an item with the mouse. The command is written into the input box; press Enter again or click the send button at the bottom right to send it. Keep typing letters (for example #w) to filter the list.How to tell it worked: your command and the AI’s reply appear in the conversation. When the assistant returns several items at once, they are shown as separate messages, and “AI is thinking…” is displayed while you wait.Note: while the list is open, Enter selects a command instead of sending it. If sending fails, an error message pops up (showing the reason returned by the server, commonly “Request failed. Please try again.”), and that message is removed from the conversation history — type the original message again to resend it.
3

Pick the command for your scenario

The list contains these commands, with the exact interface descriptions:Group them by purpose:
  • Work status: #work to start work and #stop to pause work. Use them to start or stop the AI on the spot.
  • Group chat replies: #enable_hot_assistant to enable group chat response and #disable_hot_assistant to disable it.
  • Daily and weekly reports: #enable_daily_report / #disable_daily_report turn the daily report on or off, and #enable_weekly_report / #disable_weekly_report do the same for the weekly report. These are work summaries the AI generates each day or week — stop them with the disable command when you no longer need them.
  • Knowledge and help: #chatknowledge (Single knowledge entry) is for adding one key piece of knowledge — send it and follow the assistant’s prompts to complete the content in the conversation, with no document upload needed. #help (View all commands) is what to send first when you cannot remember them all.
How to tell it worked: the AI replies to the command; use the reply to confirm the command did what you expected.
4

Type "/" to get things done with natural-language suggestions

Typing / brings up four natural-language suggestions. Pick any one — you can still reword it before sending:
  • Please help me organize today’s conversation records
  • Generate this week’s work report
  • View last week’s business performance
  • Help me enable group chat replies
How to tell it worked: the AI’s reply appears in the conversation after you send.Note: these suggestions are one-line requests to the admin assistant — selecting one just writes an ordinary message. Change details such as the time range or the target to match your situation before sending.
5

Handle images and conversation history

  • Click “Attach image” at the bottom left of the input box to pick images and send them along with your message. The send button is unavailable while an image is uploading; pressing Enter during that time shows “Images are uploading, please wait…”; a failed upload is flagged with an error on the preview and an error message pops up.
  • “Clear chat” at the top right of the drawer clears all messages in the current conversation; the confirmation dialog reads “Are you sure you want to clear all messages in the current conversation? This action cannot be undone.”, and “Chat history cleared” appears after you confirm.
How to tell it worked: the image appears in the preview above the input box, and after sending you can see it in your own message bubble.

Correcting and coaching: where to fix the AI when it gets it wrong

Whether the AI answered well is not a matter of feeling — it is a matter of records. Start in Detail Review: open the inquiry and look at its “Reference Knowledge” and “Execution Steps” (in order: Conversation Context at That Time → Group Handling → Reply Decision → Skill Invocation → Knowledge Generation → Safety Guardrail) to tell whether the problem lies in knowledge, rules, or identity recognition. Then use the table below to fix it in the right place. After changes, retest the same type of merchant question in the target channel and inspect its actual record in Detail Review. Suggestions and learning counts help locate issues but do not replace individual checks. Review pending knowledge regularly.

Checkpoints

  • Typing # shows the full command list, and typing / shows the four natural-language suggestions; sending #help shows all commands in the conversation.
  • After you send a command, the conversation shows your message and the AI’s reply (multiple replies appear as separate messages).
  • You can explain the relationship between Assistant Chat and the “Selected window”: it is not bound to a window and cannot replace verification of that window’s configuration.
  • When the AI gets something wrong, you can tell from the symptom whether to go to Knowledge Optimization, Knowledge Management, Skills Library, Safety Guardrails, Reply Rules, or Relationships.

Important notes

“Clear chat” cannot be undone. The confirmation dialog reads “Are you sure you want to clear all messages in the current conversation? This action cannot be undone.”; clearing affects only the conversation history in this drawer.
The command list is the one that pops up when you type #; sending #help also shows all commands. Command names (such as work and enable_daily_report) are fixed spellings, while the descriptions in the list follow the interface language.
Commands are for quick actions; long-term, window-level configuration still happens on the matching pages — Base Persona, Reply Rules, and Safety Guardrails all save per “Selected window”, while Assistant Chat is not bound to a window.

Frequently asked questions

I typed ”#” but the command list did not appear?

Check whether # is the first character in the input box — the list pops up only when the message starts with # or /; once it is open, press Esc or click outside the input box to dismiss it. Also, the input box is disabled while the AI is replying (“AI is thinking…” is shown), so wait for the reply to finish before typing.

Chatting in Assistant Chat works fine — why is the AI still wrong in a real window?

Because this drawer is not bound to the selected communication window, its conversation cannot stand in for a test of a window. To verify a window’s configuration, test with real messages on that channel; to trace how a specific inquiry was handled, open its “Execution Steps” and “Reference Knowledge” in Detail Review.

Where do questions the AI cannot answer go, and how do I fill them in?

Needs answer (Test) uses local demo questions. Confirming, ignoring or changing categories does not write to the production knowledge base; refreshing restores the examples. Submit reusable answers through Knowledge Generation → Enter Existing Knowledge, then review and verify storage.

I switched the interface language — do the commands still work?

Yes. Command names are fixed spellings (such as #enable_weekly_report), and the descriptions in the list change with the interface language; if you are not sure what a command does, read its description in the list or send #help.

What does “Clear chat” clear?

Only the conversation history in this drawer, and it cannot be undone; backend configuration is not affected. To keep the basis for a decision (for example, a conclusion from a correction), fix the knowledge or rule on its own page before clearing the chat.