Handle feedback, replies, and notices

A user asks the Service to pass on feedback. After contacting the administrator, the Agent can confirm submission, not that someone has read it.

Try it · Show the synthetic Service conversation and submission response.

Open Inbox and select View and reply. Opening feedback acknowledges it; that is different from resolving the issue.

Try it · Open the sample feedback and observe its case status.

Select View conversation to inspect the request and the Service’s response. Use the context to understand the issue before drafting a reply.

Try it · Open the linked conversation and locate the answer without citations.

Write a concrete next step and select Submit reply. The reply stays bound to the original conversation. Check delivery after it is submitted.

Try it · Enter the sample reply, submit it, and show the pending status.

Delivery acknowledged is not a read receipt. Retry a pending delivery when appropriate. For an unknown outcome, check first: resending can create a duplicate.

Try it · Inspect the sample delivery and open the resend confirmation.

After correcting the material and replying, select Mark resolved. This records the case as handled; it does not recall messages already sent.

Try it · Select Mark resolved on the sample feedback.

Open a published Service and choose Send a direct notice. Select conversations, write the exact message, then choose Send now or Schedule.

Try it · Select two demo conversations, enter the text, and queue the broadcast.

Open Delivery by conversation. Web pages update automatically, API clients must read events, and WeChat uses the current session. Direct notices do not call a model.

Try it · Expand the broadcast details and inspect each conversation’s status.