3 ms·
I had a very strange, mixed experience with Garmin customer services recently. My watch died after 2 1/2 years. I'd heard that Garmin will, unofficially, replac
by chimprich 3y ago
I had a very strange, mixed experience with Garmin customer services recently. My watch died after 2 1/2 years. I'd heard that Garmin will, unofficially, replace broken watches for a bit longer than the official warranty (and so they should, because 1 year life expectancy would be terrible for a smart watch), so I contacted them.
The said they'd replace it for free and gave me a label to download (great!) However, I was travelling and the label wasn't valid for where I was. I asked if I could send it myself or get the label re-allocated when I got back (it had a time limit).
We then exchanged a dozen or so emails where Garmin CS kept ignoring my suggestions and giving me stupid instructions (terrible) until we eventually agreed they'd give me another label when I got back (ok).
I got back home and requested another label. CS demanded payment equivalent to the cost of a new watch (terrible!) I repeatedly asked why they were suddenly asking for payment when they'd previously offered it for free and they kept ignoring the question (argh!)
I'd have been much less annoyed if they'd just said up front that it was out of warranty, as then I wouldn't have wasted weeks and dozens of emails.
I eventually noticed that the original label still seemed to be valid, so I took up their original offer, sent my watch off and got an apparently new replacement within a day or two (great! I think.)
So, very mixed views! It's a lot like trying to write a Garmin app. They've got some nice API documentation (with a tutorial) but very incomplete as soon as you try to do something non-trivial.