Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!uupsi!schoff
From: schoff@uu.psi.com (Martin Schoffstall)
Newsgroups: comp.dcom.lans
Subject: Re: Novell to tcp/ip gateways
Keywords: subject line says it all
Message-ID: <1990Jul12.040345.3717@uu.psi.com>
Date: 12 Jul 90 04:03:45 GMT
References: <25539@nuchat.UUCP> <1524@excelan.COM> <1394@chinacat.Unicom.COM>
Reply-To: schoff@uu.psi.com (Martin Schoffstall)
Organization: Performance Systems International, Inc.
Lines: 32

Boy this one hit a sympathetic nerve.  This happens to me twice a week,
a USENET article, a Communications Week article, a chance dialog
with a peer and I'm interested in a 3.5Mbit TCP drainstopper from
DrainTCP Inc, and then the telephone tag begins.

Similar to the postmaster@draintcp.com concept, I'd love to see a standard
of info@draintcp.com where I can ask for the 3.5Mbit TCP drainstopper,
append my postal address and get a "porn pack" of information through
the surface mails.  A response via email asking me for some more details,
"are you interested in the garden variety or the counter rotating version"
is not a problem.

The real shame here is that the smaller the company the more critical this is,
AT&T can afford to send 100 phone answerers to Florida on
a moments notice to answer inquiries, small companies have next to no
flexibility, esp during daylight.  And this is perfect evening work
for those who want to succeed....

Marty
---------------------

>In article <1524@excelan.COM> manoj@excelan.COM (manoj @ Prod Mktg) writes:
>>call them for literature on LAN WORKPLACE
>
>Ha!  This is pretty funny.  Mr. Goel, why don't *you* try calling them
>for literature.  I did a couple of weeks back.  The closest I ever got
>was your voice mail system, and a few days later, a good round of telephone
>tag with a sales critter.  I shudder to think that if it's this tough to
>get sales help, what's it going to be like to get applications support?
>Never did get to talk to anybody.  Needless to say, the client will not
>be using Novell products for this project.
>