My name is Craig. I live in Florida. I have a problem that no one seems able to solve. Motorola has lost my I850 phone that I use for a home based business. It was sent to Memphis on a (door to door) service (RMA 22387 & case number 252922) This phone has been sent in for repair four times in less than eight months. The last two times, I sent the phone to El Paso then ten days later, it came back (supposedly a new phone) bad right out of the box. I got Motorola and Nextel on a conference call and Nextel agreed to pay $55 for the door to door service on 7/12/07.
The phone was picked up by FED EX on 7/13/07. I was assured that I would have the phone back by 7/17/07. I have not gotten the phone back yet. This has set me back severely as I use the phone for a home based business. Not only that but on 7/18/07 I had to make a trip from Florida to Indiana to take my eighty year old mother to the Lincoln Center nursing home in Connersville Indiana. We made that overnight trip without the security of a cell phone. I have tried repeatedly call after call to get this resolved. Nextel wanted $299 for the same phone which made me angry enough to stop their service and switch to Verizon with a new LG VX8300 phone. I had to do this because of our home based business. I've lost $360 to $420 due to the phone being misplaces or lost. Nevertheless, the phone I paid for is still lost. I have asked escalations to call me a dozen times now and just today I was promised three times that I would get a call back from a supervisor. It is now 3:47 PM CST and no call. The other day I called the 1-800-453-0920 number at 6:30 CST and was placed on hold until 7 PM at which time I was hung up on. I called back and the automated service said the office was closed. I have spoken to Jason (Sup), Andre, Carl, Carol, Bill, and many others.
Now it is Aug. 6. I called again and talked with Jason your supervisor. He says he doesn't know why this can't be resolved. It seems very strange to me that supervisors can't resolve customer issues. Why can't I get this problem resolved?
0 comments