Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: bill@toto.UUCP (Bill Cerny)
Newsgroups: comp.dcom.telecom
Subject: Re: Caller-ID Objections
Message-ID: <2430@accuvax.nwu.edu>
Date: 27 Dec 89 04:52:16 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 27
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 9, Issue 597, message 1 of 8


I need to keep up-to-date with all the 1.0E6 products & services that
are emerging in the World of Telecom, so that I can identify possible
optimizations/enhancements to my company's telecom profile (you, too?)

When the new issue of the trade rag plops on my desk, I scour thru and
make perhaps a half dozen inquiries in one day, resulting in call
backs.  When (if) the return call arrives, it starts, "Hi, this is
Joe.  What can I answer for you?"  And I attempt to figure out who Joe
works for, and what product/service his company has caught my
attention.

Hello Caller*ID!  I'd like to build an inquiry record keyed "Company
X, Product/Service Y" by telephone number.  Since the return call
won't arrive from the 800 number (marketing) I dialed, I'll have a few
alias entries that include NPA-NXX ("for instate callers").  If the
return call is made to my original inquiry, I'll be able to deduce the
subject of the call quicker (and prevent the notion that I've been in
contact with the competition).

Yep; I'm ready for Caller*ID.  If my local telco won't provide it, I
can always get it in another LATA, right?
 

Bill Cerny
bill@toto.info.com    |    attmail: !denwa!bill    |    fax: 619-298-1656