Ceva Logistics: Amazon used CEVA to ship something to me. Trac...
A Ceva Logistics customer review by GetHuman user GetHuman-269927 from October 30th, 2017
Background on GetHuman-269927's case
GetHuman: GetHuman-269927 - can you tell our other Ceva Logistics customers when your case took place?
GetHuman-269927: Yeah. It was evening, on October 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-269927 a list of common Ceva Logistics problems)
GetHuman-269927: "Track item" was why I was trying to call.
GetHuman-269927'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-269927: Amazon used CEVA to ship something to me. Tracking indicated they had contacted me but they had not. I used this number to get someone on the line and finalize details.
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-269927: 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-269927: 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-269927: For that I would say five out of five.
GetHuman: And finally- any advice for other Ceva Logistics customers?
GetHuman-269927: 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-269927 taken from his Ceva Logistics customer service problem that occurred on October 23rd, 2017.