<div dir="ltr">Erick,<div>It's as Wes said. When you're a CCIE, Cisco expects a certain level of expertise. I'm not a CCIE, and in the past I often had to have a case re-queued to get the "right" level of competence. But also running my own helpdesk, I understand the need for the base tiers. There is a significant number of people that have never seen this mailing list, never took a class, and have not bothered to read the docs.</div>
<div><br></div><div>Look at it this way. Be thankful that Cisco provides this "shortcut" for the CCIE's. As for the CCIE opening and handing off. My assumption that when the CCIE opens the case, he would at least glance at the problem, and would sort it out if it didn't need to be escalated to Cisco.</div>
<div><br></div><div>Mike</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 14, 2013 at 10:34 AM, Erick Wellnitz <span dir="ltr"><<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Wondering if any of the Cisco guys could shed some light on a situation?</div><div> </div><div>Guys on my team, non CCIE, non Partner, are getting thrid party 'engineers' when they open TAC cases and very poor service. Is this the norm now? When I open a case I get a 15 - 20 minute response time even on sev. 4 cases.</div>
<div> </div><div>It's kind of goofy that in order to get a deccent TAC engineer I would have to open all of the cases and hand them off.</div><div> </div><div>Thanks!</div><span class="HOEnZb"><font color="#888888"><div>
</div><div>-E</div></font></span></div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>