As it's implemented I'm not a fan of the idea for much the same reasons that have already been discussed. But I think there's a way to implement it that makes i

As it's implemented I'm not a fan of the idea for much the same reasons that have already been discussed. But I think there's a way to implement it that makes it more transparent to the user precisely what is going on: Aside from providing a banner indicating that the keystrokes are being sent, you could also show something in the conversation log window as the user types, similar to the way the CSR view looks with a small "sending..." caption above it. If you updated that with each keystroke, the user would see his message being composed in the composition field, and in the conversation log window at the same time. I don't have data to back it up, but if implemented properly, the cue would hopefully inform the user that what he's typing and re-typing are being seen by the CSR without requiring the user to understand whatever text was provided in the banner/notice (I subliminally dismiss those anyway).