Play.com stroke by ordering bug
Play.com a most popular online shop of UK for selling Gadgets, CDS, Movies and games are now suffering a great bug by sending the dispatch details to the customers, who have never ordered any thing from the site. Many customers reporting that they have received the email from Play.com which provides the details of an order dispatch which they have not place. Those who received the email on opening the orders found the information of contact details that also includes addresses and names of other play.com customers. The problem arises and many of them try to call Play.com help lines, which were jammed in order to complain against the site.
Simon Hurley nearer to Bristol at Clevedon says that, he had received more than 80 emails from play.com that shows the detail of the other customer name and their order. He also added that all the messages are in scrambled text at the bottom that hides some information, but doesn’t have any credit card information. This person also calls to the Play.com customer service after a long try of jammed soil and inform them that the site is in a massive problem. People are also informed to cut the documents were the big company of Play.com is sending their information through email spam to other users. It is not estimated about how many people have received the spam email which contains the information about the other customers.
Most of the forums also have the conversation about the erroneous emails received by them from Play.com. Some forum customer also said that they have received the mail as “system error” behind the sending of spam emails. For this massive trouble the reply from the Play.com spokesperson said, that they are aware of the incident affected some customers for a few period of time that happens in this morning, and they also apologized for the inconvenience caused to their customer who has a bad experienced as a result. They also reassure their customers by taking the cause of this incident seriously by investigating how this happened and resolved it that will not occur in the future.
Related posts: