<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 8 Things to do before opening ticket with Checkpoint</title>
	<atom:link href="http://yurisk.info/2010/06/25/things-to-do-before-opening-ticket-with-checkpoint/feed/" rel="self" type="application/rss+xml" />
	<link>http://yurisk.info/2010/06/25/things-to-do-before-opening-ticket-with-checkpoint/</link>
	<description>Yuri Slobodyanyuk&#039;s blog on IT Security and Networking</description>
	<lastBuildDate>Tue, 31 Jan 2012 16:36:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: guy yovel</title>
		<link>http://yurisk.info/2010/06/25/things-to-do-before-opening-ticket-with-checkpoint/comment-page-1/#comment-1220</link>
		<dc:creator>guy yovel</dc:creator>
		<pubDate>Sat, 04 Sep 2010 12:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://yurisk.info/?p=925#comment-1220</guid>
		<description>I am impressed, you are absolutely correct. Check point support is pretty bad, I might say. Indeed if you have critical situation and proven network or system down due to check point software then you will get good service. Your case will be immediately escalated to higher support level and software developers will be involved fast enough, so you can expect a fixing patch in few days. This is very logic attitude from company perspective because customer can forgive on slow handling of medium severity case but will be very disappointed for slow acting when his business in troubles.

But in reality most, and I estimate this in 95%, the cases will be moderate severity and therefore the case will be 1 out of 30 cases per support engineer in average. Even if the support engineer is really want to assist, you are only one out of 30 other cases. So you can expect big delays and very slow work on your issue. So if you as customer or check point partner is professional enough to assist with debugging, self replication and workaround the issue will progress much faster then if you are passive and wait for instructions from the TAC. By the way in most cases the check point TAC is not acting as real technical and more as kind of call center. And the difference is huge…..

Best regards,
Guy Yovel
guyovel@nana.co.il</description>
		<content:encoded><![CDATA[<p>I am impressed, you are absolutely correct. Check point support is pretty bad, I might say. Indeed if you have critical situation and proven network or system down due to check point software then you will get good service. Your case will be immediately escalated to higher support level and software developers will be involved fast enough, so you can expect a fixing patch in few days. This is very logic attitude from company perspective because customer can forgive on slow handling of medium severity case but will be very disappointed for slow acting when his business in troubles.</p>
<p>But in reality most, and I estimate this in 95%, the cases will be moderate severity and therefore the case will be 1 out of 30 cases per support engineer in average. Even if the support engineer is really want to assist, you are only one out of 30 other cases. So you can expect big delays and very slow work on your issue. So if you as customer or check point partner is professional enough to assist with debugging, self replication and workaround the issue will progress much faster then if you are passive and wait for instructions from the TAC. By the way in most cases the check point TAC is not acting as real technical and more as kind of call center. And the difference is huge…..</p>
<p>Best regards,<br />
Guy Yovel<br />
<a href="mailto:guyovel@nana.co.il">guyovel@nana.co.il</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

