Tiscali TalkTalk: Extremley bad service , cut off once, incorrect...
A Tiscali TalkTalk customer review by GetHuman user GetHuman-181771 from October 31st, 2017
Background on GetHuman-181771's case
GetHuman: GetHuman-181771 - can you tell our other Tiscali TalkTalk customers when your case took place?
GetHuman-181771: Sure. It was morning, on October 30th.
GetHuman: Did you reach out to Tiscali TalkTalk, and if so, how?
GetHuman: And which of these common Tiscali TalkTalk customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-181771 a list of common Tiscali TalkTalk problems)
GetHuman-181771: "Change plan" was why I was trying to call.
GetHuman-181771's review of Tiscali TalkTalk customer service
GetHuman: So how would you sum up your experience for GetHuman's Tiscali TalkTalk customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
GetHuman-181771: Extremley bad service , cut off once, incorrect dept * times and passed around from pillar to post with no customer service what so ever.
GetHuman: Let's quantify your experience contacting Tiscali TalkTalk. On a scale of 1 to 5, how easy is it go get help on a Tiscali TalkTalk problem?
GetHuman-181771: I'd give them a five out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
GetHuman-181771: I'd give them a two out of five on communication.
GetHuman: And what about Tiscali TalkTalk's ability to quickly and effectively address your problem?
GetHuman-181771: For that I would say five out of five.
GetHuman: And finally- any advice for other Tiscali TalkTalk customers?
GetHuman-181771: Call them early in the day or late. Don't forget any personal or account information you might need for Tiscali TalkTalk to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-181771 taken from his Tiscali TalkTalk customer service problem that occurred on October 30th, 2017.