Ceva Logistics: this phone numaber did put me right through to...
A Ceva Logistics customer review by GetHuman user GetHuman-297893 from October 29th, 2017
Background on GetHuman-297893's case
GetHuman: GetHuman-297893 - can you tell our other Ceva Logistics customers when your case took place?
GetHuman-297893: Yup. It was late at night, on October 25th.
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-297893 a list of common Ceva Logistics problems)
GetHuman-297893: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-297893'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-297893: this phone numaber did put me right through to someone at ceva who was able to give me the phone * for their local office in my town.
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-297893: I'd give them a three 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-297893: I'd give them a five out of five on communication.
GetHuman: And what about Ceva Logistics's ability to quickly and effectively address your problem?
GetHuman-297893: For that I would say one out of five.
GetHuman: And finally- any advice for other Ceva Logistics customers?
GetHuman-297893: 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-297893 taken from his Ceva Logistics customer service problem that occurred on October 25th, 2017.