Select Test a Service at the top of an admin chat. Finish active replies and approvals before changing the role handling your messages.

Select the saved draft and start testing. Following messages use the Service’s engine, rules, and file scope, not the admin chat’s selected model.

Ask a realistic user question. Check whether the Service uses allowed documents and explains missing information instead of inventing an answer.

Service testing does not inherit earlier admin conversation history. Ask about a detail mentioned only in the admin chat to check that boundary.

Contacting the admin is simulated and creates no real inbox notice. Other authorized tools may execute, so testing can still consume model or tool usage.

Exit test mode; the records remain in this chat. Ask the admin Agent whether the issue needs better documents or a change to the Service rules.

After saving changes, the previous test selection may be invalid. Exit and reopen as prompted, rather than treating a configuration change as unpredictable model behavior.

Repeat the same question and compare the answer. Then verify the real workflow through the Service’s web, API, or WeChat channel.