We recently purchased two of Motorola's new products, the Moto G. For the most part we are initially impressed with the new phones, but only one of them will connect for transferring files. I think they call the type of connection MTP. It would connect as a camera, but that limited it to just the camera directory, so I couldn't transfer to the music directory.
I am guessing I could've transferred to the camera directory and then transferred out of it and into the music folder with the phone itself.
I contacted technical support via chat. I waited to be connected to someone for about 15 minutes. Once I got connected they asked me to do the usual "turn it off and back on" and such. I had already done that and did it again. No luck. They gave me a link to some article about clearing the cache or something. While I read the article and tried to figure out how to do what it was explaining the tech support agent typed to me that I had been inactive for two minutes and they were going to give me one more minute and then disconnected.
The link they sent me did not work for me. I could not tell them, since they hung up on me.
I don't understand why they were in such a hurry to hang up. It is a chat window. You should be able to have several chat windows up, so they could help another customer while waiting on me. The only explanation I can think of is that there is some metric that some manager is using to measure performance. They must be tracking how quickly they resolve the call. That doesn't measure if they actually helped me.
I hurried and went back to chat and sat on hold for another 15 to 20 minutes. The customer service person quickly walked me through finding my serial number and then quickly gave me a phone number and other information on Level 2 tech support, which I couldn't call until morning, and then hung up on me again.
Level 2
The next morning I called level 2 support. Level 1 had told me that if I entered in my phone number at the beginning of the call, level 2 would see the chat history and be able to read everything that we had talked about before helping me.
When I called level 2, then asked me for my phone number a second time, even though I entered it in their system via the phone I was calling from. They then asked what they could help me with. I asked if they had read the chat history. They said they had not and put me on hold to read them.
Level 1 support had tried to switch me into developer mode at one point, but didn't know how to do it properly. Level 2 tried the same thing.
They wanted me through switching it, but also gave the wrong instructions, but I ended up getting it to go anyway. They had told me to tap About Phone 7 times in settings. It only took three. That allowed up to turn on USB debugging. Once I did that I could see all the folders, even though it still would not go into MTP mode normally.
I took this work around, since it did what I needed, but I was concerned about leaving a phone in developer mode, where the user could inadvertently get into something that could make a mess. Tech support told me how to turn it off (tap About Phone seven times) and the instructions were incorrect. All it did was tell me the phone was already in developer mode. They never could get it to switch out of developer mode.
While in developer tools I notice a switch to turn it off. It still left the developer tools menu, but once in there it had to be turned on or off, so that was more acceptable to me. It still did not fix the problem with the phone, but it gave me a work around.
As support worked with me, it was like they were unfamiliar with my phone. This was true of level 1 and level 2 support. Perhaps it is too new, but I figured Android Jelly Bean on one Motorola phone would be the same as another.
The bottom line is that Motorola customer service appeared not well trained and more interested cranking a call queue than solid support of their customers. By the length of time I spent on hold and the desire of customer service to dump calls, it also appears that they are under staffed. Additionally, I got a work around, but the problem was not solved.
No comments:
Post a Comment