Article View: comp.os.os2.programmer
Article #409Re: IBMLINK - WARNING!
From: Dave Andrews
Date: Wed, 22 Jul 1992 12:59
Date: Wed, 22 Jul 1992 12:59
26 lines
1606 bytes
1606 bytes
In article <_!dms=m.grega@netcom.com> grega@netcom.com (Greg Altman) writes: > >Calling IBMLINK DOES NOT get you a better treatment then calling the 800 >number. This is true, but sometimes IBMLink is the preferable way to go. I find that I can report problems via ETR (electronically) in more precise terms than I can talking to a level-1 person at the support center. I can also pick up any technical response on my schedule rather than have to be chained to my desk awaiting a callback from the IBMer. It is probably easier to escalate a problem via the 800 number though. While your problem was eventually handled when the duty manager got involved, you always had the right to ask to speak to the duty manager yourself. It does take some time (years!) before you learn to negotiate the labyrinth that is IBM support. But after you've grown accustomed to it, and found out that the severity levels really do mean something, you can usually make the service people do business with you. (And yes, sometimes it helps to make noise! IBM management hates noise. Most people do.) - David Andrews dandrews@bilver.oau.org
Technical Details
Message-ID:
<1992Jul22.125936.10941@bilver.uucp>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!masscomp!peora!tarpit!bilver!dandrewsReferences:
<1992Jul10.180248.8498@jpradley.jpr.com> <_!dms=m.grega@netcom.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.os2.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!masscomp!peora!tarpit!bilver!dandrews From: dandrews@bilver.uucp (Dave Andrews) Subject: Re: IBMLINK - WARNING! Organization: W. J. Vermillion - Winter Park, FL Date: Wed, 22 Jul 1992 12:59:36 GMT Message-ID: <1992Jul22.125936.10941@bilver.uucp> References: <1992Jul10.180248.8498@jpradley.jpr.com> <_!dms=m.grega@netcom.com> Lines: 27