Ceva Logistics: Answered on first ring but because I live in Ca...
A Ceva Logistics customer review by GetHuman user GetHuman-403918 from November 27th, 2017
Background on GetHuman-403918's case
GetHuman: GetHuman-403918 - can you tell our other Ceva Logistics customers when your case took place?
GetHuman-403918: Yup. It was middle of the night, on November 23rd.
GetHuman: Did you reach out to Ceva Logistics, and if so, how?
GetHuman: And which of these common Ceva Logistics customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-403918 a list of common Ceva Logistics problems)
GetHuman-403918: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-403918's review of Ceva Logistics customer service
GetHuman: So how would you sum up your experience for GetHuman's Ceva Logistics 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-403918: Answered on first ring but because I live in Canada they gave me numbers to call and then the service got crappy. Still not sure when delivery will be?
GetHuman: Let's quantify your experience contacting Ceva Logistics. On a scale of 1 to 5, how easy is it go get help on a Ceva Logistics problem?
GetHuman-403918: 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?
GetHuman-403918: I'd give them a one out of five on communication.
GetHuman: And what about Ceva Logistics's ability to quickly and effectively address your problem?
GetHuman-403918: For that I would say four out of five.
GetHuman: And finally- any advice for other Ceva Logistics customers?
GetHuman-403918: Call them early in the day or late. Don't forget any personal or account information you might need for Ceva Logistics to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-403918 taken from his Ceva Logistics customer service problem that occurred on November 23rd, 2017.