Cambridge Soundworks: LEFT MESSAGE YESTERDAY AND THEY HAVE NOT CALLED...
A Cambridge Soundworks customer review by GetHuman user ~mssally1 from November 20th, 2017
Background on ~mssally1's case
GetHuman: ~mssally1 - can you tell our other Cambridge Soundworks customers when your case took place?
~mssally1: Yeah. It was middle of the night, on November 19th.
GetHuman: Did you reach out to Cambridge Soundworks, and if so, how?
GetHuman: And which of these common Cambridge Soundworks customer issues best describes the reason you wanted to talk to them?
(Shows ~mssally1 a list of common Cambridge Soundworks problems)
~mssally1: "Where to buy" was why I was trying to call.
~mssally1's review of Cambridge Soundworks customer service
GetHuman: So how would you sum up your experience for GetHuman's Cambridge Soundworks 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.
~mssally1: LEFT MESSAGE YESTERDAY AND THEY HAVE NOT CALLED BACK. CALLED AGAIN TODAY WITH THE NUMBER YOU HAD AND I HAD TO LEAVE A MESSAGE
GetHuman: Let's quantify your experience contacting Cambridge Soundworks. On a scale of 1 to 5, how easy is it go get help on a Cambridge Soundworks problem?
~mssally1: I'd give them a two 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?
~mssally1: I'd give them a three out of five on communication.
GetHuman: And what about Cambridge Soundworks's ability to quickly and effectively address your problem?
~mssally1: For that I would say two out of five.
GetHuman: And finally- any advice for other Cambridge Soundworks customers?
~mssally1: Call them early in the day or late. Don't forget any personal or account information you might need for Cambridge Soundworks to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~mssally1 taken from his Cambridge Soundworks customer service problem that occurred on November 19th, 2017.