>Utica on 8/30. Buffalo of 8/31, Illinois on 9/1. Then nothing until
this
>AM. When I checked it this AM it showed: 9/7 "attempted delivery,
>customer not home".
I guess it is region specific... in the Maryland/DC area, it goes to a
collection/distribution center (Burtonsville) where the packages are
scanned and then loaded on local delivery trucks. Must have to do
with density... the Hub approach may not be economic in your neck of
the woods, Emory.
But the fact that the driver said he didn't have your package
yesterday because it was loaded on another truck, says they are using
a hub but not scanning (or disclosing) the arrival at the HUB.
This all explains why they don't want too many people tracking other
people's packages, and discovering the fallacies in their data. If
there is only one datapoint, they can say "Well... that almost never
happens"
Companies will learn... the easy way or the hard way, that lying
doesn't work anymore with a connected customer community.
Regards,
John 74 Glacier DC GMC
this
>AM. When I checked it this AM it showed: 9/7 "attempted delivery,
>customer not home".
I guess it is region specific... in the Maryland/DC area, it goes to a
collection/distribution center (Burtonsville) where the packages are
scanned and then loaded on local delivery trucks. Must have to do
with density... the Hub approach may not be economic in your neck of
the woods, Emory.
But the fact that the driver said he didn't have your package
yesterday because it was loaded on another truck, says they are using
a hub but not scanning (or disclosing) the arrival at the HUB.
This all explains why they don't want too many people tracking other
people's packages, and discovering the fallacies in their data. If
there is only one datapoint, they can say "Well... that almost never
happens"
Companies will learn... the easy way or the hard way, that lying
doesn't work anymore with a connected customer community.
Regards,
John 74 Glacier DC GMC
