{"id":368,"date":"2012-03-05T17:06:50","date_gmt":"2012-03-05T22:06:50","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/03\/tips-to-a-speedy-resolution\/"},"modified":"2012-03-05T17:06:50","modified_gmt":"2012-03-05T22:06:50","slug":"tips-to-a-speedy-resolution","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/03\/tips-to-a-speedy-resolution\/","title":{"rendered":"Tips to a Speedy Resolution"},"content":{"rendered":"<p>Anybody that works in technology is familiar with ticketing systems and while at times they can be effective, it&#8217;s merely as effective as the two people interacting with the ticket. So here are some tips that can help make your tickets &#8220;one update&#8221; answer. The most important thing you can consider and rely on when opening your ticket is to maximize the effectiveness of the information you&#8217;re providing. If you give the person on the other end all the information they need, you&#8217;re improving your chances for a speedy resolutions. &#8220;But Carlos! I do this every time!&#8221;, well if you&#8217;re not following the guidelines below you&#8217;re now.  <\/p>\n<blockquote>\n<p><b>The Ticket Title has a character limit.<\/b>  <\/p>\n<p><i>That\u2019s correct if you write your entire ticket.<\/i><br \/>See? That didn&#8217;t help me get my point across, what I wanted to say is. If you type your entire ticket into the title we only see what fits in the title.  <\/p>\n<p><b>Please don\u2019t copy and paste your end users report to you.<\/b>  <\/p>\n<p>When we receive a ticket that says it\u2019s from Mary (with no address) and it says I emailed Tom (with no address) and it bounced back, we basically have zero information. While we\u2019d love to help, we don\u2019t know your client and to that extent their clients on first name basis.  <\/p>\n<p><b>After you submit a ticket, click on it to see what we see.<\/b>  <\/p>\n<p>This becomes pivotal, when you\u2019re pasting data with markup codes in it, it\u2019s important that you see what you\u2019re sending us. Because sometimes your ticket may have too much markup to the point that it won\u2019t render and we\u2019re left with no content or partial content. And knowing your luck and mine, it\u2019ll be the information we need to research your issue.<\/p>\n<\/blockquote>\n<p>Carlos Lascano<br \/>VP Support Services, ExchangeDefender<br \/><a href=\"mailto:carlos@ownwebnow.com\">carlos@ownwebnow.com<\/a><br \/>(877) 546-0316 x737<\/p>\n","protected":false},"excerpt":{"rendered":"<p> [&hellip;]<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"class_list":["post-368","post","type-post","status-publish","format-standard","hentry","category-support"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/368","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=368"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/368\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}