Manual replies should go back into the same visitor chat so the lead does not receive a disconnected thread. When an employee takes over, the answer must not remain an internal note. The visitor expects the conversation to continue in the widget.
Write the reply in the lead space, check recipient and chat binding, then send it back to the original widget conversation.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Draft a short manual reply to this lead and mark which internal notes must not be sent to the visitor.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to employee reply, widget history, internal notes, recipient check and chat binding. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not copy internal scoring, team notes or private assessment into the visitor reply.
The lead space remains the team cockpit while the visitor sees a normal chat continuation.