{"id":504,"date":"2012-12-11T12:19:54","date_gmt":"2012-12-11T17:19:54","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/12\/show-me-the-documentation\/"},"modified":"2012-12-11T12:19:54","modified_gmt":"2012-12-11T17:19:54","slug":"show-me-the-documentation","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/12\/show-me-the-documentation\/","title":{"rendered":"Show Me the Documentation!"},"content":{"rendered":"

\"13901387_gal\"<\/a>Usually my blog tends to be more technical than dealing with the human side of support. That’s because usually high resource usage in support is caused by not researching reports or lack of understand of the technology. But there are a few every now and then that are an exception to the rule. We came across a difficult scenario a couple of days ago where a customer is having issues with a service. So of course we ask for documentation. Instead of providing the information requested, instead we get the “can’t you just fix it?”, yes we can if we can decipher what is wrong out of thin air. <\/p>\n

One of things we sell to our customers as what separates us from the rest is support. I stand by that. We’re not the biggest fish, yet. But that allows us time to spend on fixing your issues, if you help us. Like a doctor or mechanic, we need to know where it hurts or where it smells like oil. <\/p>\n

Going back to this case, so talked to the partner again, hey we’re standing by to help you can you give us anything? The second reply was, I just got yelled at over this! At this point we’re really empathetic and trying to explain to the guy, if you can’t tell us what is wrong and show us we can’t review it. <\/p>\n

Guys I can’t emphasize this enough, I understand the emotions that come from getting chewed out. While some of you forget that while you post “You’re not getting it in the ear like we are!”, you’re doing it to us and I’m ok with it, it’s part of support. I understand. But if you could mix in the facts of the issue with some documentation so we can see or read what you’re seeing, you’d find that we can resolve your issues in a faster manner. <\/p>\n

Carlos Lascano
VP Support Services, ExchangeDefender
carlos@ownwebnow.com<\/a>
(877) 546-0316 x737<\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-504","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/504","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=504"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/504\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=504"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=504"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=504"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}