Customer Service Agents Might Be Able To See What You're Typing In Real Time (gizmodo.com)
Gizmodo is warning that some customer service agents might be able to see what you're typing in real time. A reader sent them a transcript from a conversation they had with a mattress company after the agent responded to a message he hadn't sent yet. From the report: Something similar recently happened to HmmDaily's Tom Scocca. He got a detailed answer from an agent one second after he hit send. Googling led Scocca to a live chat service that offers a feature it calls "real-time typing view" to allow agents to have their "answers prepared before the customer submits his questions." Another live chat service, which lists McDonalds, Ikea, and Paypal as its customers, calls the same feature "message sneak peek," saying it will allow you to "see what the visitor is typing in before they send it over." Salesforce Live Agent also offers "sneak peak."
This particular magic trick happens thanks to JavaScript operating in your browser and detecting what's happening on a particular site in real time. It's also how companies capture information you've entered into web forms before you've hit submit. Companies could lessen the creepiness by telling people their typing is seen in real time or could eliminate the send button altogether. So if you don't want to be monitored or send secret messages to agents, put your phone on mute while on hold and copy/paste messages from another document to your customer service chatbox. And in general, be nice to customer service agents. It's not their fault.
This particular magic trick happens thanks to JavaScript operating in your browser and detecting what's happening on a particular site in real time. It's also how companies capture information you've entered into web forms before you've hit submit. Companies could lessen the creepiness by telling people their typing is seen in real time or could eliminate the send button altogether. So if you don't want to be monitored or send secret messages to agents, put your phone on mute while on hold and copy/paste messages from another document to your customer service chatbox. And in general, be nice to customer service agents. It's not their fault.
The logical solution would be to insert a false delay of 3-5 seconds whenever the user types something to the CSR's replies so that it is never perceived to be answering too fast.
As for the creepiness factor—you're typing stuff into a text box on a website, nothing should be considered hidden from them.
...
I always assumed that the CSRs could see every keystroke I type in the chatbox.
If I have a long question (often the first question is long for example), I usually type the text into emacs (and, if I'm being picky, spell check it as well) and then cut and paste into the chatbox just to avoid confusion (such as me leaving out a "not" and later correcting it and the CSR never noticing my correction).
Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading
I just chatted with Amazon support yesterday. I'm gonna type, "Fuck you," and wait for a ten count and then back over it.
It little behooves the best of us to comment on the rest of us.
If this really bugs you, just type your response into some other text editor. Notepad, or even a comment submission window on slashdot. Then cut and paste it into the CSR window.
This is probably happening. Just as likely is the person has a million calls about your issue and knows what you are going to say. They likely have some canned answers. I'm on the other end and I have canned information; I tech support chat so often I have a txt file with everything in it - explanations of troubleshooting processes, error codes, contact information - I know what they are going to ask me. Like I tell my kids, I'm not smart, I'm just old...
Old news. Very old news
"live chat" has caught up to ICQ in the 90's.
Back in the days of "smart" (and "dumb") terminals, live chat enabled some attacks.
For instance: sending a control sequence that reprogrammed a "soft key" and then "pressed" it, allowing the attacker to execute commands as if the victim had typed them. (This could include suppressing the visibility on his screen so he didn't know it had been done.)
I wonder if these systems have an analogous vulnerability?
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
This feature could be used to game the system. Slowly type in some question and leave it for a few seconds for them to digest. Then make a minor change that changes the sense of your question and quickly hit send. If they don’t notice the change, there’s now a chat log in your favour. Profit.
The fact that you think most needs should know about this or care says more about your understanding of nerds than it does about nerds understanding.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
I was chatting to my phone company about my modem. They lulled me into a false sense of security by asking for info I'd already given. But a bit later I thought better of a somewhat tetchy paragraph and replaced it with a calmer one. Then they referred to something in the paragraph I had not sent.
Then they offered to call me and I had a friendly conversation with a nice young lady who fixed my problem. I was left wondering: good customer service, or psychological warfare?
Bah! Old bulletin board systems (BBSes)'s had real-time chats too. Now, get off my lawn! :P
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
I used to work in a technical support role. We used a chat service provider called comm100 which does show the agent what you type in real time. At first, I felt dirty like I was invading their privacy, but it does help efficiency considerably. It's invaluable when it comes to de-escalating clients that start to type out a giant rant, then slowly edit it to be more civil... eventually they just chicken out and delete their entire whiny post when they decide it's not worth it. It feels bad and dirty, but also consider that the support agent is usually multi-tasking between clients, so being able to know what you are typing as you are typing it is a real time saver. The worst is when the client has typed out part of a question which you know the answer to and have a full response typed out, then you have to wait for them to hit the 'send' button before you can continue answering the question or solving the problem. Sometimes you have to wait a LONG time.
Is this a big deal? I worked on a CSR chat system for a major clothing retailer back in the early 00's that had that feature. If I remember right, there was an ActiveX version for IE and a javascript version for anyone else and you configure it to see as the user typed or wait until they hit "Send". The idea was that if you watched the person type, the CSR could start to compose their answer so that there was a small delay as possible.
Yes of course this behavior is unacceptable. You are being dishonest with the customer. If you want to do this legitimately all you need to do is configure the interface such that what customer types appears in sent area of message box as CSR sees it so there is no confusion or assumptions about what is happening.
When you design a UI like this it's not materially different than creating an interface where dismissing an upgrade prompt causes Windows 10 to be installed. You know damn well what a particular UX design almost always with an explicit 'Send' button conveys to a normal person. This sort of shady behavior sure as heck is not that.
Would love to see some nuisance lawsuits over this shit.
Normally I am paranoid about privacy, but this seems like a good thing. Why wouldn't you want them to respond faster?
By including this sig, the copyright holders of this work or collection unreservedly place it in the public domain.
The chat client ICQ was doing this back in 1998. Why is it surprising that this would still be possible 20 years later?
*slight crashing sound*
I've already had a couple of conversations with support agents when their replied to the messages I hadn't yet sent which made me feel extremely awkward but now I know that I should never ever paste anything in such chat windows without first verifying that my clipboard contents are the one I really intend to share.
Dude, the 2A isn't 'assholes wanting to threaten your life because their 10 mb/s broadband is only testing at 5 mb/s, despite the fact that somebody else in the house is streaming HD Netflix, the right to keep and bear arms shall not be infringed.'
Vintage computer games and RPG books available. Email me if you're interested.
At any rate, it is so easy to get around it, if necessary, that it hardly deserves any discussion.
What does doing that buy you?
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
Sometimes it is their fault, like when they're trying to do something unethical or illegal with the excuse being that it's part of their job. Fuck them. Fuck them sideways. They're part of the problem. Getting paid for your bad behavior doesn't make it less bad.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Evil technology!
Why, back in my day we called people, and of course the person on the other end of the telephone doesn't hear anything until I finish a sentence... oh wait.
There's obviously no reasonable expectation of "privacy" in this scenario -- but frankly, if you're using a computing device of any flavor, and if that device is attached to the internet, then you should probably just automatically assume that anything you do on that device could potentially be tracked. It obviously won't always be the case... but it might be the case, on occasion. This thought process kind'a falls under the "plan for the worst, hope for the best," kind of thing.
As an obvious direct example: I was attempting to negotiate with Verizon just recently, to try to circumvent an obvious "bait-and-switch" tactic that they had used during the Cyber-Monday promotional. At one point, I think I made the mistake of typing a comment into my "open mic" chat session, that essentially admitted that I was on the verge of just taking the deal, regardless of whether or not they agreed to give me what they had originally promised -- but of course, I backspaced over that before submitting. I realized a few minutes later what had probably happened, as my leverage completely evaporated in very short order. That mistake effectively cost me $200. (I left an absolutely scathing review of the CSR after the fact, describing what had happened... which, in retrospect, probably prompted some enthusiastic high-fives and kudos from the CSR's manager. So yeah... fuck you, Verizon.)
Lesson learned, though: just always assume that the mic is open.
If you are in a live support chat the agent already knows you are frustrated and angry because if everything was great you wouldn't be talking to them at all. Anyone that has worked in IT knows you sometimes just have to let people vent before you can help them. It's not a big deal.
Yes. Similar story here. How did this become news though, it's not new, it's not even that special, or interesting. A large number of /. readers would know this already, those that don't will not need to think much about it, it is pretty simple and is there as a feature for the operators to be able to read or get some more insight into what the customer is thinking about when they're raising a live chat ticket.
Why UNIX?